Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-3652

ProfileService: when deployed to cluster node, ManagedComponents incorrectly report a RunState of UNKNOWN or STARTING, when they should report STARTED

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Critical Critical
    • EAP 5.0.1
    • EAP 5.0.0 WS CXF TP
    • Other
    • None

      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.

              emuckenhuber_jira Emanuel Muckenhuber (Inactive)
              ips_jira Ian Springer (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: