dialog work process in stop gui status

[Former Member]

Hi,

there are lots of dialog work process are stuck status due to stop gui error.

stop gui work process are not getting released automatic from the system due to this many users are facing problem and they are getting sap slow problem.

to resolve the issue we have to kill the work process manually from the system by using tcode sm66.

kindly help to resolve the issue.

Regards,

Koushal Solanki

[Former Member]

problem solved

[Former Member]

Dear Solanki,

Please give the solution how you resolved the issue

Regards

Mohammed

[former_member221621]

Could you possibly let us know how the problem got resolved?

[Former Member]

Hi Koushal,

Did you perhaps upgrade your kernel recently? I have simmilar problems and I suspect it is the kernel.

Regards,

CJ

[Former Member]

Could you go through the following note, incase of the same release

-

---

Note 51373 - Problems with progress indicator at WAN connection

-

---

Pls let us know your SAP version details.

cheers !

PRADi

[Former Member]

Hi,

Please check your rdisp/max_hold_time parameter default is 60 seconds to connect GUI as a WP.

Regards

Shailendra

[Former Member]

What do you see in de dev_* trace of the work process and the dispatcher?

Kind regards,

Mark

[Former Member]

Hi,

kindly find the log below

M *** WARNING => ThAdXDelUser: delete T149

M *** ERROR => ThCheckEmState: no em context for T2/M0 [thxxmem.c 381]

M *** ERROR => ThCheckEmState: no em context for T2/M0 [thxxmem.c 381]

C

C Wed May 19 09:01:40 2010

C build_stmt: reallocating stmt buffer: 2304 -> 3312 characters

C build_stmt: reallocating stmt buffer: 3312 -> 4328 characters

C build_stmt: reallocating stmt buffer: 256 -> 2000 characters

C build_stmt: reallocating stmt buffer: 2816 -> 3822 characters

C build_stmt: reallocating stmt buffer: 3822 -> 4823 characters

C build_stmt: reallocating stmt buffer: 512 -> 2000 characters

C build_stmt: reallocating stmt buffer: 2048 -> 3050 characters

C build_stmt: reallocating stmt buffer: 3050 -> 4052 characters

M

M Wed May 19 09:01:42 2010

M *** ERROR => ThCheckEmState: no em context for T2/M0 [thxxmem.c 381]

M

M Wed May 19 09:01:57 2010

M *** ERROR => ThCheckEmState: no em context for T2/M0 [thxxmem.c 381]

M

M Wed May 19 09:04:46 2010

M *** ERROR => ThCheckEmState: no em context for T2/M0 [thxxmem.c 381]

******************************

B ***LOG BY4=> sql error 60 performing SEL on table NRIV [dbtran#4 @ 7588] [dbtran 7588 ]

B ***LOG BY0=> ORA-00060: deadlock detected while waiting for resource [dbtran#4 @ 7588] [dbtran 7588 ]

B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'SEL'

B RSLT: {dbsl=99, tran=1}

B FHDR: {tab='NRIV', fcode=33, mode=2, bpb=0, dbcnt=0, crsr=1,

B hold=0, keep=1, xfer=0, pkg=0, upto=0, init:b=0,

B init:p=(nil), init:#=172, wa:p=0xc0000004440b6120, wa:#=172}

B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'SEL'

*********************************************

M Wed May 19 08:57:25 2010

M *** ERROR => ThCheckEmState: no em context for T2/M0 [thxxmem.c 381]

C

C Wed May 19 08:58:57 2010

C OCIStmtExecute() failed with -1=OCI_ERROR

C SQL error 60:

C *** ERROR => Error 60 in stmt_fetch() from oci_execute_stmt(), orpc=0

[dbsloci.c 12990]

C *** ERROR => ORA-60 occurred when executing SQL stmt (parse error offset=0)

[dbsloci.c 13011]

*********************************************

dispatcher log

Wed May 19 15:13:43 2010

• ERROR => DpWPCheck: max_hold_time W2 exceeded (T140=msb85 ) [dpxxdisp.c 15928]

• ERROR => DpTmRetErr: DpTmSend [dpxxdisp.c 13138]

[Former Member]

Hi,

i am also getting following error for some of the users.

Thu May 6 11:08:15 2010

• ERROR => DpCheckTerminals: NiCheck2(rc=-23) failed for tid: 189 (60secs)-> disconnecting [dpxxdisp.c 13208]

RM-T189, U30657, 500 ASTVSTOM1, aswag59, 11:05:15, M2, W1, SQ01, 5/2

Regards,

Koushal Solanki

[Former Member]

Hi, are you check the DB01 t-code ? In CHECK DB (shedule in db13) check results ?