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.
We've faced that many times in older versions. The code may run just fine everywhere but from Report Caster, which uses a different code set, I believe. I know this sounds silly, but in one instance what fixed it was putting a space between the double quote ending a heading and the character just before it. Other times just deleted and added back a row. The really bad issue for us was a job had been running forever and then boom, java socket exception. The administrator always insisted it had to be the code, which it wasn't. We've had the issue recently on a job that gets the exception, queue it in again and it runs fine. I empathise with you completely on this one.
Leah
Posts: 1317 | Location: Council Bluffs, IA | Registered: May 24, 2004
...but back on 5.2.8 we've seen this error many times when someone makes a change to a config file or adds a data connection and restarts the services or kills a job by accident.
WebFOCUS 7.6.6/TomCat/Win2k3
Posts: 428 | Location: Springfield, MA | Registered: May 07, 2003
We cannot try in Dev studio since we use standalone reports that run in browser. Is there any standard solution for this problem? We cannot queue the requests manually since that action is done independent of our control.
Then run from a browser or an adhoc window. You need to test in another environment to verify that the program does work before you blame RC for the problem.
Do you mean in the managed reporting environment? If so do you edit the code? Are you allowed to run other than with Report Caster, such as in deferred mode or 'live' mode?
Leah
Posts: 1317 | Location: Council Bluffs, IA | Registered: May 24, 2004
We currently have an open issue similar to this where we occasionally we getting these types of failures. This is on release 7.6.1.
What it came down to was having 2 ReportCaster jobs scheduled to run at the same exact time (i.e. 11:05:00). Sometimes they would both work. Other times 1 would fail. Sometimes both would fail.
We finally did get a patch to address the issue. It did work. However it has since caused us another problem that has forced us to remove the patch.
By this time we had identifed all schedules that were doubling up on the execution time. So, removing the patch is not that big a deal.
in you fex and run it in reportcaster with full notification of error to you. Sometimes this reveals what it doesn't like, otherwise, change some little thing and see what happens then.
Good Luck
Leah
Posts: 1317 | Location: Council Bluffs, IA | Registered: May 24, 2004