The only thing I have seen mentioned for some of the Microsoft services is needing to increase idleTimeout as they require the advertised value requested from the client to be above a certain value. The client defaults to a 60sec idle timeout, and so as can be seen in your trace advertises/requests 30sec in the Open frame per by the AMQP spec advice (i.e advertising half your actual timeout). However in the cases where that was seen/mentioned, I think it was clearly stated in any error returned.
Given the below, there is little I can think to advise as the trace from the client seems reasonable and no reason is given for the response, so I think you'd need to ask Microsoft, perhaps the included trackingId can help narrow down the reason. The fact your original mail said it works when used seperately is a bit puzzling though. Robbie On 20 July 2016 at 08:57, DraCzech <[email protected]> wrote: > So now I have finer logs - you can clearly see that the connection is closed > right after it is opened. No idea why the MS server closes it. In the log > there is first the connection attempt, then the Exception formed based on > the remote close. Then the connection should be closed in my part because an > exception has been caught. (There is no exception to close though, but that > is not the main problem.) > > Has anyone encountered similar behaviour while working with the Azure IoT > Hub/Event Hub servers? > > 2016-07-20 07:32:03.811456 [11039143:0] -> Open{ > containerId='C4EDBA888344', hostname='boxmessagehub.azure-devices.net', > maxFrameSize=1048576, channelMax=32767, idleTimeOut=30000, > outgoingLocales=null, incomingLocales=null, offeredCapabilities=null, > desiredCapabilities=[sole-connection-for-container], > properties={product=QpidJMS, version=0.10.0, platform=JVM: 1.7.0_75, > 24.75-b04, Oracle Corporation, OS: Linux, 3.2.0-1.3.0, arm}} > 2016-07-20 07:32:04.022224 [11039143:0] <- Open{ > containerId='DeviceGateway_265f135f269149b987d38c7c63940b61', > hostname='10.0.0.58', maxFrameSize=65536, channelMax=8191, > idleTimeOut=240000, outgoingLocales=null, incomingLocales=null, > offeredCapabilities=null, desiredCapabilities=null, > properties={com.microsoft:open-error=Error{condition=amqp:internal-error, > description='null', > info={com.microsoft:tracking-id=f23be8d574544125b0fb1557647b728e-G:8-TimeStamp:07/20/2016 > 07:32:04, com.microsoft:is-filtered=true}}}} > 2016-07-20 07:32:04.028086 [11039143:0] <- > Close{error=Error{condition=amqp:internal-error, description='null', > info={com.microsoft:tracking-id=f23be8d574544125b0fb1557647b728e-G:8-TimeStamp:07/20/2016 > 07:32:04, com.microsoft:is-filtered=true}}} > 2016-07-20 07:32:04.045978 2016-07-20 07:32:04,038 > {ServerConnector:BoxExchange} databroker.amq.OMJmsQueueConnector [DEBUG] > 2016-07-20 07:32:04.046192 javax.jms.JMSException: Received error from > remote peer without description [condition = amqp:internal-error] > 2016-07-20 07:32:04.046253 at > org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:148) > 2016-07-20 07:32:04.046345 at > org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:103) > 2016-07-20 07:32:04.046406 at > org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.remotelyClosed(AmqpAbstractResource.java:147) > 2016-07-20 07:32:04.046467 at > org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.processRemoteClose(AmqpAbstractResource.java:242) > 2016-07-20 07:32:04.046528 at > org.apache.qpid.jms.provider.amqp.AmqpProvider.processUpdates(AmqpProvider.java:771) > 2016-07-20 07:32:04.046620 at > org.apache.qpid.jms.provider.amqp.AmqpProvider.access$1900(AmqpProvider.java:92) > 2016-07-20 07:32:04.046681 at > org.apache.qpid.jms.provider.amqp.AmqpProvider$17.run(AmqpProvider.java:699) > 2016-07-20 07:32:04.046742 at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > 2016-07-20 07:32:04.046803 at > java.util.concurrent.FutureTask.run(FutureTask.java:262) > 2016-07-20 07:32:04.056085 at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) > 2016-07-20 07:32:04.056237 at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) > 2016-07-20 07:32:04.056299 at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > 2016-07-20 07:32:04.056360 at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > 2016-07-20 07:32:04.056451 at java.lang.Thread.run(Thread.java:745) > 2016-07-20 07:32:04.066008 2016-07-20 07:32:04,058 {QpidJMS Connection > Executor: ID:7044249b-8821-48c5-ac5c-4785a8be6eb9:1} > databroker.jms.ServerConnector [INFO ] About to stop server connection: > javax.jms.JMSException: Received error from remote peer without description > [condition = amqp:internal-error] > (amqps://boxmessagehub.azure-devices.net:5671) > 2016-07-20 07:32:04.068786 [11039143:0] -> Begin{remoteChannel=null, > nextOutgoingId=1, incomingWindow=2047, outgoingWindow=2147483647, > handleMax=65535, offeredCapabilities=null, desiredCapabilities=null, > properties=null} > 2016-07-20 07:32:04.074343 [11039143:0] -> Close{error=null} > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/Cannot-conect-while-using-ActiveMQ-with-Qpid-JMS-client-tp7647859p7647916.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
