cancel
Showing results for 
Search instead for 
Did you mean: 

WPs are dying and can not be restarted with EyeDestroyed error in trace

Former Member
0 Kudos

Hi,

since few days WPs started dying and we can not restart them on central instance (on dialog instance running on different server, everything looks ok). IN the trace file of wps, we find following error message:

M rdisp/wp_abap_restart = 0

M ThSetThToolParam : restartable_wp[0] = FALSE

M ThSetThToolParam : restartable_wp[1] = TRUE

M ThSetThToolParam : restartable_wp[2] = TRUE

M ThSetThToolParam : restartable_wp[3] = FALSE

M ThSetThToolParam : restartable_wp[4] = TRUE

M ThSetThToolParam : restartable_wp[5] = TRUE

M ThSetThToolParam : restartable_wp[6] = TRUE

M ThDtWpBlk: detach WP ca_blk 127

M ThISend: clear stat record

M PfClearAllRec: clear statistic area

M ThISend: stat_state = TH_STAT_CLEAR

M ThISend: th_wp_waits_for_rq = TH_WP_WAITS_FOR_RQ

M make DISP owner of wp_ca_blk 127

M DpRqPutIntoQueue: put request into queue (reqtype 0, prio LOW, rq_id 56996)

M -OUT- sender_id WORK_PROCESS tid -1 wp_ca_blk 127 wp_id 6

M -OUT- action SEND_TO_DP uid -1 appc_ca_blk -1 type NOWP

M -OUT- new_stat WP_WAIT mode 0 len 8 rq_id 56996

M REL APPC ca_blk 120

M ThDtAppcBlk: detach APPC ca_blk 120

I *** ERROR => Shared Pool=10 Key=13 EyeBefore Violation [shmux.c 3422]

M ***LOG R1D=> TH_PRIV_OUT_CHECK, Eye destroyed () [thxxhead.c 9818]

M in_ThErrHandle: 1

M *** ERROR => TH_PRIV_OUT_CHECK: EyeDestroyed (step 5, th_errno 5, action 3, level 1) [thxxhead.c 10237]

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

hi Andrija Jevtic,

It seems the problem is caused by kernel.

please upgrade your kernel to the latest version.

Don't forget to backup your old kernel before do the upgrade.

Let me know if still problem.

Regards

Ariyanto

Answers (3)

Answers (3)

Former Member
0 Kudos

Did you ever find a resolution to the EyeDestroyed error in the trace files. We are having the same issue and the only solution is to restart the instance.

Former Member
0 Kudos

This is a kernel issue.

Please check SAP Note 1416430 - Incorrect synchronization during server startup.

Former Member
0 Kudos

Hi Andrija

Check, SAP Note 6512 - Problems when poolsize is set to 0

Hope that useful

Cheers

Shaji

Former Member
0 Kudos

Hi,

It's not clear from this log, pl. try to paste all the log of dev_w0. Did you make any changes in memory related parameters? or did u applied any patch?

Reagrds,

Hari.