TN sending 16 old EDIINT messages for no reason

While we shutdown and start webMethods server during monthly maintain, TN sending 16 old EDIINT messages. these EDIINT message are changed User Status from ‘SendMsg:DONE’ to ‘SendMsg:WAITMDN’

We took a look at Activity log and found someone processed these tasks again to resend these EDIINT for no reason. Is this a system bug? Any suggestion? Thanks advance.

They resend behind your EDIINT message changed from sendMSG:waitMDN , After those resent EDIINT Message to your partner and received the MDN with different ID and your parent EDIINT message could not be able to correlate the received MDN and status could not be able to update to Done in this case.

  1. kindly find the resend behind the resend of your EDIINT message.
  2. Try to get the existing status of the 16 Message in your system before system restart.
  3. Is this your first occurrence , are your seeing these message are resend everytime server restarts.

Hi Dinesh,
You are right. From this April until now, TN resent EDIINT for no reason while server restarted. AS2 sender and receiver are different like below.

Hi Dinesh,
The User Status of these resent EDIINT are ‘SendMsg:DONE’ before resending by TN.

Is that message are processed via scheduled EDIINT queue based delivery ?

if so was there any changes happened to the delivery Queue Name recently , Can you check if those resend message are hung for some reasons in those queue or default queue.

if it not queue. Request you to identify those message and check was there any environment changes during that time is causing this issue ? Also create support team to under this behavioral

Hi Dinesh,
We invoke wm.EDIINT:send to send the EDIINT message.

The Task Retries is 0. The AS2 receiver will receive 2 EDIINT messages with the same message ID.

Hi rocky,

normally the data are send by scheduler or port, if the old messages will be sent every time when the server restart, please check the following

  1. check the data availability, if behind have a scheduler or port to pick up the data and send EDIINT message, check whether the port or scheduler are pickup from the backup or old folder path, which cause the server sending the old data. If the data is pickup by using adapter and SQL, check whether the sql is correct.

  2. check the flow services to send the EDIINT message, sometime the debug branch/ restorefilefrompipeline will affect the transaction.

  3. can have checking on the trigger service , processing rules configuration which relate to the EDIINT sending.

Hope this could help you. Thanks

Hi Foo,
Thanks for reply.
According to activity log of MWS:

  1. 8/12 service invoke sendMsg (We invoke wm.EDIINT:send to send the EDIINT message), then processing task xxxx54an and delivery successfully.
  2. 8/15 We shutdown and start webMethods server during monthly maintain, then processing task xxxx54an again for no reason.
    Why did this task xxxx54an delivery 2 times? Any suggestion is welcome.

Hi Foo,
The data is sent by the scheduler. Why does the same task deliver 2 times? If you send an EDIINT message with a MDN reply, then the same task will not resend.

rockylee * via Software AG Tech Community & Forums <> 於 2021年10月13日 週三 下午3:46寫道:

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.