Help for "ICM max connection" problem !

[Former Member]

Hi there,

we're running EP 7.0 (abap+java dual stack ) on HP-UX 11.31 for about 5000~6000 users.

-one db+ci server and three ap servers

Smetimes I'm getting message in 'dev_icm'

[Thr 67] *** ERROR => IcmConnPoolNewEntry: upper limit of desc in pool reached (used=500/max=500) [icxxpool_mt. 1664]

I wonder why this messages are showing

one of AP server's instance parameters are ...

icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=5$$00

icm/server_port_0 = PROT=HTTP,PORT=80,TIMEOUT=30,PROCTIMEOUT=600,EXTBIND=1

icm/max_conn = 16384

icm/max_sockets = 16384

rdisp/max_wprun_time = 600

icm/req_queue_len = 6000

icm/min_threads = 100

icm/max_threads = 250

mpi/total_size_MB = 500

mpi/max_pipes = 20500

rdisp/tm_max_no = 3000

rdisp/max_arq = 3000

gw/max_conn = 3000

rdisp/max_comm_entries = 3000

gw/max_sys = 3000

gw/max_overflow_size = 50000000

gw/max_shm_req = 500

-> I found although I set 'icm/max_conn' parameter to 16384 ( above 500 ),

the system did not establish more than '500' connections.

I guess 'icm/HTTP/j2ee_0... 'CONN=0-500' parameter value might force the connection go below '500'.

-> If so,

- what should I do to keep free ICM connection as many as possible?

regularly restart j2ee instance?

regularly restart abap process with rdisp/wp_auto_restart?

...

- what should I do to make the ICM establish more connections over 500

increase 'CONN=0-500' to 'CONN=0-1000' ?

...

Thanks in advance~

Edited by: Nam-Moo BC on Jul 6, 2009 9:59 AM

[JPReyes · Accepted solution]

Have you looked into icm/keep_alive_timeout ? that might help you to keep the more icm connection available.

http://help.sap.com/saphelp_nw04s/helpdata/EN/0b/1c7e7abbc311d5993a00508b6b8b11/content.htm

Regards

Juan

[Former Member · Accepted solution]

Thanks Juan,

as per your advice I have checked currnent profile valus. here are some of them.

- icm/keep_alive_timeout = 60

- icm/server_port_0 = PROT=HTTP,PORT=80,TIMEOUT=30,PROCTIMEOUT=600,EXTBIND=1

- rdisp/max_wprun_time = 600

from those values, my guess are

for IDEL TIMEOUT

-1. HTTP service(ICM) keeps idle connection state for 30 seconds

after that the connection is freed.

-2. After 1800 seconds of idel state, the user context expires and is removed

for PROCESSING TIMEOUT

- ICM waits for 600 seconds for an output form the WEB AS server.

But, If on a heavy load situation for example between 9 to 10 am, concurrent 2000 users...

maximum connections are reaching up to 400...498,499,500 max !

Can it be solved by enlarging

icm/max_conn = 16384

icm/max_sockets = 32768

icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=5$$00

or should it be enlarged altogather

icm/max_sockets

icm/max_sockets

icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-2000,PORT=5$$00

[Former Member]

icm/max_conn = 16384
icm/max_sockets = 16384

You may want increase icm/max_conn further as it allows upto 32000. I believe you need to have icm/max_sockets double the number of max_conn parameter as it opens one or two sockets for each connection. Check your OS limits too.

[Former Member]

thanks Manoj

I'm running the EP 7.0 on a HP-UX 11.31 IA64 machine

current os parameter shows maximum sokects are 4088 < 32768.