AmqpProvider - Transport connection remotely closed

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

AmqpProvider - Transport connection remotely closed

jeunii
This post was updated on .
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

Re: AmqpProvider - Transport connection remotely closed

Gordon Sim
On 09/05/17 21:47, jeunii wrote:
> I am currently clueless as to why this would happen ? What other possible
> debugging can I do ? Any pointers would be highly recommended.

Do you know what that remote node is? It sounds like there is some error
that the remote peer is handling by just terminating the socket. It may
be that there is some message logged on that remote peer. You could also
try setting the env var PN_TRACE_FRM=1 for your client just to see the
protocol exchange and verify that there is no error being passed back.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: AmqpProvider - Transport connection remotely closed

Timothy Bish
In reply to this post by jeunii

The error alone without any other context simply indicates that the
remote end suddenly broke the connection to the client, as to why you'd
want to try and do some more digging.  One thing to do in these cases is
to try and capture an AMQP protocol trace to see what's happening on the
wire, there's some good information in the configuration documentation
on how to enable such logging on the client:
http://qpid.apache.org/releases/qpid-jms-0.22.0/docs/index.html



On 05/09/2017 04:47 PM, jeunii wrote:

> I am using ServiceMix alongside Apache camel and Qpid libraries to connect to
> a remote node to fetch JMS queues.
>
> My Bean config is ::
>
>    <bean id="amqp" class="org.apache.camel.component.amqp.AMQPComponent">
>      <property name="connectionFactory">
>         <bean class="org.apache.qpid.jms.JmsConnectionFactory">
>            <property name="remoteURI" value="amqp://esesslxjks.se:9443" />
>         </bean>
>      </property>
>    </bean>
>
>   <camelContext xmlns="http://camel.apache.org/schema/blueprint">
>      
>      <route>
>        <from uri="amqp:queue:///CS_output" />
>        <log message="Copying o the output directory"/>
>        <to uri="amqp:queue:///CS_input" />
>      </route>
>
>
> Using this bean I start my application and see some positive response ::
>
>
> | DEBUG | mix-7.0.0/deploy | JmsProducer                      | 43 -
> org.apache.camel.camel-core - 2.16.4 | Starting producer:
> Producer[amqp://queue:///CSDP_input]
> | DEBUG | mix-7.0.0/deploy | JmsConsumer                      | 43 -
> org.apache.camel.camel-core - 2.16.4 | Starting consumer:
> Consumer[amqp://queue:///CSDP_output]
> | DEBUG | mix-7.0.0/deploy | BlueprintCamelContext            | 43 -
> org.apache.camel.camel-core - 2.16.4 | Route: route1 >>>
> EventDrivenConsumerRoute[Endpoint[amqp://queue:///CS_output] ->
> Pipeline[[Channel[Log(route1)[Copying o the output directory]],
> Channel[sendTo(Endpoint[amqp://queue:///CS_input])]]]]
> | DEBUG | mix-7.0.0/deploy | faultJmsMessageListenerContainer | 154 -
> org.apache.servicemix.bundles.spring-jms - 3.2.17.RELEASE_1 | Established
> shared JMS Connection
>
>
> But then I get the below ERROR ::
>
>
> | DEBUG | esesslxjks.se:9443] | AmqpProvider                     | 226 -
> qpid-jms-client.jar - 0.0.0 | Transport connection remotely closed
> | DEBUG | esesslxjks.se:9443] | JmsConnection                    | 226 -
> qpid-jms-client.jar - 0.0.0 | Async exception with no exception listener:
> java.io.IOException: Connection remotely closed.
> java.io.IOException: Connection remotely closed.
>       at
> org.apache.qpid.jms.provider.amqp.AmqpProvider$18.run(AmqpProvider.java:727)[226:qpid-jms-client.jar:0.0.0]
>       at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_121]
>       at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_121]
>       at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_121]
>       at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_121]
>       at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_121]
>       at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_121]
>       at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]
>
>
> I am currently clueless as to why this would happen ? What other possible
> debugging can I do ? Any pointers would be highly recommended.
>
>
>
> --
> View this message in context: http://qpid.2158936.n2.nabble.com/AmqpProvider-Transport-connection-remotely-closed-tp7663002.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]