*** ERROR => BAD REQUEST - Reason: DpRqCheck failed (line 5195): [dpxxdisp.

[Former Member]

Hello All,

In our development system, we are able to perform all the transactions normally(SAP level) and there is no performance issues..

We have checked from OS level in work directory file dev_disp..

We are getting below error.

Can you please suggest us on this..............

=========================================================

• ERROR => DpRqCheck: T72 in stat TM_SLOT_FREE [dpxxdisp.c 5805]

***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c 4621]

• ERROR => BAD REQUEST - Reason: DpRqCheck failed (line 5195): [dpxxdisp.c 4623]

-IN-- sender_id DISPATCHER tid 72 wp_ca_blk -1 wp_id -1

-IN-- action SEND_TO_WP uid 8012 appc_ca_blk -1 type DIA

-IN-- new_stat NO_CHANGE mode 0 len -1 rq_id 53650

-IN-- req_info MS_ERROR

• ERROR => DpRqCheck: T73 in stat TM_SLOT_FREE [dpxxdisp.c 5805]

***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c 4621]

• ERROR => BAD REQUEST - Reason: DpRqCheck failed (line 5195): [dpxxdisp.c 4623]

-IN-- sender_id DISPATCHER tid 73 wp_ca_blk -1 wp_id -1

-IN-- action SEND_TO_WP uid 8013 appc_ca_blk -1 type DIA

-IN-- new_stat NO_CHANGE mode 0 len -1 rq_id 53651

-IN-- req_info MS_ERROR

• ERROR => DpRqCheck: T74 in stat TM_SLOT_FREE [dpxxdisp.c 5805]

***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c 4621]

• ERROR => BAD REQUEST - Reason: DpRqCheck failed (line 5195): [dpxxdisp.c 4623]

-IN-- sender_id DISPATCHER tid 74 wp_ca_blk -1 wp_id -1

-IN-- action SEND_TO_WP uid 8014 appc_ca_blk -1 type DIA

-IN-- new_stat NO_CHANGE mode 0 len -1 rq_id 53652

-IN-- req_info MS_ERROR

• ERROR => DpRqCheck: T77 in stat TM_SLOT_FREE [dpxxdisp.c 5805]

***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c 4621]

• ERROR => BAD REQUEST - Reason: DpRqCheck failed (line 5195): [dpxxdisp.c 4623]

-IN-- sender_id DISPATCHER tid 77 wp_ca_blk -1 wp_id -1

-IN-- action SEND_TO_WP uid 8019 appc_ca_blk -1 type DIA

-IN-- new_stat NO_CHANGE mode 0 len -1 rq_id 53653

-IN-- req_info MS_ERROR

Wed Apr 7 08:55:32 2010

***LOG Q0K=> DpMsAttach, mscon ( ussapdir00) [dpxxdisp.c 10127]

Wed Apr 7 08:55:33 2010

use SAPLOCALHOST=<ussapdir00> as internal hostname

NiPAccept: accept failed (socket=7;errno=72)

***LOG Q0I=> NiPRead: recv (73: Connection reset by peer) [niuxi.c 928]

SoftCancel request for T45 U8133 M0 received from REMOTE_TERMINAL

Network error of client T46, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3

Client address of T46 is 10.228.250.65(10.228.250.65)

***LOG Q04=> DpRTmPrep, NiBufReceive (8135 MKK27890 46 BREWL07D4359) [dpxxdisp.c 9830]

RM-T46, U8135, 620 MKK27890, BREWL07D43598, 08:43:19, M0, W4, , 2/0

Network error of client T45, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3

Client address of T45 is 10.228.250.65(10.228.250.65)

***LOG Q04=> DpRTmPrep, NiBufReceive (8133 RR606033 45 BREWL07D4359) [dpxxdisp.c 9830]

RM-T45, U8133, 600 RR606033, BREWL07D43598, 08:38:22, M0, W0, SPRO, 2/3

Release check o.K.

MBUF state PREPARED

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1025]

MBUF state ACTIVE

Wed Apr 7 08:55:39 2010

• ERROR => DpRqCheck: T45 in stat TM_SLOT_FREE [dpxxdisp.c 5805]

***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c 4621]

• ERROR => BAD REQUEST - Reason: DpRqCheck failed (line 5195): [dpxxdisp.c 4623]

-IN-- sender_id DISPATCHER tid 45 wp_ca_blk -1 wp_id -1

-IN-- action SEND_TO_WP uid 8133 appc_ca_blk -1 type DIA

-IN-- new_stat NO_CHANGE mode 0 len -1 rq_id 53678

-IN-- req_info LOGOFF CANCELMODE

Wed Apr 7 08:55:44 2010

• ERROR => DpRqCheck: T46 in stat TM_SLOT_FREE [dpxxdisp.c 5805]

***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c 4621]

• ERROR => BAD REQUEST - Reason: DpRqCheck failed (line 5195): [dpxxdisp.c 4623]

-IN-- sender_id DISPATCHER tid 46 wp_ca_blk -1 wp_id -1

-IN-- action SEND_TO_WP uid 8135 appc_ca_blk -1 type DIA

-IN-- new_stat NO_CHANGE mode 0 len -1 rq_id 53676

-IN-- req_info LOGOFF CANCELMODE

======================================================================

Thanks in advance..

Best Regards,

Kiran

[Former Member]

Hi Kiran,

It's not a problem or error, it's just a message and hence can be ignored. However you can check out SAP note 1111154 once, it will fix the issue probably if it's happening due to HTTP problem. Else you can very well ignore it.

Regards

Sourabh Majumdar