activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Dossot (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-1455) Network bridge keeps falling down
Date Wed, 10 Oct 2007 18:18:24 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40336
] 

David Dossot commented on AMQ-1455:
-----------------------------------

I have stopped using VM transport altogether from my embedded client application, but the
problem still happens: the bridge keeps falling down.

I noticed the issue seems to happen if I have a queue browser (from Hermes) on the same distributed
queue my application is using.

I recognize the issue is hard to reproduce on your side, but in the mean time can the bridge
be made more resilient to runtime exceptions so it recovers and does not stop?



> Network bridge keeps falling down
> ---------------------------------
>
>                 Key: AMQ-1455
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1455
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.0.0
>         Environment: apache-activemq-5.0-20071008.215641-19, RHEL 4, JDK 1.6.0_02
>            Reporter: David Dossot
>
> The bridge between two nodes keeps falling down after a few minutes of use.
> This is maybe a misconfiguration and totally my bad, so here is the network config:
> 		<transportConnectors>
> 			<transportConnector uri="vm://${esb.node.name}" />
> 			<transportConnector uri="tcp://localhost:58080" discoveryUri="rendezvous://dev-esb-node"
/>
> 		</transportConnectors>
> 		<networkConnectors>
> 			<networkConnector conduitSubscriptions="true" decreaseNetworkConsumerPriority="true"
dynamicOnly="true"
> 				networkTTL="64" uri="rendezvous://dev-esb-node" userName="broker" password="XXX"
/>
> 		</networkConnectors>
> ${esb.node.name} resolves to "backbone-node-8080" on one box and "collection-node-8080"
on the other.
> And here are the errors when the bridge crashes:
> 11:04:46,241 DEBUG [org.apache.activemq.network.DemandForwardingBridge] backbone-node-8080
Forwarding sub on vm://backbone-node-8080#4 from collection-node-8080 :  ConsumerInfo {commandId
= 4, responseRequired = true, consumerId = ID:ddo-mbp.local-51198-1191953085196-0:0:1:1, destination
= queue://esb.admin.errors, prefetchSize = 500, maximumPendingMessageLimit = 0, browser =
true, dispatchAsync = false, selector = null, subscriptionName = null, noLocal = false, exclusive
= false, retroactive = false, priority = 0, brokerPath = null, optimizedAcknowledge = false,
noRangeAcks = false, additionalPredicate = null}
> 11:04:46,250 INFO  [org.apache.activemq.network.DemandForwardingBridge] Network connection
between vm://backbone-node-8080#4 and tcp://esb-backbone-node2.dev.com/10.20.116.14:58
> 080 shutdown due to a local error: java.lang.NullPointerException
> 11:04:46,254 DEBUG [org.apache.activemq.network.DemandForwardingBridge] The local Exception
was:java.lang.NullPointerException
> java.lang.NullPointerException
>         at org.apache.activemq.network.DemandForwardingBridgeSupport.configureMessage(DemandForwardingBridgeSupport.java:539)
>         at org.apache.activemq.network.DemandForwardingBridgeSupport.serviceLocalCommand(DemandForwardingBridgeSupport.java:561)
>         at org.apache.activemq.network.DemandForwardingBridgeSupport$1.onCommand(DemandForwardingBridgeSupport.java:137)
>         at org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:100)
>         at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:67)
>         at org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:102)
>         at org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:40)
>         at org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:59)
>         at org.apache.activemq.broker.TransportConnection.dispatch(TransportConnection.java:1184)
>         at org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:803)
>         at org.apache.activemq.broker.TransportConnection.iterate(TransportConnection.java:838)
>         at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:118)
>         at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:42)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
>         at java.lang.Thread.run(Thread.java:619)
> 11:04:46,259 DEBUG [org.apache.activemq.network.DemandForwardingBridge]  stopping backbone-node-8080
bridge to collection-node-8080 is disposed already ? false
> 11:04:46,261 INFO  [org.apache.activemq.network.DemandForwardingBridge] backbone-node-8080
bridge to collection-node-8080 stopped

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message