qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-6099) Closing a 0-8..0-9-1 connection with an exceptions whose message exceeds 255 characters leads to unexpected Broker shutdown
Date Mon, 15 Sep 2014 10:33:33 GMT

     [ https://issues.apache.org/jira/browse/QPID-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Keith Wall updated QPID-6099:
-----------------------------
    Description: 
If an unexpected exception occurs within the Broker whilst processing on behalf of a messaging
client, the exception text is sent to the client as part of the connection.close frame.  However,
if the exception message is longer than 255 characters, this leads to an unexpected Broker
shutdown and the following exception:

{noformat}
2014-09-15 11:10:07,574 ERROR [IoReceiver - /192.168.0.1:51612] (thread.LoggingUncaughtExceptionHandler)
- Uncaught exception in thread "IoReceiver - /192.168.0.1:51612"
java.lang.IllegalArgumentException: Cannot create AMQShortString with number of octets over
255!
       at org.apache.qpid.framing.AMQShortString.<init>(AMQShortString.java:147)
       at org.apache.qpid.framing.AMQShortString.<init>(AMQShortString.java:133)
       at org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.exception(AMQProtocolEngine.java:1356)
       at org.apache.qpid.server.protocol.MultiVersionProtocolEngine.exception(MultiVersionProtocolEngine.java:138)
       at org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:217)
       at java.lang.Thread.run(Thread.java:745)
{noformat}

The Broker must be restarted to resume normal operations.

This was seen to occur when using BDB HA with a long environment path name, as JE commonly
includes the environment path within the text of its exceptions.

  was:
If an unexpected exception occurs within the Broker whilst processing on behalf of a messaging
client, the exception text is sent to the client as part of the connection.close frame.  However,
if the exception message is longer than 255 characters, this leads to an unexpected Broker
shutdown and the following exception:

{noformat}
2014-09-15 11:10:07,574 ERROR [IoReceiver - /192.168.0.1:51612] (thread.LoggingUncaughtExceptionHandler)
- Uncaught exception in thread "IoReceiver - /192.168.0.1:51612"
java.lang.IllegalArgumentException: Cannot create AMQShortString with number of octets over
255!
       at org.apache.qpid.framing.AMQShortString.<init>(AMQShortString.java:147)
       at org.apache.qpid.framing.AMQShortString.<init>(AMQShortString.java:133)
       at org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.exception(AMQProtocolEngine.java:1356)
       at org.apache.qpid.server.protocol.MultiVersionProtocolEngine.exception(MultiVersionProtocolEngine.java:138)
       at org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:217)
       at java.lang.Thread.run(Thread.java:745)
{noformat}

The Broker must be restarted to resume normal operations.


> Closing a 0-8..0-9-1 connection with an exceptions whose message exceeds 255 characters
leads to unexpected Broker shutdown
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-6099
>                 URL: https://issues.apache.org/jira/browse/QPID-6099
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>            Reporter: Keith Wall
>            Priority: Critical
>
> If an unexpected exception occurs within the Broker whilst processing on behalf of a
messaging client, the exception text is sent to the client as part of the connection.close
frame.  However, if the exception message is longer than 255 characters, this leads to an
unexpected Broker shutdown and the following exception:
> {noformat}
> 2014-09-15 11:10:07,574 ERROR [IoReceiver - /192.168.0.1:51612] (thread.LoggingUncaughtExceptionHandler)
- Uncaught exception in thread "IoReceiver - /192.168.0.1:51612"
> java.lang.IllegalArgumentException: Cannot create AMQShortString with number of octets
over 255!
>        at org.apache.qpid.framing.AMQShortString.<init>(AMQShortString.java:147)
>        at org.apache.qpid.framing.AMQShortString.<init>(AMQShortString.java:133)
>        at org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.exception(AMQProtocolEngine.java:1356)
>        at org.apache.qpid.server.protocol.MultiVersionProtocolEngine.exception(MultiVersionProtocolEngine.java:138)
>        at org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:217)
>        at java.lang.Thread.run(Thread.java:745)
> {noformat}
> The Broker must be restarted to resume normal operations.
> This was seen to occur when using BDB HA with a long environment path name, as JE commonly
includes the environment path within the text of its exceptions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message