We have IS6.5. I updated one trigger from serial processing mode to concurrent processing mode. After I deployed the pkg this trigger is in to another integration server, this trigger got disconnected to the broker associated with the second integration server. So the trigger service did not get invoked.

Did I miss something when changing this trigger processing mode?

Thanks

Do you have an error while loading the package ?

like :Unable to create Broker Transport XXXXXX. Exception com.wm.app.b2b.server.dispatcher.exceptions.EndpointUnavailableException: [ISS.0098.9014] BrokerException: Client Contention (201-1034): Cannot reconnect client ‘XXXXXXXXXXX’. Cannot change shared document ordering property while reconnecting to an existing client.

To enable the change of the processing mode of a trigger from serial to concurent you need to:

• disable the trigger
• delete the broker client associated via BrokerAdmin or Portal
• enable the trigger.

That’s why, I think, the best thing to do when you create a trigger is to set it to concurrent 1 instead of serial.