cancel
Showing results for 
Search instead for 
Did you mean: 

JDBC initialize failed due to long idling time

Former Member
0 Kudos

Hi gurus

Anyone having similar problem and would like to share their solution for the problem stated below.

Normally the integration for IDOC-XI-JDBC scenarios is working fine, but when the R3 halt sending IDOC to XI, the JDBC connection to MS SQL 2000 server failed to process and initialise due to long idling time. Currently the temporary solution is to go to XI change the Integration Directory : Communication Channel for the JDBC - Activate - Clear Cache. Then go to R3, retrigger the IDOC again. And the above problem will be resolved. But after a while (long idling time again), this problem arise once again.

2008-10-21 15:18:45 Success Message successfully received by messaging system. Profile: XI URL: http://locahost:50600/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER

2008-10-21 15:18:45 Success Using connection JDBC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.

2008-10-21 15:18:45 Success Message successfully put into the queue.

2008-10-21 15:18:45 Success The message was successfully retrieved from the receive queue.

2008-10-21 15:18:45 Success The message status set to DLNG.

2008-10-21 15:18:45 Success Delivering to channel: CC_IDOC_TO_DBMS_ESMS_588

2008-10-21 15:18:45 Success MP: Entering module processor

2008-10-21 15:18:45 Success MP: Processing local module localejbs/CallSapAdapter

2008-10-21 15:18:45 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce

2008-10-21 15:18:45 Error JDBC adapter receiver channel CC_IDOC_TO_DBMS_ESMS_588 not initialized. Unable to proceed due to null

2008-10-21 15:18:46 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: JDBC Adapter configuration not initialized: null

2008-10-21 15:18:46 Error Exception caught by adapter framework: JDBC Adapter configuration not initialized: null

2008-10-21 15:18:46 Error Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: JDBC Adapter configuration not initialized: null.

2008-10-21 15:18:46 Success The message status set to WAIT.

2008-10-21 15:18:46 Success The asynchronous message was successfully scheduled to be delivered at Tue Oct 21 15:23:46 GMT+08:00 2008.

2008-10-21 15:23:46 Success The message status set to TBDL.

2008-10-21 15:23:46 Success Retrying to deliver message to the application. Retry: 1

2008-10-21 15:23:46 Success The message was successfully retrieved from the receive queue.

2008-10-21 15:23:46 Success The message status set to DLNG.

2008-10-21 15:23:46 Success Delivering to channel: CC_IDOC_TO_DBMS_ESMS_588

2008-10-21 15:23:46 Success MP: Entering module processor

2008-10-21 15:23:46 Success MP: Processing local module localejbs/CallSapAdapter

2008-10-21 15:23:46 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce

2008-10-21 15:23:46 Error JDBC adapter receiver channel CC_IDOC_TO_DBMS_ESMS_588 not initialized. Unable to proceed due to null

2008-10-21 15:23:46 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: JDBC Adapter configuration not initialized: null

2008-10-21 15:23:46 Error Exception caught by adapter framework: JDBC Adapter configuration not initialized: null

2008-10-21 15:23:46 Error Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: JDBC Adapter configuration not initialized: null.

2008-10-21 15:23:46 Success The message status set to WAIT.

2008-10-21 15:23:46 Success The asynchronous message was successfully scheduled to be delivered at Tue Oct 21 15:28:46 GMT+08:00 2008.

2008-10-21 15:28:46 Success The message status set to TBDL.

Edited by: Malcolm Pang on Oct 23, 2008 11:08 AM

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi

I agree with Bhavesh. Try disconnecting after every message process. This would ensure that connection is not broken in idle times.

Regards

bhavesh_kantilal
Active Contributor
0 Kudos

In the JDBC adapter , select option Disconnect From Database after Each message processing.

This will solve the process as your JDBC Database seems to be closing the connection after a particular idle time.

Regards

Bhavesh