In a case of something I have never seen before, it appears that PK49507: THE SIBUS RESOURCE ADAPATER WILL NOW INDICATE THAT AN MDB SHOULD BE STOPPED IF A CERTAIN NUMBER OF FAILURES ARE HIT actually requires you to recreate your entire server profile from scratch! It contains the statement:

This property will only be available for new activation
specifications in profiles created after this APAR has been
applied.

This makes the fix completely useless to anyone who actually uses a WebSphere server. The functionality? It adds a new property called ‘maxSequentialMessageFailure’ so that MDBs who use activation specs aren’t also completely useless in the rollback scenario.

All I want is to have this fix so that WebSphere can issue a ‘CWSIV0605W’ message which we can listen for to turn off the delivery of messages to the endpoint. If you can’t turn off the processing, then you have to deal with creating dead letter queues and have a process for putting message back on the queue when they are non-poison. This scenario is discussed further on Bobby Woolf’s Wiki.

I’ve never seen IBM release something called an ‘ifix’ that required you to create a completely new profile. I’m hoping that this is a misinterpretation from the support team. Unfortunately, I have verified with my two eyes that a server who has a preexisting profile and then upgraded does not see it.