Dear Stephen,
today, we tried to implement an amqps collection following the instructions in your document. The only change we had to make was a newer version of qpid (apache-qpid-jms-0.9.0-bin.tar.gz was not available anymore).
We configured everything according to your instructions, but the gateway didn't establish an outbound connection to the target URL.
Associated log entries:
2016-10-27T16:32:43.141+0000 INFO 76 com.l7tech.server.transport.jms2.JmsBootProcess: Connection ccdbd58758c25bc65a5e1cd5a9c8e1d0 updated!2016-10-27T16:32:43.152+0000 INFO 155 com.l7tech.server.transport.jms2.asynch.a: Starting JMS poller on EC-nm-b2b w/o SSL,/opt/SecureSpan/Gateway/runtime/lib/ext/EC-Queue[ccdbd58758c25bc65a5e1cd5a9c8e1d2v1,ccdbd58758c25bc65a5e1cd5a9c8e1d0v3]
2016-10-27T16:32:43.153+0000 WARNING 155 com.l7tech.server.transport.jms2.asynch.a: Unable to receive message from JMS endpoint EC-nm-b2b w/o SSL,/opt/SecureSpan/Gateway/runtime/lib/ext/EC-Queue[ccdbd58758c25bc65a5e1cd5a9c8e1d2v1,ccdbd58758c25bc65a5e1cd5a9c8e1d0v3]
2016-10-27T16:32:43.155+0000 INFO 152 com.l7tech.server.transport.jms2.asynch.a: Stopping JMS poller on EC-nm-b2b w/o SSL,/opt/SecureSpan/Gateway/runtime/lib/ext/EC-Queue[ccdbd58758c25bc65a5e1cd5a9c8e1d2v1,ccdbd58758c25bc65a5e1cd5a9c8e1d0v2]
Any idea where to start troubleshooting? Is the information in your document still valid, especially the instruction to leave the JNDI URI blank?
Any help is appreciated!
Regards,
Thomas