This content has been marked as final.
Show 3 replies
-
1. Re: MBean ObjectNames are a garbled mess!
dimitris Mar 11, 2009 7:45 AM (in response to amlodzin)"amlodzin" wrote:
The problem, in the app-state case, is that the "jboss.web.deployment:*" MBeans use a random id as a key property, in addition to just one other key property - the war file name. That makes it impossible to link a particular war file with its parent EAR file (if there is one) when several ear files are deployed containing the a war file with the same name.
Where do you see that - which AS version?
Also, I'd be interested in some hard facts about JBoss' insignificance, rather than some random ranting. -
2. Re: MBean ObjectNames are a garbled mess!
amlodzin Mar 11, 2009 3:29 PM (in response to amlodzin)"dimitris@jboss.org" wrote:
"amlodzin" wrote:
The problem, in the app-state case, is that the "jboss.web.deployment:*" MBeans use a random id as a key property, in addition to just one other key property - the war file name. That makes it impossible to link a particular war file with its parent EAR file (if there is one) when several ear files are deployed containing the a war file with the same name.
Where do you see that - which AS version?
Every version of JBoss 4.x, including at least 4.0.2 to 4.2.3.
Also, JBoss 5.0.0 does away with the random id - but replaces it with NOTHING! So, if you could find the ID in 4.x (say, hidden in the Exception generated by jboss.system:service=MainDeployer.checkIncompleteDeployments()), you might have had a chance of matching it up to the MBean that contains the modules StateString. In 5.0.0, that chance, however slim, is gone completely."dimitris@jboss.org" wrote:
Also, I'd be interested in some hard facts about JBoss' insignificance, rather than some random ranting.
Got your attention, didn't it ;)
In our business of providing monitoring solutions for J2EE middleware, we always build support in stages: WebLogic 1st; WebSphere 2nd; OracleAS 3rd; JBoss last. I'm sure there are reasons beyond what the various appservers have to offer - but we follow the money. -
3. Re: MBean ObjectNames are a garbled mess!
amlodzin Mar 11, 2009 5:11 PM (in response to amlodzin)Wow - JBoss 5.0.1 doesn't even have a 'state' associated with any WebModule. The jboss.web.deployment MBeans still have the start() and stop() operations, but the StateString attribute is gone.
Finding out whether a particular application has all of it's modules in a running state or not just got even more difficult!
Thanks JBoss :(