on 11-13-2013 4:57 AM
Hi All,
Today our PI system crashed due to OutOfMemory error. The response we received from the Basis team was that most likely this was caused by PI team clicking on messages in error status link (RWB->Adapter Monitoring). System didn't come back automatically as file system was at 100%, 4gb heap dump file and also large core file created at crash time. The system was completely re-started to bring back to life.
There was a huge load that was sent from ECC to PI, but opening the failed message only has created the system outage. Is there any note or solution for this issue. Any help on this would be much appreciated.
Thanks,
Sherin Jose P
HI,
We have the same issue & our PI server crashed on stopping/starting the adapter. We have huge volume coming in PI from third party and while looking into the message log ( from RWB-selecting the CC) The system crashed & never came back, unless BASIS restarted it and added some memory.
Although Admin said that memory is not full, i believer this object which select the message crashed & hanged on. My question is how do we handle this. If we need to turn on/off the channel or look message log how should we go from there..!!
Please advice.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sherin,
PI Sys will not crash just because of clicking the messgaes (RWB->Adapter Monitoring).
This might have happen becuase the Archive directory in the PI Server might have filled up , please check with your basis team and ask them to increase disc space of archive directory.
Regards,
Sai
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sherin,
Seems like the volume of the message processed is high.
becuase of this PI server disc space might have filled up and when you click on the messages you are not able to open and sys gets hanged up.
Ask basis team to check on the disk space of PI server and increase the space.
Regards,
Sai
OOM error is thrown when there is insufficient space to allocate an object in the Java heap.
May be the messages are very large in size and when you are trying to open the failed messages the GC cannot make any further space available as the heap cannot be expanded further.
do you know the size of the failed messages?
http://help.sap.com/saphelp_nwesrce/helpdata/en/97/d0de42c02c420da92a7cec346f9168/content.htm
Instead of opening from the group try opening one of the failed messages i.e. go to
RWB->Msg Monitoring-> AE(Database) -> give the filters and select one of the failed message to see what the error is
Hi Sherin,
Doing operations like display/restart/cancel on huge number of messages causes memory issues, which can cause slow message processing/server hanging.
As Hareesh suggested restrict the messages using filter, give interface details and time of error. All the messages might be in error due to a common issue, seeing one of message error details would be good.
Your basis team might be right on system outage, the above will be work around for your case to view message error details.
Regards,
Pranav
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
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.