We use a trigger with these settings:
processing mode: “concurrent”
max execution thread: 10
When we deliver the package containing this trigger, on the target the trigger appears “not connected” in the client list of the WmBrokerAdmin of the target IS, and indeed, it doesn’t catch any published document.
The solution we have found is to set the trigger to “serial”, then back to “concurrent”, and after that everything works…
Is there an explanation for this?
By the way, we use IS 6.1 and Broker 6.5