qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sreeram Garlapati (JIRA)" <j...@apache.org>
Subject [jira] [Created] (PROTON-1939) NullPointerException while handing remote session.begin in TransportImpl
Date Fri, 21 Sep 2018 21:33:00 GMT
Sreeram Garlapati created PROTON-1939:
-----------------------------------------

             Summary: NullPointerException while handing remote session.begin in TransportImpl
                 Key: PROTON-1939
                 URL: https://issues.apache.org/jira/browse/PROTON-1939
             Project: Qpid Proton
          Issue Type: Bug
          Components: proton-j
    Affects Versions: proton-j-0.29.0
         Environment: Any environment
            Reporter: Sreeram Garlapati
             Fix For: proton-j-0.30.0


Our library (Microsoft Azure EventHubs java sdk) take a dependency on proton-j library for
AMQP implementation.

Many of Our customers are reporting this issue and would highly appreciate your response.

 

We are basically hitting this TODO in the TransportImpl.java - which results in reactor teardown:

[https://github.com/apache/qpid-proton-j/blob/master/proton-j/src/main/java/org/apache/qpid/proton/engine/impl/TransportImpl.java#L1160]

 

Here's the Exception stack trace:

 

{color:#24292e}com.microsoft.azure.eventhubs.impl.MessagingFactory$RunReactor.run:487 messagingFactory[MessagingFactoryab1d8d],
hostName[NNNNNNNNNNN.servicebus.windows.net], error[UnHandled exception while processing events
in reactor:{color}
{color:#24292e} java.lang.NullPointerException: uncorrelated channel: 3{color}
{color:#24292e} org.apache.qpid.proton.engine.impl.EventImpl.dispatch(EventImpl.java:112){color}
{color:#24292e} org.apache.qpid.proton.reactor.impl.ReactorImpl.dispatch(ReactorImpl.java:324){color}
{color:#24292e} org.apache.qpid.proton.reactor.impl.ReactorImpl.process(ReactorImpl.java:292){color}
{color:#24292e} com.microsoft.azure.eventhubs.impl.MessagingFactory$RunReactor.run(MessagingFactory.java:462){color}

 

here's how to reproduce this error:
 * configure the listener - to delay respond to session.begins for ex: by 5 secs
 * then client (or another peer) sends session.begin
 * client doesn't receive any response even after 1 sec
 * then the client decides to close the session
 * then, after few sec's service(listener) responds back with session.begin

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message