Greg Baynham [EMAIL PROTECTED] wrote:
I'm getting tripped up trying to get tomcat to run JSP code when it's
installed as a service. when I access a JSP page I get this error:
root cause
Unable to find a javac compiler;
com.sun.tools.javac.Main is not on the classpath.
Perhaps JAVA_HOME
Perhaps the Tomcat5.exe process manager is trying to send sun jvm
specific parameters to the jrockit jvm?
Indeed, it does. Tomcat5w.exe passes -Xrs to the jvm and you can do
nothing about it as it is hardcoded.
See Bugzilla Bug 33777:
http://issues.apache.org/bugzilla/show_bug.cgi?id=33777
Dan Washusen [EMAIL PROTECTED] wrote:
Hi Sven,
I can access the data source from within my code using the name
java:/comp/env/jdbc/MindDB and everything works great. It's just
that the Realm can't... I have found a few other posts to this list
with the same problem and one of the email
TomK [EMAIL PROTECTED] wrote:
Dominik -- Regarding your statement that the latest CVS version does
not suffer from the nasty jar locking. I'll try it out later, but are
you suggesting 5.5.7 will not have JAR locking issues at all, and thus
the antiResourceLocking and antiJARLocking
Siarhei Dudzin [EMAIL PROTECTED] wrote:
Did you find a solution?
FYI it has been fixed on 17/12/2004 and the latest CVS version does not
suffer from the nasty jar locking.
The root of the problem was the JasperLoader locking (using cached
getResourceAsStream()) the jars containing jsp tag
Slobodan Vujasinovic [EMAIL PROTECTED] napisa(a):
Hi,
Has anyone succeeded to expose Tomcat 5.5.x server for remote JMX
management
with j2se 1.4?
Tomcat 5.5.x is intended to be run on JRE 5.0, but its *is* compatible with
JRE 1.4.
Several libraries became core ones for JRE 5.0, therefore,
Slobodan Vujasinovic [EMAIL PROTECTED] wrote:
That is the way to start and run tomcat under j2sdk 1.4.x!
But, my question was regarding server exposure for remote jmx management
(for example, to enable MC4J connection to installed tomcat 5.5).
I must have misread your question, sorry :/
/dd
