-
1. Re: JMX-console problem in JBoss 3.2.3
dbeckedo2 Feb 25, 2004 3:18 PM (in response to divine_comedy)I've got the same problem trying to list JNDI info via the jmx-console (JBoss 3.2.3). I don't see any resolutions posted on this. Seems bizarre that something as basic as this would slip through the QA process.
-David -
2. Re: JMX-console problem in JBoss 3.2.3
juha Feb 26, 2004 12:23 AM (in response to divine_comedy)Seems to work fine for me. What version of Tomcat are you using?
-
3. Re: JMX-console problem in JBoss 3.2.3
amayingenta Feb 26, 2004 6:42 AM (in response to divine_comedy)Are you using Tomcat 5? We had the same problem. The fix (which just adds a no argument constructor) is checked into CVS and will be in JBoss 3.2.4.
You could do what I did and fix it in a copy of the 3.2.3 source and just update the class in jmx-console.war.
Seems like Jasper has changed how it creates instances of JavaBeans - it used to use java.beans.Beans.instantiate(), but now it uses the no-args constructor directly. The constructor should never get called as there should already be a copy of the bean in the Request.
-Andrew -
4. Re: JMX-console problem in JBoss 3.2.3
murxx Feb 27, 2004 7:20 AM (in response to divine_comedy)I got the same problem here!
Can you perhaps provide a compiled version of the fixed class?!
I know that sounds lazy of me, but finding through the JBOSS CVS would take me half a day, and that's too much time. Or can you point me a quick way?!
Thx in advance!
(I'd be glad if you could mail it to me tim.adler(at)bertelsmann.de) -
5. Re: JMX-console problem in JBoss 3.2.3
murxx Feb 27, 2004 7:54 AM (in response to divine_comedy)Aww man, sorry I didn't say anything!
Managed it myself. Thought that thing had some big imports or stuff, but wasn't THAT difficult :)! -
6. Re: JMX-console problem in JBoss 3.2.3
rmaucher Feb 27, 2004 8:11 AM (in response to divine_comedy)"amayingenta" wrote:
Are you using Tomcat 5? We had the same problem. The fix (which just adds a no argument constructor) is checked into CVS and will be in JBoss 3.2.4.
You could do what I did and fix it in a copy of the 3.2.3 source and just update the class in jmx-console.war.
Seems like Jasper has changed how it creates instances of JavaBeans - it used to use java.beans.Beans.instantiate(), but now it uses the no-args constructor directly. The constructor should never get called as there should already be a copy of the bean in the Request.
-Andrew
The page was invalid. The new JSP spec now recommends throwing an exceptio at translation time, so that's what is done. The latest Jasper (will be in Tomcat 5.0.20) now has a flag in case it is better to disable this.