Hi all, Found the issue that causes VM producer and consumer to "disconnect" in an OSGi environment when a bundle is restarted. It looks like a bug in ServiceSupport#shutdown. See [1].
I filed CAMEL-6072 and CAMEL-6073, but before I commit the patch I'm waiting on some feedback on from the rest of devs, because it's quite a central piece in Camel. Hopefully it'll make it in time for Camel 2.10.4 if the release is not yet staged ;) [1] http://camel.465427.n5.nabble.com/Why-do-we-allow-executing-service-shutdown-logic-twice-or-more-times-tt5727429.html . Regards, *Raúl Kripalani* Apache Camel Committer Enterprise Architect, Program Manager, Open Source Integration specialist http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk <http://twitter.com/raulvk> On Fri, Feb 8, 2013 at 10:13 AM, SteveC <steve.chap...@nz.unisys.com> wrote: > I have 2 camel routes, each deployed in separate bundles to Fuse ESB > (7.0.0.fuse-061). > > Route 1 accepts text via HTTP and send it to a vm queue, e.g. <to > uri="vm:TestQ"/> > > Route 2 accepts input from the vm queue, e.g.. <from uri="vm:TestQ"/>, and > logs a msg. > > Each route is deployed in a Karaf feature and they function correctly on > initial deployement, i.e. I can send a msg via HTTP to route1 and it is > passed to route 2 via the vm queue. > > When I use the Karaf console Bundles page to update the bundle for either > or > both bundles they stop and restart with no apparent errors but from then on > the vm queues are disconnected, e.g. I can send a msg via HTTP to route1 > and > it sends the msg to the vm queue, but route 2 never sees the msg arrive > from > the vm queue and eventually the exchange times out in route 1 (using InOut > MEP). > > Once in this state the only way to get the routes to link via the vm queue > again is to either bounce Fuse ESB or to uninstall/install the associated > features. > > I've tried adding some options to see if behaviour will change but no joy - > tried pollTimeout and concurrentConsumers. > > The only reason for the bundle update is to bounce in new configuration, it > is frustrating having to bounce Fuse ESB just to update the config for a > single bundle. > > I've tried replacing the VM component with JMS i.e. using JMS queues, and > the behaviour is as expected without any problem. > > Advice anyone? > > Thanks > Steve > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/VM-Queues-Disconnected-after-Karaf-Bundle-Update-tp5727205.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
