As this has cropped up a couple of times recently and, as far as I’m aware, there is still no information in the public domain, I thought I’d stick my neck out and post about it. WebSphere Integration Developer allows you to add an event sequencing qualifier to components in a mediation module but the required runtime support for that qualifier only exists in WebSphere Process Server not in WebSphere ESB. In other words, for that qualifier to work, the mediation module must then be deployed to WebSphere Process Server.
At the latest customer, this lack of support manifested itself in the following way (in case you should come across this problem). Firstly, a warning with the following text:
CWSCA0001W: "jar:file:/<profile directory>/installedApps/<app name>/<ear name>.ear/<jar name>.jar|/<component name>.component" is not a valid Service Component Definition Language file for the following reason: "org.eclipse.emf.ecore.xmi.PackageNotFoundException: Package with uri 'http://www.ibm.com/xmlns/prod/websphere/wbiserver/eventSequencing/6.0.0' not found.
This was then followed by an exception
CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "onNotification" on bean "BeanId(<app name>#<jar name>.jar#<export name>, null)". Exception data: java.lang.NullPointerException at com.ibm.wsspi.sca.j2c.inbound.J2CInboundImpl.invoke(J2CInboundImpl.java: 242)
A tech note now exists confirming this lack of support.
This was correct prior to V7, but support has now been added
Thanks for providing this update Callum.
I have WESB 6.2.0.2 and I know that this version not support event sequencing. but still need to do it.
I have set the maxConcurrency=1 of my mediaiton module, created a listener and set “Maximum sessions” and “Maximum messages” to 1 , but when I look at the log, I still see threads running concurrently.
appreciate your help. btw I am reading messages from MQ.
Sorry for the slow response. The chances are that the messages are getting copied from your MQ queue to an internal SIB queue which is the point at which they are being processed concurrently. You could try setting the maximum concurrency of the activation spec but this isn’t supported and you would have to do it every time you reinstall the application. Move to Version 7!