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 have a report that occasionally receives the following error:
An error has been detected during server to client data transfer. ERROR: -12: Pcb2.: java.io.EOFException
It will work fine with the same input ten or twenty times and then I get the error. There is no difference in the data or the input when it happens. It crashes the agent when it gets this error.
We sometimes get a java socket exception in report caster. Recently a job that had run daily for at least two years with no issues failed. I put a space after a parm that was printed in the heading and it went away. Seems once you get the error it stays for us. May be a java issue. I had one one time when a specific date was printed in the header and it wouldn't work any other date and it did. Even had a case open but no resolutions. Oh and it occurred in 4.3.6 and 5.3.2.
You might see if your headings do have an amper variable printed at the end just before a double quote mark.
Posts: 1317 | Location: Council Bluffs, IA | Registered: May 24, 2004
Yep. It actually happens on more than one report. This report is the most used report we have so it show up more often. We have about 10 - 12 crashed agents a day. This never happened when we were running CGI.
Anyone seen this one? I have researched it on the IBI site...and only found reference to too many defines. I have one. I have been getting this error for about a week. Doesn't seem to have any pattern...just whenever it wants to just show up.
Read-Only Topic