on 03-31-2016 9:17 AM
Hi,
Receiver channel has error as below. I tested mapping with message pay load, no error in it. I done ping channel it is successful. I tried to resend the message but same error. I done cache refresh to this channel then I tried to resend but no improvement. I restarted channel and i resend the message but no use.Suggest me any tool that i can test SOAP url (It is on production).
Integration Info
Proxy --> po --> SOAP
QoS :: EOIO
No SOAP action
No authentication
No module on receiver channel(Required module for sender proxy are added)
Below is the error snapshot. i attached channel snapshot.
Hi Charan,
Check with your third party users.Seems there system might be down.
Even we faced the same issue,when we reported to end user they informed that the server was down,once the server is re-started we were able to send the messages.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Charan,
We got the same error in different channel but only one message got this error.And rest of the messages delivered successfully.
Therefore undoubtedly the problem is for the data inside the payload. Check it against the successfully one: any tag missing or a new one, any currency or date tag different, even the problem could be functional, you can send a register that in the endpoint raises an exception: duplicated, inconsistency in any reference to another registers in the endpoint and so on.
The first part you can check it, the second one you have to contact with endpoint maintenance team.
Regards.
Hi charan,
Is this error only for some messages or every message is failing?
was this interface working fine till now and suddenly stopped working?
Is the channel ping of soap receiver fine?
If answer to all the above question is yes then the reason is you are not getting proper response from receiver may be no response at all or not in proper format for those particular messages ask someone to debug in the receiving system.
Regards
Vinay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Charan,
The http 500 can be raised to multiple causes. For example, a tag missing, wrong namespace, currency with wrong format, date with wrong format, etc. In the endpoint this exception is raised because it can't process the message. Could you reproduce the message in quality environment and to follow Eng suggestion?, could you try to test with SOAPui?
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.