Skip to Content
0

JDBC Error in IDOC to JDBC Scenario

Jul 13, 2017 at 11:40 AM

114

avatar image
Former Member

Hi Experts,

For the use case IDOC to JDBC in SAP PI dual stack the messages are failing with Mapping:General Error as " Configuration error: Channel "6ad3ef7be245398d8b66ecc814cc8bc3" is not a receiver type" . The details log as below.

InformationUsing connection JDBC_http:// sap.com/xi/XI/System. Trying to put the message into the receive queue13.07.2017 13:06:43.935InformationMessage successfully put into the queue13.07.2017 13:06:43.988InformationThe message was successfully retrieved from the receive queue13.07.2017 13:06:44.079InformationMessage status set to DLNG13.07.2017 13:06:44.095InformationDelivering to channel: CC_JDBC_RCV_Invoice13.07.2017 13:06:44.101InformationMP: processing local module localejbs/CallSapAdapter13.07.2017 13:06:44.103InformationReceiver JDBC adapter: processing started; QoS required: ExactlyOnce13.07.2017 13:06:44.414ErrorConfiguration error: Channel "6ad3ef7be245398d8b66ecc814cc8bc3" is not a receiver type13.07.2017 13:06:44.417ErrorMP: exception caught with message {0}13.07.2017 13:06:44.440ErrorException caught by adapter framework: {0}13.07.2017 13:06:44.446ErrorDelivery of the message to the application using connection JDBC_http:// sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception13.07.2017 13:06:44.511ErrorMessage status set to NDLV

Thanks in Advance,

Farooq

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

4 Answers

gurudatta d Jul 13, 2017 at 12:16 PM
0

Hi Farooq,

1)Please check in Message mapping -IDOC-JDBC structure mapping..Whether it is sucessfull/All fields are mapped correctly.

JDBC expects a standard structure statement,action,table,access

2)Please check JDBC receiver channel Configuration for Jdbc Driver ,Connection string,User name,Password

3)Try to stop and start the channel again

3)If possible please share the screenshots

Thanks,

Guru

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Jul 13, 2017 at 01:51 PM
0

Farooq,

please upload a screenshot of the receiver channel configuration.

Regards

Share
10 |10000 characters needed characters left characters exceeded
Manoj K Jul 13, 2017 at 12:32 PM
0

Farooq,

Check if your reciever JDBC channel has deafult module : CallSapAdapter and check the cache too.

if the above dosen't work try restarting JBDC channels in RWB or in NWA.

Br,

Manoj

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Jul 26, 2017 at 08:46 AM
0

The same issue also arised for IDOC to File scenario where File receiver channel is showing the same error " Configuration error: Channel "6ad3ef7be245398d8b66ecc814cc8bc3" is not a receiver type"

Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hello Farooq,
The "invalid receiver channel" error is most likely related to the cluster communication problem.

The cause of the problem, which surfaces as inconsistent channel state in the cluster, is the processing time for the channel startup on each cluster node. As the cluster communication is synchronous, the node which triggered the channel activation waits for a certain time (which is the addressed cluster communication time out value) for answers and fails, if this time out expires without having received answers from all other nodes.

To avoid this problem, I would suggest to set the time out value to 180000 (it is configured in milliseconds, so this would be 3 minutes).

Check the following two parameters and increase their value:

(1) clusterCommunicationTimeoutMsec

The timeout is 15000 [ms] * default and is defined in the Property 'clusterCommunicationTimeoutMsec' of the J2EE Service "com.sap.aii.af.svc". Increase the value to 180000 [ms] * higher in all nodes.

(2) messaging.cluster.timeout

Increase the value of property 'messaging.cluster.timeout' of service "SAP XI AF Messaging" from 60000 [ms] * value) to 180000 [ms] * higher.

A server restart is required to make them take effect.

Best regards,
Vadym

0