This is something I have seen in the past. The error is misleading. The
problem is not that it can't find jikesw, the issue is most likely that JNI
cannot allocate enough memory to make the external call to jikesw.
You might have some newly introduced code or driver etc that is consuming
all the JVM's memory which then results in this error.
I would monitor your JVM memory and check your Event log you probably have
some Out of Memory errors.
It might be as simple as increasing your JVM heap as well.
I entered an enhancement for this to change the error message.
Hope this helps,
Mike
-----Original Message-----
From: Aslam Karachiwala [mailto:[EMAIL PROTECTED]
Sent: Monday, October 11, 2004 2:27 PM
To: JRun-Talk
Subject: NoCompilerFoundException when compiling JSPs
Folks,
My setup:
Solaris 8
JRun 4, Update 4 (was 2)
Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)
We were on JRun 4, Update 2 and had been pre-compilng JSPs using JSPC for
many months. All of a sudden, this stopped working because...
"Could not invoke Java compiler, please make sure jikesw is in
/ora2/JRun4/bin or put a JDK bin directory in your path."
There was a jikesw in /ora2/JRun4/bin and the JDK bin was/is the first
location in the environment var PATH.
I then installed Updater 4 to see if this would fix it but the problem
persists. Incidentally, the update made /ora2/JRun4/bin/jikesw a symbolic
link to /ora2/JRun4/bin/jrun - not sure if that's relevant.
The exception:
jrunx.compiler.JavaCompiler$NoCompilerFoundException: Could not invoke Java
compiler, please make sure jikesw is in /ora2/JRun4/bin or put a JDK bin
directory in your path.
at jrunx.compiler.JavaCompiler.outProcessCompile(JavaCompiler.java:434)
at jrunx.compiler.JavaCompiler.compile(JavaCompiler.java:126)
at jrunx.compiler.JavaCompiler.compile(JavaCompiler.java:94)
at jrun.jsp.Translator.compilePage(Translator.java:176)
at jrun.jsp.Translator.translate(Translator.java:254)
at jrun.jsp.Translator.translate(Translator.java:101)
at jrun.jsp.JSPEngine.translateJSP(JSPEngine.java:693)
at jrun.jsp.JSPC.compile(JSPC.java:85)
at jrun.jsp.JSPC.main(JSPC.java:223)
I also found the following thread about this on Java Technology Forums:
http://forum.java.sun.com/thread.jsp?thread=421512&forum=45&message=1870732
We're now also seeing this exception if we don't precompile the JSPs.
Any ideas/info?
--aslam
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
