qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-8180) [JMS AMQP 0-8..0-91] Improve error message associated with the channel not found during frame dispatch
Date Fri, 04 May 2018 15:04:00 GMT

    [ https://issues.apache.org/jira/browse/QPID-8180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463985#comment-16463985

ASF subversion and git services commented on QPID-8180:

Commit 4e127c21159c2bdd69f55ff8b4e087f2fb264bf5 in qpid-jms-amqp-0-x's branch refs/heads/6.3.x
from [~k-wall]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms-amqp-0-x.git;h=4e127c2 ]

QPID-8180: [Qpid JMS AMQP 0-8..0-91] Improve error message used to handle a channel not found
condition during frame dispatch.

(cherry picked from commit e4e2b6b206c8d232f01a7527a0a884abb957be53)

> [JMS AMQP 0-8..0-91] Improve error message associated with the channel not found during
frame dispatch
> ------------------------------------------------------------------------------------------------------
>                 Key: QPID-8180
>                 URL: https://issues.apache.org/jira/browse/QPID-8180
>             Project: Qpid
>          Issue Type: Improvement
>          Components: JMS AMQP 0-x
>    Affects Versions: 0.32
>            Reporter: Keith Wall
>            Assignee: Keith Wall
>            Priority: Minor
>             Fix For: qpid-java-client-0-x-6.3.1
> A defect report against a 0.32 derivative client included a seemingly spontaneous  NullPointerException
stack trace whilst the IOReceiver was processing an incoming content.body frame.  There is
no indication that the underlying channel had been closed.
> {noformat}
> 2018-05-01 15:30:27.914 ERROR Exception processing frame                            
> java.lang.NullPointerException: null
>                 at org.apache.qpid.client.protocol.AMQProtocolSession.deliverMessageToAMQSession(AMQProtocolSession.java:290)
~[qpid-client-x.x.x.jar: x.x.x]
>                 at org.apache.qpid.client.protocol.AMQProtocolSession.contentBodyReceived(AMQProtocolSession.java:272)
~[qpid-client- x.x.x.jar: x.x.x]
>                 at org.apache.qpid.framing.ContentBody.handle(ContentBody.java:72) ~[qpid-common-
x.x.x.jar: x.x.x]
>                 at org.apache.qpid.client.protocol.AMQProtocolHandler.received(AMQProtocolHandler.java:492)
[qpid-client- x.x.x.jar: x.x.x]
>                 at org.apache.qpid.client.protocol.AMQProtocolHandler.received(AMQProtocolHandler.java:120)
[qpid-client- x.x.x.jar:5.1.8]
>                 at org.apache.qpid.client.AMQConnectionDelegate_8_0$ReceiverClosedWaiter.received(AMQConnectionDelegate_8_0.java:538)
[qpid-client- x.x.x.jar: x.x.x]
>                 at org.apache.qpid.client.AMQConnectionDelegate_8_0$ReceiverClosedWaiter.received(AMQConnectionDelegate_8_0.java:524)
[qpid-client- x.x.x.jar: x.x.x]
> {noformat}
> Attempts to reproduce the problem have so far been unsuccessful. Improving the error
message used in this situation should help a future investigation, if it occurs again.

This message was sent by Atlassian JIRA

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

View raw message