No, I see:
13:47:22,934 INFO [Server] JBoss (MX MicroKernel) [3.2.4 (build: CVSTag=JBoss_3_2_4 date=200406040847)] Started in 9s:984ms 13:47:22,934 INFO [Tomcat5] Saw org.jboss.system.server.started notification, starting connectors 13:47:22,981 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080 13:47:23,106 INFO [ChannelSocket] JK2: ajp13 listening on /0.0.0.0:8009 13:47:23,106 INFO [JkMain] Jk running ID=0 time=0/47 config=null
Try listing the mbean metadata using the twiddle command line tool:
[starksm@banshee9100 bin]$ twiddle.sh info 'jboss.web:type=Service,serviceName=jboss.web' Description: null +++ Attributes: Name: modelerType Type: java.lang.String Access: rw Name: connectorNames Type: [Ljavax.management.ObjectName; Access: r- Name: debug Type: int Access: rw Name: name Type: java.lang.String Access: rw Name: domain Type: java.lang.String Access: r- Name: containerName Type: javax.management.ObjectName Access: r- Name: info Type: java.lang.String Access: r- Name: objectName Type: javax.management.ObjectName Access: r- +++ Operations: void start() [Lorg.apache.catalina.LifecycleListener; findLifecycleListeners() java.lang.String toString() void postRegister(java.lang.Boolean param0) [Lorg.apache.catalina.Connector; findConnectors() void initialize() void stop() void destroy() void init()
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.
[root@inwood bin]# ./twiddle.sh info 'jboss.web:type=Service,serviceName=jboss.web' Description: Standard Service Component +++ Attributes: Name: modelerType Type: java.lang.String Access: rw Name: debug Type: int Access: rw Name: managedResource Type: java.lang.Object Access: rw Name: name Type: java.lang.String Access: rw Name: connectorNames Type: [Ljavax.management.ObjectName; Access: r- Name: container Type: org.apache.catalina.Container Access: rw Name: containerName Type: javax.management.ObjectName Access: r- +++ Operations: void addConnector(org.apache.catalina.Connector connector) void start() void stop() [root@inwood bin]#
Yes, this causes the problem. I think the integration code should not use findConnectors, but instead call start on each connector MBean, which would avoid the problem (although the capability of starting the connectors after the rest of the server will be lost).
Starting and stopping the connectors independent of the web apps is what I want though. This was the easiest way to accomplish this currently. In the future I would like the connectors more loosely coupled such that the transport layer can be managed independent of the core web server like the other containers. Let's think about that for the next release.
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.
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 greatly appreciated.
This needs tc5.0.26 to work so I don't see what the mystery is here about making this go away. Use the version of tomcat shipped with jboss. The metadata is that the component itself exposes. How this is done depends on the type of the mbean that is gegistered with jmx.
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.
And now it is no longer a mystery...
in server.xml, i had...
<Service name="jboss.web" className="org.jboss.web.tomcat.tc5.StandardService">
works fine now.
thx for the help.