Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-2016

[activemq-client] Connection cannot be established when setting wireFormat.maxInactivityDurationInitalDelay=0

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • JBoss A-MQ 6.3, Jboss A-MQ 7.0.0.ER12
    • None
    • Hide

      using the QE client program:

      java -jar /var/dtests/node_data/clients/aoc7.jar sender --broker tcp://localhost:61616 --conn-username admin --conn-password admin --address "myQueue" --conn-max-inactivity-dur-init-delay 1

      Show
      using the QE client program: java -jar /var/dtests/node_data/clients/aoc7.jar sender --broker tcp://localhost:61616 --conn-username admin --conn-password admin --address "myQueue" --conn-max-inactivity-dur-init-delay 1

      If I use activemq-client and set "wireFormat.maxInactivityDurationInitalDelay=0" in connection URL, then the client cannot connect to either A-MQ 6.3.0r1 and 7er13.

      If I set ...InitalDelay > 0, it works on 7er13 and only sometimes works on 6.3.0

      With ...InitalDelay > 100 it works on both.

      In cases it "does not work", the client is throwing

      17:24:16,889 ERROR Error while creating session! Wire format negotiation timeout: peer did not send his wire format.
javax.jms.JMSException: Wire format negotiation timeout: peer did not send his wire format.

      I believe that all the values are perfectly legal and should be permitted and should work.

            Unassigned Unassigned
            jdanek@redhat.com Jiri Daněk
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: