This content has been marked as final. Show 3 replies
Are you executing the WS through SOAP/JMS (best practice) or using a Java automator over HTTP(s)?
In general, if an exception happens within an automator and the transaction rolled back, this will cause JMS to redeliver the same internally generated message that initiates the automation plugin so that the transaction can be retried. Could perhaps an exception be happening within your plugin?
I am executing it using a Java automator over HTTP.
Thanks for your help.
Likely then that you are throwing an exception which is triggering JMS redelivery which is causing the Java automator to fire again.