We’re battling another runtime problem. We’re on 184.108.40.206 and WAS 220.127.116.11 and have a situation where our modules that enable Event Sequencing seem to deadlock when trying to pick messages up off the queue. The transactions then time-out in a sea of exceptions. We have a messaging engine cluster (set to 1 of N) and a two-node SCA cluster (M of N). It seems like the SCA cluster just can’t do anything on the messaging engine.
We’re working with IBM Support on this one. I know that there are a ton of APARs about SIBus contained in WAS 18.104.22.168 and WAS 22.214.171.124 that seem like they MAY fix the issue, but jurisprudence won’t allow us to just upgrade without assured resolution.