Details
-
Bug
-
Resolution: Done
-
Critical
-
EAP 5.0.0, EAP 5.0.1
-
None
-
EAP 5.0.1 running on Fedora 11 Kernel 2.6.30.10
Description
Deployed datasources will sometimes return a state of UNKNOWN instead of a state of RUNNING when certain configuration is used. As current, this issue prevents Admin Console (admin-console) from reporting the correct state of deployed components. In some instance, the issue is confined to the farm directory but in others the issue seems to also affect deployments in the deploy directory.
The steps/actions when running EAP and deploying the first datasource seems to directly affect the outcome of the deployment's state. For example, if removing all the JGroups environment options from the run.sh command-line seems to make the issue go away, however, it should be noted that I have reproduced this issue without those options in the past (just not able to do it now).
Attachments
Issue Links
- is related to
-
JBPAPP-3652 ProfileService: when deployed to cluster node, ManagedComponents incorrectly report a RunState of UNKNOWN or STARTING, when they should report STARTED
- Resolved