Comments on: Event Sequencing Message Locking - Resolution!

By: Mannie Kagan

Mannie Kagan — Mon, 21 Jul 2008 17:01:41 +0000

Dan, Please contact Sunita about this. (Jeff B says you’re the worst volley-ball player he has ever seen.)

By: Chris Holding

Chris Holding — Wed, 02 Jul 2008 14:30:41 +0000

I am working on the same project as Vijita. We have hit several different issues with the SI Bus and SCA due to our topologyb (multiple ME clusters in one cell). We have had to play around with targetSignificance etc for activation specs and connection factories. This seems to be because the underlying SI Bus does not like the use of remote puts and gets which is part of the default behaviour of WAS and WPS.

We have had to tie our connection factories and activation specifications to specific ME’s so that they always connect to the one which hosts the queue points and do not try to use remote puts/ gets.

Unfortunately, the SCA does not then honour the settings and so a further fix is required to sort that out.

We have also had to load the system up with fix packs and we are now looking at WPS 6.0.2.4 plus fixes to resolve our issues.

So far we have spent about 2 months trying to resolve these issues….

Regards
Chris

By: dan

dan — Thu, 26 Jun 2008 13:25:51 +0000

Hi Vijita,

I am glad that you were able to find your issue in PREproduction and not POST like we did :). As a side note we ran into another instance where event sequencing messages lock. I believe there is both an sibus (was) ifix and wps event sequencing fix coming out, so be aware.

By: Vijita L

Vijita L — Thu, 26 Jun 2008 09:01:43 +0000

I am sorry, that is WPS V6.0.3 and WAS V6.0.2.25

By: Vijita L

Vijita L — Thu, 26 Jun 2008 08:37:55 +0000

Hi,
This is a good one..!
We have encountered similar problem on our pre-production cluster, and we seem to have resolved the same.
Our current version of process servers is 6.0.2.25.

Cheers..