cancel
Showing results for 
Search instead for 
Did you mean: 

JDBC Channel ERROR

Former Member
0 Kudos

Hi,

We sended data from DB using PI JDBC Sender Adapter. Some times we

found error ocuured in RWB when the data rows is large.

Here is the Audit log for the error message. It tell me

that "java.io.IOException: Error writing to server".

The data about 15461 row(s) and each row has about 200 colums, the

query result size is about 12M.

Can someone get me some help? Some parameters should be changed ?

Best Regards,

Terry

Audit Log for Message: 59e0f073-6206-48b2-109a-922e33b71e36

Time Stamp Type Description

2012-01-10 09:34:31 Information Channel JDBC_SEND_EB_CO_PA: Executed

Query successfully, start executing update.

2012-01-10 09:34:32 Information Channel JDBC_SEND_EB_CO_PA: Updated

15461 row(s) successfully.

2012-01-10 09:34:32 Information Send query result, size 108737266

characters.

2012-01-10 09:34:44 Information MP: entering1

2012-01-10 09:34:44 Information MP: processing local module

localejbs/CallSapAdapter

2012-01-10 09:34:44 Information The application tries to send an XI

message asynchronously using connection

JDBC_http://sap.com/xi/XI/System.

2012-01-10 09:34:44 Information Trying to put the message into the send

queue.

2012-01-10 09:35:29 Information Message successfully put into the

queue.

2012-01-10 09:35:29 Information The application sent the message

asynchronously using connection JDBC_http://sap.com/xi/XI/System.

Returning to application.

2012-01-10 09:35:29 Information MP: leaving

2012-01-10 09:35:29 Information The message was successfully retrieved

from the send queue.

2012-01-10 09:35:44 Information The message status was set to DLNG.

2012-01-10 09:35:44 Error Transmitting the message to endpoint

http://sapxiprd:9000/sap/xi/engine?type=entry using connection

JDBC_http://sap.com/xi/XI/System failed, due to:

com.sap.engine.interfaces.messaging.api.exception.MessagingException:

Error transmitting the message over HTTP. Reason: java.io.IOException:

Error writing to server.

2012-01-10 09:35:44 Information The message status was set to WAIT.

2012-01-10 09:35:44 Information The asynchronous message was

successfully scheduled to be delivered at Tue Jan 10 09:40:44 CST 2012.

2012-01-10 09:40:44 Information The message status was set to TBDL.

2012-01-10 09:40:46 Information Retrying to send message. Retry: 1

2012-01-10 09:40:46 Information The message was successfully retrieved

from the send queue.

2012-01-10 09:40:46 Information The message status was set to DLNG.

2012-01-10 09:40:47 Error Transmitting the message to endpoint

http://sapxiprd:9000/sap/xi/engine?type=entry using connection

JDBC_http://sap.com/xi/XI/System failed, due to:

com.sap.engine.interfaces.messaging.api.exception.MessagingException:

Error transmitting the message over HTTP. Reason: java.io.IOException:

Error writing to server.

2012-01-10 09:40:47 Information The message status was set to WAIT.

2012-01-10 09:40:47 Information The asynchronous message was

successfully scheduled to be delivered at Tue Jan 10 09:45:47 CST 2012.

2012-01-10 09:45:47 Information The message status was set to TBDL.

2012-01-10 09:45:48 Information Retrying to send message. Retry: 2

2012-01-10 09:45:48 Information The message was successfully retrieved

from the send queue.

2012-01-10 09:45:48 Information The message status was set to DLNG.

2012-01-10 09:45:49 Error Transmitting the message to endpoint

http://sapxiprd:9000/sap/xi/engine?type=entry using connection

JDBC_http://sap.com/xi/XI/System failed, due to:

com.sap.engine.interfaces.messaging.api.exception.MessagingException:

Error transmitting the message over HTTP. Reason: java.io.IOException:

Error writing to server.

2012-01-10 09:45:49 Information The message status was set to WAIT.

2012-01-10 09:45:49 Information The asynchronous message was

successfully scheduled to be delivered at Tue Jan 10 09:50:49 CST 2012.

2012-01-10 09:50:49 Information The message status was set to TBDL.

2012-01-10 09:50:50 Information Retrying to send message. Retry: 3

2012-01-10 09:50:50 Information The message was successfully retrieved

from the send queue.

2012-01-10 09:50:50 Information The message status was set to DLNG.

2012-01-10 09:50:51 Error Transmitting the message to endpoint

http://sapxiprd:9000/sap/xi/engine?type=entry using connection

JDBC_http://sap.com/xi/XI/System failed, due to:

com.sap.engine.interfaces.messaging.api.exception.MessagingException:

Error transmitting the message over HTTP. Reason: java.io.IOException:

Error writing to server.

2012-01-10 09:50:51 Error The message status was set to NDLV.

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member184681
Active Contributor
0 Kudos

Hi,

Have a look at a similar thread . It says about a file adapter error, but the reason seems similar - exceeding the maximum size of a HTTP request allowed in PI configuration. Try checking the value of parameter icm/HTTP/max_request_size_KB and make sure it is greater then the size of your message (in XML size).

Hope this helps,

Grzegorz

rajasekhar_reddy14
Active Contributor
0 Kudos

its looks adapter unable to process bulk records at a time.this could be the reason.