Re-sending messages
Hello,
today I made a similar test. I tried to test the behavior with big files.
I tried to send a file with 50 MB encrypted to an other partner. The connection between the two partners are a standard 100 MBit/s LAN.
The result of the test was, that the sender tries to send the message and the sender startes to process the incoming message. Then something strange happens. The sender reports an error and the receiver gots the message 3 times and processed it in all cases. So the receiver gots the message 3 times successfully and the sender quits after a while with the message SocketException or something.
I don't have the logs on this maschine so I'll post the logs later to get a more detailed report.
One way is to build a script that would move all of the messages from the error folder to the outbox folder. But I've one question, should all the messages placed on the error folder be reprocessed again?
Can the application be altered to add this functionality?
Thanks
Mourovaz,
Resending isn't available in the application so far. But the script idea sounds good to me. Resending is a feature we definitly have to add to the next release.
@Tobias
A log would be really great because such a behavior hasn't been noticed before and we are really interested in what happened there.
Regards
Heller
hi all,
i would really appreciate a resend mechanism too. e.g. try 3 times with 15 minutes between the attempts then put into error dir.
what would be interesting too for me is to keep the original filename when it goes to the error dir would this be a problem?
regards chris
hi heller,
i did not get your point...
do mean that mec should be responsible for this? or the system above?
if the system above (not mec) --> it would be really helpful if mec keeps the filenames as they are in error dir. or to have an option for this.
regards chris
© 1999-2007 mendelson-e-commerce GmbH. All right reserved.
Hi guys,
I've been testing how the application behaves in crash cases...
Imagine you have a scenario where you send a message to your partner but for some reason (communication, server down...whatever) he doesn't receive it.
Well, the application starts to pick the message placed at the outbox folder, processes it and transforms it in a as2 message. When the other partner doesn't receive the message, a new message is created and placed at the error folder.
My question is, does the application contains any kind of reprocessing mechanism? How can I retry sending the message which was placed at the error folder?
This is really important because it is a very likely scenario....
Do you guys have any suggestions?