Comments on: WebSphere Default Messaging (SIBus) and WebService Error Handling

By: Rajesh_sk

Rajesh_sk — Tue, 21 Oct 2008 10:08:58 +0000

Hi Trond,

Can you please elaborate on how exactly I can deactivate the J2Cactivation spec in runtime?

By: Trond

Trond — Tue, 21 Oct 2008 08:48:45 +0000

It’s pretty amazing that the solution for throttling message processing is based on having to create a custom application that reads error messages from a log file and then invokes server administrative features to stop the activation spec. Why didn’t they make this declarative…?!

By: Rajesh_sk

Rajesh_sk — Thu, 16 Oct 2008 06:46:23 +0000

Hi Dan,

Thanks for the inputs.
This fixpack is to enable the property on the J2CActivation specification.
I am using WID 6.1.2 which has WAS version of 6.1.0.17. I can see that this property is already enabled in this version. The only problem is that I am not able to bring that to effect.
I am able to set value for ‘maxSequentialMessageFailure’ property but I am not able to change the ‘Required’ column to ‘true’ in the customProperties tab of J2CActivation specification.

Have you got any idea about this?

By: dan

dan — Tue, 14 Oct 2008 20:03:06 +0000

You’ll need to pause the Activation Spec listener once your system has detected that a transaction rollback is required. Or else you will find that your transaction rollsback and it immediately re-tried for n times until it ends up in the excpetion destination.

http://www.ibm.com/developerworks/wikis/display/woolf/Pausing+SIBus+MDBs

By: Rajesh_sk

Rajesh_sk — Mon, 13 Oct 2008 15:20:43 +0000

Hi Dan,

We have a small scenario in our project where in we are using JMS Queue (SIB)to send and receive soap messages (soap over JMS).
Listener picks up the message and invokes the service.
If I have any problem (specific errors) while processing the request I want to rollback the message to the same queue and end the process.
I don’t find any way to rollback the message. The message is lost when a runtime exception (unhandled) occurs.
Do you have any idea on how I can do this.
Thanks in advance.

By: David L

David L — Wed, 23 Jul 2008 06:21:59 +0000

Nice job, can you email me code too? thanks

By: Chris Holding

Chris Holding — Wed, 02 Jul 2008 14:20:34 +0000

One way to handle this type of situation is:
Check availability of destination. If it is not available, set a flag in say a relationship to divert the data to a persistent store. When the destination system is restored, reset the flag and process the backlog in the persistent store (I have used a DB for this).

By: Trond Isaksen

Trond Isaksen — Wed, 25 Jun 2008 16:27:18 +0000

You have mail

By: dan

dan — Wed, 25 Jun 2008 13:57:37 +0000

Hi Trond,

Of course I’m interested in the code Awesome that you got that all up and working. Are you on the 6.1 level? We are at 6.0.2 maybe thats why you were able to get it going so quickly.

And yes, I agree that the Failed Event Manager is a ‘last resort’ location but an integration platform should be able to deal with the common pattern of retrying “out of the box”. How about a new set of properties on an activation spec that define “Business Hours”, Retry Delay etc?

By: Trond

Trond — Tue, 24 Jun 2008 13:51:54 +0000

Dan,
Just tried it, and it seems to work pretty good. It is possible to get the business object (use the “getFailedEventWithParameters” method on the FailedEventManagerEJB), but it is not necessary. I simply search for failed events using the FailedEventManagerEJB, look through the failure exception/type/date, and invoke resubmit() on the FailedEvents that are candidates. I’ll send you the code if you want it

My gut feeling, however, still is that there should be a resubmit queue that handles downtime/scheduled unavailability. That means that each backend system will have its own independent resubmit-handler. I’m not too happy about using the FEM for this.

By: dan

dan — Mon, 23 Jun 2008 14:49:25 +0000

Hi Trond,

Yeah, it’s a very common pattern that I was surprised is so difficult to implement.

From what I have heard from a developer who attempted to use the FEM API to get a handle to the business object contained in the event and he said he was unable to get it (or that there was no method). So if you get something like this working, it’d be awesome to let me know.

Cheers.

By: Trond Isaksen

Trond Isaksen — Mon, 23 Jun 2008 07:23:51 +0000

Hi,
we have pretty much the same challenge. I would be surprised if we are the only ones that want support for automatic retries against backend-systems…so I believe this should be better handled by WPS. FEM is to me a good last-resort queue, but typically not a good structure for holding messages while systems are down.
We have also considered the JMS-solution. I believe it should be feasible. Outside of business hours I expected that it should be OK to check the time, roll back the message, sleep, and retry later.

However, we are currently pursuing to use the FEM API for automatic resubmit (having a batch job look through failed messages and decide which ones should be resubmitted). We’ll se if this turns out OK.