Bug 5118 - Unsent messages reported as failed after disconnect 83/35683/1
authorMichal Polkorab <michal.polkorab@pantheon.sk>
Wed, 27 Jan 2016 01:08:19 +0000 (02:08 +0100)
committerMichal Polkorab <michal.polkorab@pantheon.sk>
Thu, 3 Mar 2016 13:10:34 +0000 (13:10 +0000)
commit3183810b0ec6075f1cf0d2752f8f488916d29acc
tree691257a9ea0da56f9db8e890bfaf0a4aaf9b4325
parent3a9dc6618aac4d9d498d91d1a7fb240619ddcc39
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: Ifd64c8f9346534a934d49a88ddd5c8f71cbb01e7
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