Cannot complete connection to R/3 System & Cannot get Dynpro information

[Former Member]

Hi,

We are currently testing the performance of our ITS 6.2 with just 450 concurrent users with the think time of 30sec using Borland software. However, errors will appear after about 5 min of run and when I try to launch webgui, the screen prompted an error saying "Cannot complete connection to R/3 System. The internet Transaction Server was able to establish a connection to the R/3 System, but the connection could not be completed because of the following error Cannot get Dynpro information"

We have 3x Agate and 3x Wgate with load balanced.

The agate0.trc trace file will show

2008-05-22T00:34:46.830 p003292 t12308 s000000000DE43AF0 [w3xxwork.c, 1375]: E WorkDoWork: WorkDoEstablishSession() failed, WebASConnectFailed : rc=0xfffffffe

2008-05-22T00:34:46.830 p003292 t12308 s000000000DE43AF0 [w3xxwork.c, 1642]: WorkDoWork: catch ...

2008-05-22T00:34:46.830 p003292 t12308 s000000000DE43AF0 [w3xxsess.c, 1106]: SessCloseSession: close session 000000000E030A20(000000000DE43AF0)

2008-05-22T00:34:46.846 p003292 t12308 s000000000DE43AF0 [w3xxxgat.c, 863]: Calling gateway: sapdiag function XGatEventCloseSession(session 000000000DE43AF0)

2008-05-22T00:34:46.846 p003292 t12308 s000000000DE43AF0 [w3xxsess.c, 1106]: SessCloseSession: close session 000000000E030A20(000000000DE43AF0)

2008-05-22T00:34:46.846 p003292 t12308 s000000000DE43AF0 [w3xxxgat.c, 743]: Calling gateway: sapdiag function XGatEventDestroySession(session 000000000DE43AF0)

2008-05-22T00:34:46.846 p003292 t12308 s000000000DE43AF0 [w3xxsess.c, 336]: SessFreeSessionSlot: freeing 000000000E030A20

2008-05-22T00:34:46.846 p003292 t12308 s000000000DE43AF0 [w3xxwork.c, 1733]: WorkDoWork: ... catch done

2008-05-22T00:34:46.846 p003292 t12308 s000000000DE43AF0 [w3xxwork.c, 1190]: WorkDoWork: WorkDoGetRequest() ...

2008-05-22T00:34:46.861 p003292 t12308 s0000000000000000 [w3xxphtt.c, 328]: INCOMING HTTP HEADER: >GET /scripts/wgate//webgui/!?_{transaction=ZGENDTC002&}cli

Anyone has such experience before and would appreciate if anyone can help.

Thanks in advance

Jack

[Former Member]

Hi,

This generally happens if the Backend R3 does not have enough Dialog work process available during high load situations.

Thank You,

Salman Qayyum

[Former Member]

I have increased the R3 Dialog work process to 150+ but I still encounter the error.

dev_disp trace in my R3 system show the below error and we are not able to logon to the R3 system when it happen and the performance test would fail.

Wed May 14 20:45:25 2008

• ERROR => AdExecBlk: scratch area too small (30924), opcode 6 [adxx.c 639]

• ERROR => DpAdmHandle: AdExecBlk [dpxxdisp.c 9054]

• ERROR => DpRqNoWpHandle: DpAdmHandle [dpxxdisp.c 2622]

***LOG Q0G=> DpRqBadHandle, bad_req (NOWP) [dpxxdisp.c 3695]

• ERROR => BAD REQUEST - Reason: DpAdmHandle failed (line 2623):

[dpxxdisp.c 3697]

-IN-- sender_id DISPATCHER tid -1 wp_ca_blk 54 wp_id 0-IN-- action SEND_TO_WP uid -1 appc_ca_blk -1 type NOWP

-IN-- new_stat WP_HOLD mode 255 len 148 rq_id 9169

-IN-- req_info MSG_WITH_REQ_BUF MSG_WITH_OH SET_SYSTEM_USER

DP_APPL_SERV_INFO

I was wondering whether it has any connection to my ITS error?

Any can help?

Rg

Jack

[Former Member]

check note 681085

[Former Member]

This happens due to the threads that hangs. have a look at note 433399

thank you

[Former Member]

Hi, thanks for the reply.

The note say that this is due to an unreleased lock on a critical section when accessing the service file. This happens when the performance monitoring is turned on.

However, our system performance monitoring is turned off. Anyone can help?