cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP Adapter, Communication Channel Error

Former Member
0 Kudos

Hi,

I am getting the below given error message

com.sap.engine.interfaces.messaging.api.exception.MessagingException:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException:
com.sap.aii.af.service.administration.api.cpa.CPAChannelStoppedException:
Channel stopped by administrative task.

I am using a SOAP Adapter for exposing SAP PI Synchronous interface. I am testing through SOAP UI Tool.

Please help.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

What is you receiver side configuration? which adapter you are using? check if respective channel for that is active. Do all the above checks for this also.

Former Member
0 Kudos

Hi Bharat,

Turns out that my receiver side channel was stopped. I started it, now I am getting the below given exception.

Any thoughts

com.sap.engine.interfaces.messaging.api.exception.MessagingException:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException:
java.net.ConnectException: Connection refused: connect

Regards

Former Member
0 Kudos

Which adapter you are using? Verify the connection parameters you should be able to find catch there.

Former Member
0 Kudos

Hi Upendra,

Could be multiple issues... on connection failure.

Just check if host name of webservice endpoint is updated on SAP PI machine hosts file.

--Divyesh Vasani

Former Member
0 Kudos

Hi Upendra,

Possible reasons for your exception.

1)Target system is down.

2)Configured url might be wrong.

3)Receiver channel might be stopped.

Sol:share the configured url to receiver system folks and ask them to check whether the service is down or configured url is not correct.

Regards

Venkat

Answers (4)

Answers (4)

Former Member
0 Kudos

Thanks for your answers everyone,

I was able to overcome the issue. The receiver communication channel had the URL in the format http://localhost:xxxx/xxxxx. Local host since I am using SOAP UI as the target webservice.

I changed the localhost to the to the IP Address of my machine and messages started flowing.

Regards

anand_shankar10
Active Participant
0 Kudos

Just one more check:

Since you are using SOAP UI.. try with both the option http and https and see the difference. Before that make sure to activate the channel.

The option for HTTP ad HTTPS will be available in the property when you select the service interface.

Check SOAPAction.

Thanks

Anand

Former Member
0 Kudos

Thanks Anand,

need a clarification.

The SOAP action is to be provided for "Receive Communication Channel". This one will be used by SAP PI to call external service. Please correct me if I am wrong here.

For Sender communication Channel, I am not getting an option to provide the SOAP action even though I am using the SOAP Adapter.

Regards

anand_shankar10
Active Participant
0 Kudos

Hi Upendra,

A little change., try with different endpoints (http and https) after selecting the request message under service interface.

You will get this option in SOAP UI tool.

Thanks

Anand

Former Member
0 Kudos

Generic solutions:

1. Check communication channel advanced tab in directory if it is inactive, set it to active

2. Check in RWB Communication Channel monitor

3. Try CPA Cache refresh

4. If above steps don't help, check if there is any locks in NWA

Former Member
0 Kudos

Thanks Bharat. Responses below

1. Already set to Active

2. "Process errors in last 10 mins"

3. CPA Cache updated

4. Removed locks

Tried above steps, no success.

Former Member
0 Kudos

have you seen below threads:

http://scn.sap.com/thread/2143298

http://scn.sap.com/thread/763886 (refer Vinc solution )

Former Member
0 Kudos

Hi Sankar S,

Thanks for the answer.

I have tried the below steps but no success

1. Stopping and starting the communication channel.

2. Cleared the SLD Data Cache

Anything else that I should do.