Hi All,

I am using Report Caster for generating reports based on schedule jobs.

There are few intermittent errors because of which the reports are failing continuously.

I tried generating the reports from report caster individually. Individually, all the reports generated are successful and no errors are shown in the report caster logs. However, when same reports are generated in jobs (7 reports per min) following errors come up in report caster.

1. Task error: incoming signal AB spooled by FTM code 2 event 4 not allowed in state 0.
2. Error connecting to the WebFOCUS Reporting Server EDASERVE: EDA SQL STATUS (-11).
3. Task error: EdaPro00.rcv in err state
4. Task error: incomplete mas file.
5. Task error: java.net.SocketException: Socket closed

I have checked the Java code which schedules the reports, ran the report individually through report caster, checked all the configurations of Webfocus but I am still able to get these errors when the reports are triggered through java code.

As these errors are repetitive but every time for different reports, I am not able to find out the root cause for it. The maximum connection pool is set to 30
Is there any configuration change that needs to be done in webfocus side?

Any kind of help is much appreciated.

This message has been edited. Last edited by: Kerry,

Swap,

Have you considered opening a case with IB tech support?
This seems to be something that is not really a topic that belongs in this forum but rather in IB's problem queue.

I thought I should try in Forums first in case I am lucky, I'll be able to get the answers.

Anyways I have opened a case with IBI and waiting for their response.

In the meantime suggestions are welcome

Gamp is correct something like this really needs to go to IBI who will almost certainly want servlet traces.

However possible causes are
lack of resources,
connection timeout limits being hit,
to many concurrent processes.

Also look at increasing the java heap size