[
https://jira.jboss.org/jira/browse/JBAS-6500?page=com.atlassian.jira.plug...
]
Shelly McGowan updated JBAS-6500:
---------------------------------
EAR:
"jboss.deployment:id=\"vfszip:" +
System.getProperty("jsfunit.deploy.dir") + "/" + earName +
"\",*";
WAR:
"jboss.deployment:id=\"jboss.web.deployment:war=/"+warName+"\",*";
EJB:
"jboss.j2ee:module=\""+ejbJarName+"\",service=EjbModule";
JMX View and ManagementView do not consistently reflect J2EE
application state after undeployment
-------------------------------------------------------------------------------------------------
Key: JBAS-6500
URL:
https://jira.jboss.org/jira/browse/JBAS-6500
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Shelly McGowan
Assignee: Shelly McGowan
Fix For: JBossAS-5.1.0.Beta1
This issue was detected managing applications through the Embedded Console. An
enterprise archive (.ear) can be successfully added and removed from the management
console. When the .ear is DELETED, embedded console returns status:
Successfully deleted Enterprise Application (EAR) 'earname.ear'."
Using JMX to detect the status of the deployment for the .ear and its' subcomponents
still shows the STATE == DEPLOYED.
Not sure if this is a goal for the 5.1.0.Beta1 release but opened for tracking.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira