Intermittent exception in startup

[hoguester]

We are seeing this in server.log upon startup of 2.4.4 on RedHat 7.2 ..... Doesn't seem to hurt anything but any direction would be appreciated.

JBOSS_CLASSPATH=:/usr/java/lib/tools.jar:run.jar:../lib/crimson.jar
jboss.home = /usr/local/JBoss-2.4.4_Tomcat-3.2.3/jboss
Using JAAS LoginConfig: file:/usr/local/JBoss-2.4.4_Tomcat-3.2.3/jboss/conf/tomcat/auth.conf
JBoss release: JBoss-2.4.4 CVSTag=JBoss_2_4_4
JBoss version: 2.4.4.2001-12-29 02:04:40 PST
Using configuration "tomcat"
[INFO,root] Started Log4jService, config=file:/usr/local/JBoss-2.4.4_Tomcat-3.2.3/jboss/conf/tomcat/log4j.properties
[INFO,Info] Java version: 1.3.0,IBM Corporation
[INFO,Info] Java VM: Classic VM 1.3.0,IBM Corporation
[INFO,Info] System: Linux 2.4.9-31smp,x86
[INFO,Shutdown] Shutdown hook added
javax.management.InstanceNotFoundException: DefaultDomain:service=Log
at com.sun.management.jmx.MBeanServerImpl.getMBean(MBeanServerImpl.java:1678)
at com.sun.management.jmx.MBeanServerImpl.addNotificationListener(MBeanServerImpl.java:1712)
at org.jboss.logging.Log4jService.preRegister(Log4jService.java:192)
at com.sun.management.jmx.MBeanServerImpl.preRegisterInvoker(MBeanServerImpl.java:2245)
at com.sun.management.jmx.MBeanServerImpl.createMBean(MBeanServerImpl.java:513)
at javax.management.loading.MLet.getMBeansFromURL(MLet.java:523)
at javax.management.loading.MLet.getMBeansFromURL(MLet.java:369)
at org.jboss.Main.(Main.java:180)
at org.jboss.Main$1.run(Main.java:110)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.Main.main(Main.java:106)
[INFO,Service Control] Initializing 48 MBeans

[adrian.brock]

That's weird.

I wonder if Sun's MLet implementation isn't threadsafe?
Is it always the log4jservice? From memory I think that
is the first to get loaded.

You have an smp kernel, do have multiple cpus?

You could try JBoss3.0 which doesn't use MLets.

Regards,
Adrian

[hoguester]

We do have multiple cpu's...can't really go with 3.0 just yet as we just went live with 2.4.4

[adrian.brock]

It just occured to me.

I think service=log was part of 2.4.3 and removed for
2.4.4 are you using an old jboss.conf?

Regards,
Adrian

[hoguester]

will look at it -- good thought

[hoguester]

Fixed it...it was because we had a mixture of jars from 2.4.3 and 2.4.4

Thanks