BUG-3219: Fix OutboundQueue cleanup on channel failure 17/20617/5
authorRobert Varga <rovarga@cisco.com>
Sun, 17 May 2015 01:11:00 +0000 (03:11 +0200)
committerRobert Varga <rovarga@cisco.com>
Mon, 18 May 2015 01:12:37 +0000 (03:12 +0200)
commit44b028491689d8d89c2ffea2e7bc6bb2d80209fe
tree7ae645969cd0bb1c1d0c40aed5c8797e77907a20
parent763e430f61196740c5ea1c7356022396adf55065
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>
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