Skip to content

Connections to Tibco EMS Fault-Tolerant setup only loads queues from first server in list, regardless of whether it is the Active server or not #187

Description

@jmhellman

Specifications

  • JMSToolBox version: 5.9.0
  • OS (Name, version, 32/64bits): Windows 10 Enterprise
  • Q provider (kind, version) : Tibco EMS 10.3

Expected Behavior

When connecting to a fault-tolerant Tibco EMS setup using multiple Host entries, JMS Toolbox should identify which server is the "active" server in the fault-tolerant pair and only retrieve queue/topic information from that server.

Actual Behavior

JMS toolbox will create a connection based on whatever host in the pair is active, however it will retrieve the queue list using the underlying tibjms .jar based on whatever host is first in the list. This results in JMSToolbox only showing queues that are statically configured and not dynamically created/populated.

Steps to Reproduce the Problem

  1. In JMSToolbox, add a pair of Tibco EMS hosts that are set up with a Fault-Tolerant configuration, Node 1 in the first host slot and Node 2 in the second host slot
  2. In Tibco EMS Admin:
    a. Start Node 1
    b. Create static queues on Node 1
    c. Create dynamic queues on Node 1
    d. Start Node 2
    e. Stop Node 1 (force failover to Node 2)
  3. In JMSToolbox, connect your session to the fault-tolerant pair
  4. Confirm no dynamic queues currently available on Node 2 are listed in JMSToolbox, only the static queues from Node 1 are listed
  5. Disconnect your session
  6. Change the order of Node 1 and Node 2 in the list of hosts
  7. Connect your session to the fault-tolerant pair
  8. Confirm the full list of queues is available

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions