Moving the Connection events to its own executorService thread. 14/8714/1
authorMadhu Venugopal <mavenugo@gmail.com>
Mon, 7 Jul 2014 01:26:49 +0000 (18:26 -0700)
committerMadhu Venugopal <mavenugo@gmail.com>
Mon, 7 Jul 2014 01:40:49 +0000 (18:40 -0700)
commit3e871a4ac0acabd06a23903509f861acf34f06d4
treed458122b1e53d058fb930ad6765b0ffccbe5a178
parent96e24a89ed2a058168a8291121bcdc3ed3de799b
Moving the Connection events to its own executorService thread.

During the neutron integration it is observed that connection events are immediately followed by OVSDB table
configuration events and causes a similar channel lock issue that we faced recently. Hence moving it in its
own thread to avoid the Channel locking issue.

Change-Id: Ibcf147e0ff107aecfcb7987956055f563a5a17a0
Signed-off-by: Madhu Venugopal <mavenugo@gmail.com>
library/src/main/java/org/opendaylight/ovsdb/lib/impl/OvsdbConnectionService.java