Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-137

[AMQP] Broker does not support dynamic sender link

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • A-MQ 7.0.0.GA
    • A-MQ 7.0.0.ER7
    • None
    • Hide

      1. Start the broker on linux
      2. Start the Lite self test

      mstest /testcontainer:./Test.Amqp.Net/Test.Amqp.Net.dll /test:TestMethod_DynamicSenderLink
      Show
      1. Start the broker on linux 2. Start the Lite self test mstest /testcontainer:./Test.Amqp.Net/Test.Amqp.Net.dll /test:TestMethod_DynamicSenderLink
    • AMQ 7.0.2 sprint 1

      In this test the client creates a sender with no target but with the Dynamic flag = true.
      The broker is supposed to generate a name for the endpoint and return it to the client in the corresponding link attach. Then the client can send to the sender link and open a receiver to the name the broker returned to get the messages.

      It looks like the broker is returning the generated name but not associating that name with the sender link the client created.
      I've got traces of AMQ7 hitting an error and of Qpidd doing it correctly.

      The A-MQ7 broker console issues an error:

      16:07:20,292 INFO  [org.apache.activemq.artemis.spi.core.security.ActiveMQJAASSecurityManager] Couldn't validate user: user name is null
ActiveMQIllegalStateException[errorType=ILLEGAL_STATE message=AMQ119029: No address configured on the Server''s Session]
	at org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.send(ServerSessionImpl.java:1256)
	at org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.send(ServerSessionImpl.java:1219)
	at org.apache.activemq.artemis.core.protocol.proton.plug.ProtonSessionIntegrationCallback.serverSend(ProtonSessionIntegrationCallback.java:351)
	at org.proton.plug.context.server.ProtonServerReceiverContext.onMessage(ProtonServerReceiverContext.java:116)
	at org.proton.plug.context.AbstractConnectionContext$LocalListener.onDelivery(AbstractConnectionContext.java:299)
	at org.proton.plug.handler.Events.dispatch(Events.java:100)
	at org.proton.plug.handler.impl.ProtonHandlerImpl.dispatch(ProtonHandlerImpl.java:362)
	at org.proton.plug.handler.impl.ProtonHandlerImpl.access$000(ProtonHandlerImpl.java:49)
	at org.proton.plug.handler.impl.ProtonHandlerImpl$1.run(ProtonHandlerImpl.java:63)
	at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:103)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
!!!!! Readable!!!!!!!
16:08:21,683 WARN  [org.apache.activemq.artemis.core.client] AMQ212037: Connection failure has been detected: AMQ119014: Did not receive data from null. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT]
16:08:21,683 WARN  [org.apache.activemq.artemis.core.server] AMQ222061: Client connection failed, clearing up resources for session 99ceb8dc-326b-11e6-a6c4-4ceb42c7eda9

        1. amq7-dynSenderLink-fail.pcapng.html
          43 kB
          Chuck Rolke
        2. ENTMQ-1766.patch
          3 kB
          Timothy Bish
        3. qpidd-dynSenderLink-pass.pcapng.html
          79 kB
          Chuck Rolke

            gaohoward Howard Gao
            crolke@redhat.com Chuck Rolke (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: