on 08-17-2011 7:24 PM
Hi All,
We are seeing following error in SXMB_MONI when huge volume of messages hitting PI system. The interface is SOAP-RFC Synchronous.
Error: /MessagingSystem/receive/AFW/XI is temporary unavailable.
Please find below trace log from SXMB_MONI
<Trace level="1" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET):</Trace>
<Trace level="1" type="T">URL = http://xxx.com:nnnnn/MessagingSystem/receive/AFW/XI</Trace>;
<Trace level="1" type="T">User = XXXXX</Trace>
<Trace level="1" type="T">Cached = X</Trace>
<Trace level="1" type="T">Security: Basic authentication</Trace>
<Trace level="1" type="T">Serializing message object...</Trace>
<Trace level="1" type="T">HTTP-client: status code = 503</Trace>
<Trace level="1" type="System_Error">Error while sending by HTTP (error code: 503 , error text: Service Unavailable)</Trace>
I have checked previous SDN blogs, SAP NOTE 803145 and everything matches in our landscape
Appreciate any thoughts on this.
Thanks
Vijay
Good afternoon - We are experiencing this exact same issue. We get the same error message when we try to push a large volume of messages through the SOAP adapter. Can you please let us know how many ICM threads SAP recommended? We have already increased them substantially, so I am curious about how high they had you set yours to.
Thanks for your assistance!
Regards,
Blair Towe
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI,
We are having the same issue where the messages are failing in random out of huge volume ( 1000+)
The error messages are different & includes
Error while sending by HTTP (error code: 503 , error text: Service Unavailable) (See attachment HTMLError for details)
While looking at HTML it is showing Error: /MessagingSystem/receive/AFW/XI is temporary unavailable
Also we are seeing 401 unauthorized messages.
As per SAP we have applied the following notes 821026, 8 91877, 937159 but with not much success.
Please advice if anyone has encountered this issue & solution.
Regards
The server is running in Normal mode all the times. We never give system access to users when it is in Safe mode.
thanks
Vj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello
This situation can also occur if the j2ee engine is started in SAFE mode. It can lead to an issue where not all applications are started. You can check this as described below.
Setting the j2ee engine to normal mode and restarting the j2ee engine should resolve the issue if the engine is in safe mode.
Using the configtool to switch the system to NORMAL mode:
1. Start the configtool script file from the /usr/sap/<SID>/<instance name>/j2ee/configtool/ directory.
2. From the menu choose "File" > "Safe Mode". A dialog box appears.
3. Choose "No" from the "Safe Mode Enabled" drop-down list.
4. Choose "OK".
5. Save the settings and confirm all the messages that are displayed.
You could also check the following:
Ensure that all xi and aii applications are started.
To do this, go to the NWA:
-> Operation Management -> Systems -> Start & Stop -> Java EE Applications -> (use the filter to search for both) xi and aii
Regards,
Sarah
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
All,
Its not Timeout error i assume....
The issue occuring when Integration Engine trying to hand shake the message to Adapter Engine over integration server. It is not related to Timeout issue. The Adapter Frame Work service giving an error Temporary unavialble when there is a huge message volume.
Sender Aggreement --> passed
Interface Mapping --> passed
Receiver Agrement --> when trying to get Adapter information through the URL http://xxxxx.nnnnnn/MessagingSystem/receive/AFW/XI, we are getting the Error: /MessagingSystem/receive/AFW/XI is temporary unavailable for some of the messages.
Let us say if PI recieves 1000 messages, 800 messages getting success and 200 getting failed with above error.
Thanks
Vijay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vijay,
Check below parameters:
u2022 UME Parameters : May be we need to look into the pool size and poolmax wait parameters - UME recommended parameters (like: poolmaxsize=50, poolmaxwait=60000)
u2022 Tuning Parameters: May be we need to look/define the Message Size Limit u201Clike: EO_MSG_SIZE_LIMIT = 0000100u201D under tuning category
u2022 ICM Parameters: May be we need to consider ICM parameters (ex: icm/conn_timeout = 900000. icm/HTTP/max_request_size_KB = 2097152)
Also increase value for icm/server_port_0 parameter.
Thanks and Regards,
Naveen
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 |
---|---|
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.