I don’t think there’s one clear answer to that question. Here’s however a link to infocenter that could be of use to you:

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.base.doc/info/aes/ae/cmj_jmsp.html

The issue is that there’s a breakdown in the simplicity of JMS Queues when the message consumer throws an error (which could be a common case when a transaction arrives during database maintenance). In order to prevent the queue from stopping, you have to figure out where the message that caused the error goes. By default in WPS it’ll go into the Failed Event Manager, where you can resubmit it. My suggestion in the developerworks post was that you could setup another queue instead of the FEM and stick messages that failed due to known common exceptions. Then, when maintenence is complete on the database you have a little MDB that picks the messages off this backup queue and adds them into the real queue.

It’s completely unelegant but there’s not a lot of choice out there.

Would it be possible to publish (or email to me) FEM code you and Trond were discussing?

I have seen you reply also for a similar posrt on devworks:
https://www.ibm.com/developerworks/forums/thread.jspa?messageID=14044278&#14044278
where you suggest JMS queues and MDB, could you please elaborate a bit more on how this would interact with mediation running on WESB and calling service provider?

May be some new great post?

Thank you

Can you expand on the problems you’ve had with the WAS Default JMS Provider?

- Dan

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

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?

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

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.

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?

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.

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.

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.