There where two changes done from the previous working configuration:
- Switched to Java 6.0 (found out I was using 5.0 by mistake)
- A new MBean was added
Cursing the entire worlds and blaming the guy who wrote the new MBean did not solve the issue so I started checking other things. It turned out that when removing the Yourkit profiler agent from the JBoss start script prevented this issue.
Digging into the Yourkit startup options I've found out that the profiler light-weight telemetry may clash with some JavaEE application servers MBeans implementation. The Yourkit J2EE integration wizard (which I did not use) adds a startup option which starts the telemetry with a delay - "delay=10000".
Adding the delay option solved my problems !
No comments:
Post a Comment