Hi Friends,

I am getting the Server Failed to Respond Error When I am running a PFLOW. This error is only for this flow. All other Flows are working Fine. Even the Sub flow is working if I run it separately.

If you have any ideas to fix this issue, Please share it with me.

Here is the complete error message:

[INFO]14:48:25 I/O exception (org.apache.commons.httpclient.NoHttpResponseException) caught when processing request: The server gd-iway01-p failed to respond
[INFO]14:48:25 Retrying request


Thanks,
Mary....

This message has been edited. Last edited by: <Kathryn Henning>,

quote:

I/O exception (org.apache.commons.httpclient.NoHttpResponseException) caught when processing request:

Hi Mary,

This is a friendly follow-up for your question regarding - Server Failed to Respond Error.

While we wait to see if anyone provides some assistance I have searched the IBI knowledgebase and found a few similar cases.
If the following suggestions do not help, I would suggest opening a case with TechSupport InfoResponse. and upload any trace files as well.

It could be something to do with memory.

May I suggest the following: bring down the configuration that has the
deployed channel with the pflow in question. Delete all the log files, bring
the configuration back up and run the channel again. Please upload the log
if it contains the error.

Otherwise, if it is an issue restricted to iIT, then collect the traces there
and upload them to the case.

Another resolution might be if it is a PFLOW running standalone in iIT.
Re-created the PFLOW from scratch, by copying the objects from the PFLOW
that failed.

Let us know if the above helps or as mentioned this might be better off opening a case for resolution since trace files will be required to better determine the cause.


Kindest regards,
Tamra Colangelo
Focal Point Moderator

This message has been edited. Last edited by: Tamra,

Hi Tamra,

Thanks for the reply. The issue is resolved by itself. I don't know how and why I got that error message and why it is not there now.

Thanks,
Mary....