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.
yup, we call that the java red screen of death, sort of the updated version of the old DOS Blue Screen of Death. It means a java error. somewhere. What i do when i get them, after swearing , is edit my program and put a hard exit in after the first couple of chunks of executable code... to see if i fail...then move the -EXIT down a few paragraphs..and try again. Eventually i can narrow down where the problem is, and usually its something like a server isn't available or a mapped drive has died or a phone line to ftpsite is dead. Usually something not code-related. For me anyway. Good luck. my sympathies.
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
I found the culprit. It was a variable named IBIAPP_app. We have it in our URL in our environment running 5.2.4 but it messes up at the client who is on 5.2.3
Posts: 81 | Location: Calgary, Alberta | Registered: August 07, 2003
So what did you finally do with that variable? I am facing the same problem and I also use that variable in my URL to refer to the directory where my focexecx are kept and I am also on WF 5.2.3.
Read-Only Topic
