Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

New session rejected due to memory bottleneck in testing proxy2proxy

Hi all!

i am testing abap proxy2proxy on the client 105 in help varient 5 of simple use cases docu.

even though i got sending successful from SXIPATT1 on the client 105, i got the following error.

my server has RAM 2GB and have four client(100,105,106,107), and only i use for testing, NOT another person, so i do not think memory bottleneck issue.

checked list.

1. SXMB_MONI, i could see inbound message(SENDER) <b>only.</b>

from 105 to XI, no problem I thought, but very strange there, becasue there is only inbound message(sender).

2. status flag on sxmb_moni

Message Recorded (Commit follows) (TO BE DELIVERED)

does anyone experience such issue?

do i have to up physical memory?

Error when processing your request

What has happened?

The URL http://sapxi.hh.net:8000/sap/bc/gui/sap/its/webgui/! was not called due to an error.

Note

The following error text was processed in the system XID : <b>New session rejected due to memory bottleneck</b>

The error occurred on the application server SAPXI_XID_00 and in the work process 0 .

The termination type was: ABORT_MESSAGE_STATE

The ABAP call stack was:

Function: ICF_ATTACH_ITS_PLUGIN of program SAPLHTTP_RUNTIME

Form: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP

Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME

Module: %_HTTP_START of program SAPMHTTP

What can I do?

If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system XID in transaction ST22.

If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server SAPXI_XID_00 in transaction SM21.

If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server SAPXI_XID_00 . In some situations, you may also need to analyze the trace files of other work processes.

If you do not yet have a user ID, contact your system administrator.

Error code: ICF-IE-http-c:105-u:XISUPER -l:E-s:XID-i:SAPXI_XID_00 -w:0-d:20060410-t:195211-v: ABORT_MESSAGE_STATE-e:

HTTP 500 - Internal Server Error

Your SAP Internet Communication Framework Team

Former Member
Former Member replied

did you have this entries in SXMB_ADM of XI server

catgory:RUNTIME parameter:ENGINE_TYPE value: HUB

catgory:RUNTIME parameter:IS_URL value:http://server:port/sap/xi/engine?type=entry

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question