BUG-3219: Fix OutboundQueue cleanup on channel failure 68/20968/1
authorRobert Varga <rovarga@cisco.com>
Sun, 17 May 2015 01:11:00 +0000 (03:11 +0200)
committerMichal Polkorab <michal.polkorab@pantheon.sk>
Fri, 22 May 2015 11:01:21 +0000 (13:01 +0200)
commitaa13d46568a13f9d73f9ea90b2c14211b473dde6
tree76d9c2ae73f9405829894a5016304b62f3e7b49c
parent20ac1113a590c3067f755a9508f915898b0185c7
BUG-3219: Fix OutboundQueue cleanup on channel failure

When the channel goes inactive, we still need to make sure that any
entries that were reserved and not committed get flushed. Instead of
perfoming a one-shot cleanup in channelInactive(), perform cleanup
whenever flush() runs.

When channel goes inactive, we just cleanup the obviously-freeable
resources and ensure that a flush is scheduled.

Change-Id: I48e1ceb51dcfafedb7352db5d952e9749cdfa50d
Signed-off-by: Robert Varga <rovarga@cisco.com>
(cherry picked from commit 44b028491689d8d89c2ffea2e7bc6bb2d80209fe)
openflow-protocol-impl/src/main/java/org/opendaylight/openflowjava/protocol/impl/core/connection/OutboundQueueEntry.java
openflow-protocol-impl/src/main/java/org/opendaylight/openflowjava/protocol/impl/core/connection/OutboundQueueImpl.java
openflow-protocol-impl/src/main/java/org/opendaylight/openflowjava/protocol/impl/core/connection/OutboundQueueManager.java