Hi,
I'm facing this error sometimes:

: ERROR: ncjInit failed. failed to connect to java server: JSS
: . JSCOM3 listener may be down - see edaprint.log for details.

Analysing the edparint.log I have several java OutOfMemory Exceptions.

My issue is what could cause this and what could I do to overcome this problem, since this leads to the application being unavailable.

I have one Agent in the Java services with Maximun heap size set to 512 MB, one thing I found strange is the low amount of memory free of this agent: is about 15-30 MB. If I create more agents all the request are treated by the first.

Has anyone faced this problem, what have you done to aliviate this?

Regards.
A.S.

This message has been edited. Last edited by: <Kathryn Henning>,

Hi as2010,

I am following up with you regarding this issue. If you have not already can you open a case at IBI Techsupport and upload the log files to review with the TSR?

There might be a bit more to review then what we can handle in this forum.

If you have opened a case please let us know and provide the resolution.

Thank you for participating in the Focal Point Forum.

Kindest regards,
Tamra Colangelo
Focal Point Moderator
Information Builders Inc.

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

Did this ever get resolved? I know it's an old post, but we're getting this error now too. Did a full restart, and then it came back shortly after.

J Hines

Look in the edaprint.log. If you are using the reporting server on you local machine App Studio is looking for a 32 bit version of Java on your machine. If this it the reporting server on your server machine it is looking for the 64 bit version of java. See if there is a environment variable JDK_HOME or JAVA_HOME pointing to a valid directory where the jvm.dll exists.