[diff attached] Passing TopologyEvent data to cartridge agent extensions (was: Re: Topology inconsistent)

2015-04-30 Thread Michiel Blokzijl (mblokzij)
Hi,It looks like this isn’t an issue in the latest 4.1 code, so that’s good.However, in the 4.1 code we’ve lost the ability to pass data about topology events to the extensions run by the cartridge agent. I’ve attached a diff which shows how I would add this functionality back. Basically I’d extend

Re: Topology inconsistent

2015-04-22 Thread Imesh Gunaratne
Hi Michiel, In JCA topology is handled by the messaging module, you could see how topology is updated on Complete Topology event here: https://github.com/apache/stratos/blob/master/components/org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/message/processor/topology/Complet

Re: Topology inconsistent

2015-04-22 Thread Michiel Blokzijl (mblokzij)
Hi Imesh, > Ideally cartridge agent should only wait for Complete Topology event once in > its lifecycle. If it is waiting more than once then there is an issue. That’s not the problem, it only waits once for the complete topology. To me it looks like the topology is never updated, or if it is

Re: Topology inconsistent

2015-04-20 Thread Imesh Gunaratne
Hi Michiel, It's a pleasure! My guess is that either cartridge agent has been restarted or there is a bug in its logic. Ideally cartridge agent should only wait for Complete Topology event once in its lifecycle. If it is waiting more than once then there is an issue. Thanks On Mon, Apr 20, 2015

Re: Topology inconsistent

2015-04-20 Thread Michiel Blokzijl (mblokzij)
HI Imesh, Thanks for replying, > This issue might occur if the cartridge agent start processing member events > before consuming Complete Topology event. The issue happened way after that, I had Stratos running for a day or so, and in the logs I saw some “waiting for complete topology event .

Re: Topology inconsistent

2015-04-20 Thread Imesh Gunaratne
Hi Michiel, This issue might occur if the cartridge agent start processing member events before consuming Complete Topology event. This is how the topology get initialized in any component that listen to topology topic in message broker; First of all when the component starts up it waits for the

Topology inconsistent

2015-04-20 Thread Michiel Blokzijl (mblokzij)
Hi, I’m looking at an issue with Stratos 4.0.0 code, and I’m having an issue with the cartridge agent. It complains about the topology being inconsistent, triggered by this code [1]. This causes the extension handler not to fire for cartridges going down. [2015-04-19 07:19:22,486] INFO - [Memb