StringIndexOutOfBounds when formating Connection Message during failed systest 
run.
-----------------------------------------------------------------------------------

                 Key: QPID-2137
                 URL: https://issues.apache.org/jira/browse/QPID-2137
             Project: Qpid
          Issue Type: Bug
          Components: Java Tests
            Reporter: Martin Ritchie
            Priority: Minor


This problem occured during a run of systests in the 
AcknowledgeAfterFailoverOnmessageTest. The test failed with a concurrent 
modification exception. However prior to that a StringIndexOutOfBounds during 
client connection establishment occured
Then shortly afterwards a NullPointerException occured and repeated a number of 
times. 

Most likely what occured is the failed connection open was not correclty closed 
by mina and so the attempts to send on the socket resulted in the NPEs.

Then the ConcurrentModException occured potentially as a result of a new 
getConnection() being called asynchronously via the onMessage when the close() 
was being called.

Dispatcher-Channel-1 2009-10-12 16:25:36,694 ERROR 
[qpid.server.protocol.AMQPFastProtocolHandler] Exception caught 
inanonymous(17670761)(?, closing session explictly: 
java.lang.StringIndexOutOfBoundsException: String index out of range: 37
java.lang.StringIndexOutOfBoundsException: String index out of range: 37
        at java.lang.String.substring(String.java:1934)
        at java.text.MessageFormat.subformat(MessageFormat.java:1208)
        at java.text.MessageFormat.format(MessageFormat.java:836)
        at java.text.Format.format(Format.java:140)
        at 
org.apache.qpid.server.logging.messages.ConnectionMessages.CON_1001(ConnectionMessages.java:141)


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


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to