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 have a strange problem with caster. About once per week the following happens: Scheduled reports do not distribute. No log files are created and no trace files are created. But the job seems to have run. So a job that is supposed to run everyday has tomorrow as the nextruntime. But it never ran and there is no log or trace related to it. Once this problem is seen, it persists for all scheduled reports until we restart report caster.
We are opening a case with IBI about this, but I was wondering whether anyone else has ever seen this?
We think our problem is related to too many reports running at the same time as well. For example the last times this happened was when there were 35 reports scheduled for the same time. None of them were very large but still... we have increased the number of permitted agents in the distribution server (was at 25) to see if that will help.
What is the maximum number of job that you are allowing caster to run at one time. The default is like 3. This means that caster will only allow 3 jobs to run at a given time.
When you say you restart reportcaster is that because it is has stopped running?
We had a problem where it looked like everything stopped running. What it tuurned out to be was that the servers were schedule to reboot on a set basis. When they came back the services would start automatically. What we found was that the service for reportcaster was trying to start prior to the webfocus service. There is a dependency between the two in that reportcaster won't start unless the webfocus service is already running. We fixed it by setting properties for reportcaster service to retry after a few minutes if it doesn't start correctly.
TexasStingray: I am not sure what the current setting is for the maximum number of jobs permitted. I will check this. Are you saying that Caster will crash if this is exceeded? Obviously it should not work like that.
MTracker: No Caster was still running. At least it appeared to be. A scheduled job at 2PM would run and then have tomorrow at 2PM as the nextruntime. But the job never actually ran. Nothing happened. Like I said, no trace no log, nothing. But the nextruntime changes like normal. Nothing was rebooted or anything like that. The problem was fixed by restarting reportcaster.
What versions are you running? I believe in older versions (<5.2) sometimes the SYNC machine would stop. I believe that reportcaster needs that to work correctly otherwise you might run into problems trying to update the repository when you have multiple updates trying to occur at once. If that happened it could explain why you don't see anything in the log or error file.
Did you look at contents of scheduler.log file to be sure reportcaster started correctly?
No I am not saying that caster will crash. It will que them. and wait for one of the 3 to finish if they never do you can see what will happen. everything will just be getting qued.
Read-Only Topic