on 04-02-2008 6:32 AM
Is it a natural behavior to have qRFC errors? There are some occurences (not all the time) on the XML message processing that messages in the inbound queue are stuck (meaning not processed).
I've read several blogs suggesting reseting queues' status and trigerring (restarting) the messages. But is this the most recommended way to do it? And is it a natural behavior that some messages are just scheduled and stuck up in the queue?
Here are qRFC errors Im encountering:
SYSFAIL: 'Screen output without connection to user.'
CPICERR: 'connection closed (no data)'
Hi,
The error may be because of -Resource Utilization, Memory Space, unavailability of the receiver at that point of time, message volume etc
Possible solutions include, sizing of the server as per the recommendation[Quick Sizer Tool from SAP], Checking the message volume and frequency
There is one SAP note talks about Restart of Messages: 833171
Rgds, Moorthy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
10 | |
10 | |
9 | |
9 | |
7 | |
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.