Http Server start error

[cimatch]

I am Shimada.
It is likely to fail in the start of the http server by the environment of OS AIX5.2 / JBoss4.0.1sp1, and generating unusual "Error registering contexts". Isn't there knowing someone ..the solution..?

The following are output by the trace when starting.

javax.management.InstanceNotFoundException: jboss.web:J2EEApplication=none,J2EEServer=none,WebModule=//localhost/xxxx,j2eeType=Servlet,name=jsp is not registered.
 at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java(Compiled Code))
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java(Compiled Code))
 at org.apache.coyote.tomcat5.MapperListener.registerWrapper(MapperListener.java:468)
 at org.apache.coyote.tomcat5.MapperListener.init(MapperListener.java:140)
 at org.apache.coyote.tomcat5.CoyoteConnector.start(CoyoteConnector.java:1537)
 at org.jboss.web.tomcat.tc5.Tomcat5.startConnectors(Tomcat5.java:462)
 at org.jboss.web.tomcat.tc5.Tomcat5.handleNotification(Tomcat5.java:488)
 at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
 at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
 at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java(Compiled Code))
 at $Proxy22.handleNotification(Unknown Source)
 at org.jboss.mx.util.JBossNotificationBroadcasterSupport.handleNotification(JBossNotificationBroadcasterSupport.java(Inlined Compiled Code))
 at org.jboss.mx.util.JBossNotificationBroadcasterSupport.sendNotification(JBossNotificationBroadcasterSupport.java(Compiled Code))
 at org.jboss.system.server.ServerImpl.sendNotification(ServerImpl.java:838)
 at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:427)
 at org.jboss.system.server.ServerImpl.start(ServerImpl.java:310)
 at org.jboss.Main.boot(Main.java:162)
 at org.jboss.Main$1.run(Main.java:423)
 at java.lang.Thread.run(Thread.java:568)

[cimatch]

I solved this event to the self.

I thought that there was a problem in the version of jmx.jar of JBoss4.0.1sp1.
Therefore, when exchanging for JBoss-jmx.jar offered with JBoss4.0.3sp1, and testing, the phenomenon was not generated.

It is everyone's favor.