There seems to be an issue with configuring the statistics mbean when not using specific session factories.
Here's the test case I've been using:
1) Configure an ejb-jar to use statistics. jboss-service.xml:
2) Enable statistics in persistence.xml and configure the session factory:
3) Startup jboss. Despite the dependency on the mbean, it tries to set its session factory jndi name, which results in the following:
{org.hibernate.jmx.StatisticsService} - No session factory with JNDI name hibernateTestSF
Which is normal because the ejb-jar has not been fully deployed yet (although it has started deploying, the session factory from persistence.xml seems to get bound later on according to my server logs). If I don't set the session factory jndi name on the mbean it deploys fine and if I set it after the server has started via the jmx console, all is well. I think there might be an issue either with the dependency or with the setter in the mbean.
If you need a sample maven project or if the test case is not clear enough or the assigned component is not the right one, let me know.
JBoss 5.1 GA (using JPA)
DBMS: MSSQL 2005
In an effort to clean up, in bulk, tickets that are most likely out of date, we're transitioning all ORM 3 tickets to an "Awaiting Test Case" state. Please see http://in.relation.to/Bloggers/HibernateORMJIRAPoliciesAndCleanUpTactics for more information.
If this is still a legitimate bug in ORM 4, please provide either a test case that reproduces it or enough detail (entities, mappings, snippets, etc.) to show that it still fails on 4. If nothing is received within 3 months or so, we'll be automatically closing them.
Thank you!
Bulk rejecting stale issues. If this is still a legitimate issue on ORM 4, feel free to comment and attach a test case. I'll address responses case-by-case. Thanks!