on 08-09-2010 8:50 AM
Hello forum,
for some weeks we have a strange problem with some messages. They will not go through the SOAP-adapterand if I go to the "Message Display Tool" via Message Monitoring, and try to see the message payload it says "Internal Server Error". The "details" are
Error javax.servlet.ServletException: null, with root cause java.lang.NullPointerException: null.
Is there a way to see the full stack trace? Or some more server logs?
Regards
Christian
Christian,
It might be due to bad data for which target system is unable to send back the response resulting in timeout.
Use some SOAP tool (Like Altove) take the data for which you are facing the problem and see if you can find something.
You can put your SOAP communication Channel in Debug mode as well.
Thanks,
Sunil Singh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Christian,
Restart your Java stack that eould fix the issue.
Thanks,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Christian,
Looks like a connectivity issue....probably a restart of java stack should solve your issue.
Regds,
Pinangshuk.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi both of you
We did that already, but have the same problem again. What makes it really strange is that the problem occurs with one out of 100 messages (round about). And it seems to have sth. to do with the data, because it happens again, if I try to send the same message again.
But the data looks as good as the data in all other messages with this interface...
That is why I really like to have a look into the server logs of the WAS...
Can you give me a hint where to find?
Regards
Christian
please refer the weblink below:
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/47/fe913d2d204aa7e10000000a421937/frameset.htm
Thanks,
Hello Hareenkumar
The link you gave me was quite helpful. I found some more logs and also tried the defauls traces. But I still did not find the error. It always seem to end in a "Null pointer exception". So I guess, that the AF does not get the message properly or something like that.
We use PI 7.0 Patchlevel 16 I think. Is there anyone out there who has experienced something like that?
Regards
Christian
User | Count |
---|---|
89 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.