activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] Created: (AMQ-3085) IndexOutOfBoundsException on FailoverTransport.updateURIs after: already known: java.net.UnknownHostException
Date Wed, 15 Dec 2010 12:19:03 GMT
IndexOutOfBoundsException on FailoverTransport.updateURIs after: already known: java.net.UnknownHostException
-------------------------------------------------------------------------------------------------------------

                 Key: AMQ-3085
                 URL: https://issues.apache.org/jira/browse/AMQ-3085
             Project: ActiveMQ
          Issue Type: Bug
          Components: JMS client
    Affects Versions: 5.4.1
            Reporter: Gary Tully
            Assignee: Gary Tully
             Fix For: 5.5.0


broker returned hosts that are not resolvable on the client can throw the update logic in
the failover transport off. Disabling update works around this (updateURIsSupported=false
on the failover uri). It should be possible to disable the sending on the broker side also.
symptom:
{code}2010-12-10 07:48:16,574 [ActiveMQ Transport: tcp://xx:61616] DEBUG  failover.FailoverTransport:228
- Transport failed with the following exception:
java.io.IOException: Unexpected error occured
	at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:208) ~[activemq-core-5.4.1.jar:5.4.1-fuse-01-00]
	at java.lang.Thread.run(Thread.java:619) [na:1.6.0_12]
Caused by: java.lang.IndexOutOfBoundsException: Index: 12, Size: 11
	at java.util.concurrent.CopyOnWriteArrayList.add(CopyOnWriteArrayList.java:409) ~[na:1.6.0_12]
	at org.apache.activemq.transport.failover.FailoverTransport.add(FailoverTransport.java:613)
~[activemq-core-5.4.1.jar:5.4.1-fuse-01-00]
	at org.apache.activemq.transport.failover.FailoverTransport.updateURIs(FailoverTransport.java:1046)
~[activemq-core-5.4.1.jar:5.4.1-fuse-01-00]
	at org.apache.activemq.transport.failover.FailoverTransport.processNewTransports(FailoverTransport.java:285)
~[activemq-core-5.4.1.jar:5.4.1-fuse-01-00]
	at org.apache.activemq.transport.failover.FailoverTransport.handleConnectionControl(FailoverTransport.java:265)
~[activemq-core-5.4.1.jar:5.4.1-fuse-01-00]
	at org.apache.activemq.transport.failover.FailoverTransport$3.onCommand(FailoverTransport.java:177)
~[activemq-core-5.4.1.jar:5.4.1-fuse-01-00]
	at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
~[activemq-core-5.4.1.jar:5.4.1-fuse-01-00]
	at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:228)
~[activemq-core-5.4.1.jar:5.4.1-fuse-01-00]
	at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83) ~[activemq-core-5.4.1.jar:5.4.1-fuse-01-00]
	at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:219) ~[activemq-core-5.4.1.jar:5.4.1-fuse-01-00]
	at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:201) ~[activemq-core-5.4.1.jar:5.4.1-fuse-01-00]
	... 1 common frames omitted{code}

-- 
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