-
Bug
-
Resolution: Done
-
Major
-
EAP 5.0.0.CR3, EAP_EWP 5.1.0
-
None
-
jdk1.6.0_14
32bit Fedora 10
-
-
Documented as Resolved Issue
Access Admin console
-> Web Application (WAR)s
-> Add a new resource -> add sample.war (simple war example from tomcat): Deploy Exploded = no, Deploy Farmed = no (notice it can be accessed at localhost:8080/sample)
-> in Admin console WARS, click sample.war -> Control -> Stop
-> go back to Web Application (WAR)s, notice the status is DOWN (which it is if you check)
-> sample.war -> Control -> Start
-> go back to Web Application (WAR)s -> sample.war
Status is DOWN still and stays like that even though its up and working
Status stays the same even if you close the Admin Console. Only way to get it to update correctly is to apply another control action to another WAR ex) stop/restart jmx-console.war
- blocks
-
JBPAPP-2422 AS Console (Embedded Jopr) Bugs (tracking issue)
- Closed
- relates to
-
JBPAPP-3250 EAR deployment not always updated in admin console
- Closed
-
JBPAPP-5157 EAR application flagged as being unavailable in the admin-console
- Closed