Description
REPRO STEPS
=============
- Make two copies of the 'all' config (named node1 and node2)
- Using the service binding manager, startup both instances using:
./run.sh -c node1 -Djboss.service.binding.set=ports-01
./run.sh -c node2 -Djboss.service.binding.set=ports-02
Look for datasource, connection factory, topic, or queue managed components that are reporting a state of UNKNOWN or STARTING. In my case, the "JmsXA" connection factory on one of the nodes was reporting UNKNOWN, and the "DLQ" and "ExpiryQueue" queues on one of the nodes were reporting STARTING. For the "JmsXA" connection factory, I checked the corresponding jboss.jca:name=JmsXA,service=ConnectionFactoryBinding MBean in the jmx-console and its StateString attribute was "STARTED", so the ProfileService-reported state of UNKNOWN is not consistent with what JMX reports.
Attachments
Issue Links
- relates to
-
JBPAPP-4332 Datasources deployed in EAP return an UNKNOWN state in some instances
- Closed