As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
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>,
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 ModeratorThis message has been edited. Last edited by: Tamra,
WebFOCUS 8x - BI Portal, Developer Studio, App Studio, Excel, PDF, Active Formats and HTML5
Posts: 487 | Location: Toronto | Registered: June 23, 2009