cancel
Showing results for 
Search instead for 
Did you mean: 

Timeout Condition of pipeline reached

Former Member
0 Kudos

Hi,

I have the following scenacrio

PC Client sends SOAP sync message into PI
Receive SOAP Message into ccBPM

Map SOAP Message and pass to ECC via sync proxy

      Data is mapped to staging tables in ECC

Sync proxy is sent back to ccBPM

Save SOAP Payload onto NFS

Return response back to PC Client

I am running tests on this using SOAPUI. Depending on how I invoke the SOAPUI test depends on what PI is doing.

If I pass is 100 threads in a "Burst", then what I am noticing is that the first 10 or so message in PI are failing with the error "Timeout Condition of pipeline reached".

The messages that are processed successfully take approx 10 seconds.

After a small amount of time PI appears to catch up with itself and start to process the messages. There then may be the odd one that fails with the same error.

I have two questions to ask.

1. What is causing this Timeout to occur. We have adjusted various timeout settings and we are still getting the error.

The timeout settings we have adjusted is:

SMICM for HTTP keep alive timeout set to 300.

RZ11 for parameter icm/keep_alive_timeout now set to 300.

2. Could I be running SOAPUI in an incorrect way which is causing PI to behave like this.

Any help is much appreciated.

Thanks

Martin

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member190624
Active Contributor
0 Kudos

Hello Martin,

Did you restarted PI system after increasing HTTP time out parameter ?

Regards

Hari.