-
Bug
-
Resolution: Obsolete
-
Major
-
JBossAS-5.0.0.Beta3, JBossAS-5.0.0.Beta4, JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA, JBossAS-5.0.0.CR2, JBossAS-5.0.0.GA, JBossAS-5.0.1.GA, JBossAS-5.1.0.Beta1, JBossAS-5.1.0.CR1, JBossAS-5.1.0.GA
-
Tested on Windows XP SP3 with all JBoss versions. Some versions tested on RedHat EL4 with same results.
When using the JMX web console an exception thrown when invoking any MBean method causes a 500 server error rather than a stack trace to be displayed. To reproduce follow these steps:
. Run JBoss with everything set to the default.
. Go to "http://localhost:8080/jmx-console/".
. Click on "jboss.ws" in the left frame.
. Choose "service=ServerConfig"
. Enter "wibble" in the "WebServicePort" field and click the Apply button.
This seems to be the same for all exceptions generated by MBeans - whether generated by operations or attributes. The correct exception and stack trace appears in the log file.