Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Satya Kesani (Satya Kesani)
The Toronto-Dominion Bank

The Toronto-Dominion Bank
CA
Satya Kesani Member since 2022 4 posts
The Toronto-Dominion Bank
Posted: Jan 15, 2018
Last activity: Dec 11, 2018
Posted: 15 Jan 2018 12:06 EST
Last activity: 11 Dec 2018 21:29 EST
Closed
Solved

While trying to invoke Connect SOAP, getting error " com.pega.apache.axis2.AxisFault: The input stream for an incoming message is null."

Hello,

While trying to invoke Connect SOAP, getting error " com.pega.apache.axis2.AxisFault: The input stream for an incoming message is null."

I am using PEGA 7.1.9

The InvokeAxis2 activity step 15 is failing and causing this error.Can any one tell me what might be the error and how to rectify it?

To see attachments, please log in.
Data Integration

Accepted Solution

Posted: 7 years ago
Posted: 16 Jan 2018 11:22 EST
Satya Kesani (Satya Kesani)
The Toronto-Dominion Bank

The Toronto-Dominion Bank
CA

Thanks Sudhakar and Asif for your replies.

Acutally, I customized 'invokeAxis2' for passing HTTP header in the request.

There was an issue with customized java code, which has been resolved now. I am able to successfully pass the custom HTTP header via Connect SOAP.

Thanks.
 

To see attachments, please log in.
Posted: 7 years ago
Posted: 16 Jan 2018 4:25 EST
Mohammad Asif Hasan (Mohammad_Asif_Hasan)
EPAM Systems, Inc.
Mohammad Asif Hasan
EPAM Systems, Inc.
ES

This exception is occurring due to failure in the invocation of svcUtils. Could you share the logs as well tracer capturing events? Though, as suggested by my colleague Sudhakar try verifying special character from SOAP UI Tool.

To see attachments, please log in.

Accepted Solution

Posted: 7 years ago
Posted: 16 Jan 2018 11:22 EST
Satya Kesani (Satya Kesani)
The Toronto-Dominion Bank

The Toronto-Dominion Bank
CA

Thanks Sudhakar and Asif for your replies.

Acutally, I customized 'invokeAxis2' for passing HTTP header in the request.

There was an issue with customized java code, which has been resolved now. I am able to successfully pass the custom HTTP header via Connect SOAP.

Thanks.
 

To see attachments, please log in.

Related content:

Related content has not currently been identified for this post.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice