I am wondering if something has been done with this issue. I am using the
2_3_1 version from CVS. I am not familiar with the internals of JBoss,
otherwise I would be fixing this.
Right now I have to shutdown JBoss in order for the changes to a bean to be
recognized.
Below is the output from the server
[Auto deploy] Auto deploy of
file:/D:/jboss-dev/jboss_2_3_1/jboss/dist/deploy/UserLogon.jar
[J2EE Deployer Default] Stopping module UserLogon.jar
[Container factory]
Undeploying:file:/D:/jboss-dev/jboss_2_3_1/jboss/dist/tmp/deploy/Default/Use
rLogon.jar/
[Container factory] Undeployed application:
file:/D:/jboss-dev/jboss_2_3_1/jboss/dist/tmp/deploy/Default/UserL
ogon.jar/
[J2EE Deployer Default] Destroying application UserLogon.jar
[J2EE Deployer Default] Deploy J2EE application:
file:/D:/jboss-dev/jboss_2_3_1/jboss/dist/deploy/UserLogon.ja
r
[J2EE Deployer Default] Create application UserLogon.jar
[J2EE Deployer Default] install module UserLogon.jar
[Container factory]
Deploying:file:/D:/jboss-dev/jboss_2_3_1/jboss/dist/tmp/deploy/Default/UserL
ogon.jar/
[Verifier] Verifying
file:/D:/jboss-dev/jboss_2_3_1/jboss/dist/tmp/deploy/Default/UserLogon.jar/e
jb1004.jar
[Container factory] Deploying UserLogon
[Container Management Proxy] Registration is not done -> destroy
[Container Management Proxy] Destroying
[Container Management Proxy] Destroyed
[Default] javax.management.InstanceAlreadyExistsException:
Management:container=UserLogon
[Default] at
com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134
)
[Default]
[Default] at
com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.ja
va:2352)
[Default]
[Default] at
com.sun.management.jmx.MBeanServerImpl.createMBean(MBeanServerImpl.java:388)
[Default]
[Default] at
org.jboss.ejb.ContainerFactory.registerContainer(ContainerFactory.java:659)
[Default]
[Default] at
org.jboss.ejb.ContainerFactory.createStatelessSessionContainer(ContainerFact
ory.java:585)
[Default]
[Default] at
org.jboss.ejb.ContainerFactory.createContainer(ContainerFactory.java:539)
[Default]
[Default] at
org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:431)
[Default]
[Default] at
org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:336)
[Default]
[Default] at
org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:276)
[Default]
[Default] at java.lang.reflect.Method.invoke(Native Method)
[Default]
[Default] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
[Default]
[Default] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
[Default]
[Default] at
org.jboss.deployment.J2eeDeployer.startModules(J2eeDeployer.java:460)
[Default]
[Default] at
org.jboss.deployment.J2eeDeployer.startApplication(J2eeDeployer.java:438)
[Default]
[Default] at
org.jboss.deployment.J2eeDeployer.deploy(J2eeDeployer.java:207)
[Default]
[Default] at java.lang.reflect.Method.invoke(Native Method)
[Default]
[Default] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
[Default]
[Default] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
[Default]
[Default] at org.jboss.ejb.AutoDeployer.deploy(AutoDeployer.java:379)
[Default]
[Default] at org.jboss.ejb.AutoDeployer.run(AutoDeployer.java:217)
[Default]
[Default] at java.lang.Thread.run(Unknown Source)
[Default]
[Default] Added ClassLoader: org.jboss.web.WebClassLoader@45aa00 URL:
http://tibetanelf:8083/WebClassLoader@45
65504/
[Container factory] Deployed application:
file:/D:/jboss-dev/jboss_2_3_1/jboss/dist/tmp/deploy/Default/UserLog
on.jar/
--------------
Hi Scott
It is still the same problem but I fixed the NPE which is caused
when the registration was not done in the ServiceMBeanSupport
and then the "log" variable was not created.
But now the registration ran into the problem that we have two
MBeans registered at the same time on the MBeanServer (on creating
the other destroying).
In my short sight I assumed that the destroying of the application
is done before the new EJBs are deployed.
I am not quite sure how to fix it but the error message shouldn't
hurt the application (I can make it silent) because it is caught.
Andy
> -----Original Message-----
> From: Scott M Stark [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 12, 2001 10:06 PM
> To: JBoss Dev
> Subject: [JBoss-dev] org.jboss.mgt.ContainerMgt now producing a
> InstanceAlreadyExistsException on redploy
>
>
> As of today's latest cvs code, on redeploy of a ejb-jar I am seeing
> a new InstanceAlreadyExistsException exception when a
> org.jboss.mgt.ContainerMgt is created in the ContainerFactory
> registerContainer method. Here is the point at which the module
> is stopped and reployed and the exception that results:
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
