The request data is invalid. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff, detail = gg....gg)

aa....aa: Resource adapter display name
bb....bb: Service group name (if the service group name cannot be determined, a single-byte hyphen (-) is displayed)
cc....cc: Service name (if the service name cannot be determined, a single-byte hyphen (-) is displayed)
dd....dd: IP address of OpenTP1
ee....ee: Listen port number of OpenTP1 (if the listen port number cannot be determined, a single-byte hyphen (-) is displayed)
ff....ff: CommNo of root AP information
gg....gg: Details

Description

While receiving the RPC request using the TP1 inbound integrated functionality, an invalid data is received. An error has occurred in the settings of OpenTP1, or a client other than OpenTP1 client is connected.

The received data will be cancelled, and then the connection will be disconnected.

Action

Take the following action based on the details:

header: Received header contents (hexadecimal 12 digits)

Check whether an invalid client is connected. If an invalid client is connected, modify the settings in such a way so that the invalid client is disconnected.

Scheduler direct function is not used.

Check that the user service network definition uses the scheduler direct function.

dc_rpc_call function is not used.

Check that the dc_rpc_call function is used, and the service is invoked.

It is not the first request data.

The RPC request message received by the TP1 inbound adapter might not be the first message, and might be a later message. Re-execute the RPC request.

An illegal client is connected. (Maintenance information)

Check whether an invalid client is connected. If an invalid client is not connected, collect the maintenance information, and then contact maintenance personnel.