]
Adrian Brock commented on JBAS-1262:
------------------------------------
The MBean you show is a war not an ear.
"jboss.web.deployment:war"
Raise a new JIRA issue for new problems, but you'll need to provide
a lot more information than this partial stacktrace if you don't want it closed as
"incomplete information".
MBean for ear not deregistered when deploy fails
------------------------------------------------
Key: JBAS-1262
URL:
http://jira.jboss.com/jira/browse/JBAS-1262
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB2
Affects Versions: JBossAS-4.0.1 Final
Environment: Win2k, JDK 1.4.2, default-configuration as supplied.
Reporter: Heiko W. Rupp
Assigned To: Adrian Brock
Fix For: JBossAS-4.0.3RC1
1) deploy an ear that has a ejb-jar in it that fails verification
2) redeploy the same ear (either with or without changed jar).
3) you will get an exception:
21:55:12,206 INFO [EARDeployer] Init J2EE application: file:/D:/jboss401/server
/small/deploy/adb.ear
21:55:12,296 INFO [EARDeployment] Registration is not done -> stop
21:55:12,296 ERROR [MainDeployer] Could not initialise deployment:
file:/D:/jboss401/server/small/deploy/adb.ear
org.jboss.deployment.DeploymentException: Error in accessing application metadata: ; -
nested throwable: javax.management.InstanceAlreadyExistsException:
jboss.j2ee:service=EARDeployment,url='adb.ear' already registered.)
4) Go to jmx-console
jboss.j2ee
* service=EARDeployer
* service=EARDeployment,url='adb.ear'
5) go into the ,url=... MBean
6) MBean is in state 8 (registered)
7) call stop() and/or destroy()
22:01:47,795 WARN [ServiceController] Ignoring request to destroy nonexistent service:
jboss.j2ee:service=EARDeployment,url='adb.ear'
8) redeploy ear -> same exception again
9) call unregister over twiddle:
D:> d:\jboss401\bin\twiddle unregister
"jboss.j2ee:service=EARDeployment,url='adb.ear'"
10) MBean is gone in MBean-List, ear can be deployed as usual.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: