Bug 5118 - Unsent messages reported as failed after disconnect 26/35726/1
authorMichal Polkorab <michal.polkorab@pantheon.sk>
Wed, 27 Jan 2016 01:08:19 +0000 (02:08 +0100)
committerThanh Ha <thanh.ha@linuxfoundation.org>
Fri, 4 Mar 2016 04:03:29 +0000 (23:03 -0500)
commit6af0ea88a438a5132590be1bbe66c5a76b2765ac
tree59a0f9ad695d67052f8e9f5d7ed50776f06d3522
parent8b1d7f2c6ad97a94870c4e32210fa772e5e33b99
Bug 5118 - Unsent messages reported as failed after disconnect

 - if there were messages delivered to OutboundQueue and disconnect occured,
   unsent messages were not marked as failed, resulting in incorrect / no report
 - channelInactive in AbstractOutboundQueueManager was never triggered as the event
   was consumed in DelegatingInboundHandler

Change-Id: Iaaffbbe14feaec4afbda0a3d6b19699c1ec79e06
Signed-off-by: Michal Polkorab <michal.polkorab@pantheon.sk>
(cherry picked from commit 25677520a3fca1a925a0970efa20d586e1445e6f)
openflow-protocol-impl/src/main/java/org/opendaylight/openflowjava/protocol/impl/core/PipelineHandlers.java
openflow-protocol-impl/src/main/java/org/opendaylight/openflowjava/protocol/impl/core/connection/AbstractOutboundQueueManager.java
openflow-protocol-impl/src/main/java/org/opendaylight/openflowjava/protocol/impl/core/connection/AbstractStackedOutboundQueue.java
openflow-protocol-impl/src/main/java/org/opendaylight/openflowjava/protocol/impl/core/connection/ConnectionAdapterImpl.java