Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-2894

HAJNDI config in bindings.xml is invalid

XMLWordPrintable

    • Workaround Exists
    • Hide

      When I altered the ports in deploy/cluster-service.xml and deploy/jms/hajndi-ds.xml, the behavior was normal. Server B had it's own HAJNDI service running listening on port 1500.

      Show
      When I altered the ports in deploy/cluster-service.xml and deploy/jms/hajndi-ds.xml, the behavior was normal. Server B had it's own HAJNDI service running listening on port 1500.

      When using de ServiceBindingManager, I was not able to change the HAJNDI port to 1500. The JBoss server started and configured HAJNDI to port 1100. This has led to an error 'The destination QUEUE.<queuename> does not exist' when two isolated servers (separate partition name and multicast address) were started on the same machine: server A with the default port bindings and server B with every port bound to port + 400. Server B connected to server A and didn't find the queue there.
      (I traced this with the debugger)

            bstansbe@redhat.com Brian Stansberry
            wsalembi_jira wsalembi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: