OK...no answer...let me rephrase
When you execute the twiddle command, it obviously must look somewhere for the MBean
information. My question is where? Could it be that i have an out-of-date MBean
descriptor file or that my actual MBean class files are out of date.
Any ideas would be
And now it is no longer a mystery...
in server.xml, i had...
| Service name=jboss.web
|
instead of...
| Service name=jboss.web className=org.jboss.web.tomcat.tc5.StandardService
|
works fine now.
thx for the help.
View the original post :
I copied over the tomcat jars and jboss-service.xml from the 'default' configuration
in the /server directory and i'm still getting the error.
This is the mystery.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3838357#3838357
Reply to the post :
so...
how do i make this exception go away? I don't understand the relationship between the
MBean and the jars that get deployed so if you could point me in the right direction
i'd appreciate it.
-m
View the original post :
| 10:38:53,187 INFO [Tomcat5] Saw org.jboss.system.server.started notification,
starting connectors
| 10:38:53,187 WARN [Tomcat5] Failed to startConnectors
| RuntimeOperationsException: null
| Cause: java.lang.IllegalArgumentException: MBean does not contain operation
findConnectors
here's the output...looks like i have a different MBean. Something to consider, i was
swapping out the tomcat jar files with the v.5.0.25 embedded jars from the Tomcat
website. Not sure if that has anything to do with it.
| [EMAIL PROTECTED] bin]# ./twiddle.sh info
