EAP app(message provider) which uses a resource adapter can't automatically create durable subscription on remote A-MQ7 broker when the EAP app submitted the message.

[Setting]

• AMQ
  • allow anonymous access
  • I attached broker.xml

• EAP
  • I attached standalone-full.xml
    point of setting

    <remote-connector name="remote-connector-hfuruich-amq1" socket-binding="remote-hfuruich-amq1"/>
    
    <connection-factory name="RemoteHfuruichAMQConnectionFactory" entries="java:/jms/remote_cf" connectors="remote-connector-hfuruich-amq1"/>
    
    <outbound-socket-binding name="remote-hfuruich-amq1">
        <remote-destination host="10.64.221.155" port="61616"/>
    </outbound-socket-binding>
    

[Instruction to reproduce]

1. start AMQ broker (DEBUG level log might be useful)
2. start EAP
   standalone.sh --server-config=standalone-full.xml
3. download and an attached reproducer "minimize-messaging-web.zip"
   -> mvn install
   -> deploy
4. On the machine which EAP is running, execute the curl command
   curl localhost:8080/minimal/queue/hogeQueue -X POST --data 'message=hello'

[result]

"hogeQueue" is not automatically generated in the broker.

It seems like EAP app send a message to the broker using a resource adapter, but the broker somehow does not like queuing this message.

I changed broker's log level to DEBUG, and find following log

16:53:50,141 DEBUG [org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl] Message CoreMessage[messageID=59,durable=true,userID=3f478a7e-e6ed-11e7-9f28-cc3d829e19ca,priority=4, timestamp=Fri Dec 22 16:53:50 JST 2017,expiration=0, durable=true, address=jms.queue.hogeQueue,properties=TypedProperties[__AMQ_CID=3f4651fb-e6ed-11e7-9f28-cc3d829e19ca]]@1576608898 is not going anywhere as it didn't have a binding on address:jms.queue.hogeQueue