Comments on: WebSphere Process Server: Messages sitting on queues unprocessed http://blog.danzrobok.com/2008/06/12/websphere-process-server-messages-sitting-on-queues-unprocessed/ Business Integration and SOA with an IBM WebSphere slant Sat, 10 Jan 2009 01:17:03 +0000 http://wordpress.org/?v=2.6.3 By: Chris Holding http://blog.danzrobok.com/2008/06/12/websphere-process-server-messages-sitting-on-queues-unprocessed/#comment-413 Chris Holding Wed, 02 Jul 2008 15:17:44 +0000 http://blog.danzrobok.com/2008/06/12/websphere-process-server-messages-sitting-on-queues-unprocessed/#comment-413 We had an issue where we were using event sequencing in an environment which contained 2 WPS nodes, each running on a local ME. The event sequencing modules were only deployed on one server. Depending on the order of server startup, the event sequencing either worked or did not work. If the server which did not host the event sequencing modules was started first, ES failed to run because it started up on the wrong server. Also if the server which ES modules ran on was restarted, leaving the other one running, ES failed over to the other server and could not run because it could not see any destinations. When the server hosting the ES modules was restarted, the non ES server also had to be restarted so that the event sequencing failed back to the correct server. There is a fix for this now. We had an issue where we were using event sequencing in an environment which contained 2 WPS nodes, each running on a local ME. The event sequencing modules were only deployed on one server. Depending on the order of server startup, the event sequencing either worked or did not work.

If the server which did not host the event sequencing modules was started first, ES failed to run because it started up on the wrong server.

Also if the server which ES modules ran on was restarted, leaving the other one running, ES failed over to the other server and could not run because it could not see any destinations.

When the server hosting the ES modules was restarted, the non ES server also had to be restarted so that the event sequencing failed back to the correct server. There is a fix for this now.

]]>