Re: configuring tomcat on XP as a service
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 does not point to the JDK However, I have set the environment variables JAVA_HOME and PATH to both reference my installation of the JSDK. I have rebooted, but still get the error. specifics: tomcat 5.0.28 windows XP home JAVA_HOME=C:\j2sdk1.4.2_06\bin PATH=%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Pro gram Files\Common Files\Adaptec Shared\System;%JAVA_HOME% JAVA_HOME should point to the very directory the jdk is installed into. Set the JAVA_HOME=C:\j2sdk1.4.2_06 You might also want to update your PATH so that it contains %JAVA_HOME%\bin Your env variables should look like that then: JAVA_HOME=C:\j2sdk1.4.2_06 PATH=%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Progr am Files\Common Files\Adaptec Shared\System;%JAVA_HOME%\bin This should make it work. cheers, /dd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 5.5.7+JRockit = windows service won't start
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 regz /dd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DataSourceRealm says Name jdbc is not bound in this Context
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 suggested that the Realm is configured before the DataSource causing an error to be thrown during realm initialisation (as the DataSource is missing). It looks like the solution is to move the DataSource configuration to the Global configuration area or to use the JBDCRealm. It is not necessary to make the datasource global. Try adding localDataSource=true to your context Realm definition. Having consulted the docs for 4.1.x, 5.0.x and 5.5.x, t seems that this flag is only allowed in the latest version of tomcat. There's a chance though that it has been backported without having the docs updated. HTH, /dd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAR locking / Tomcat 5.5.4 / Windows
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 attributes will be unnecessary?? Well, in my particular case (I have a test app using jstl fmt taglib) I no longer needed antiJARLocking. I have even explicitely set it to false in context.xml. It undeploys now whereas before having the fix applied undeploy failed. cheers /dd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAR locking / Tomcat 5.5.4 / Windows
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 libraries. It works for me. Please do give it a spin and test for yourselves. BTW, there seems to be 5.5.7 distro coming soon. cheers, /dd On Tue, 4 Jan 2005 15:27:56 -0800 (PST), TomK [EMAIL PROTECTED] wrote: I've been following the recent threads regarding JAR locking with Tomcat 5.x on Windows platforms. A few people mentioned they had been able to get either the antiJARLocking or antiResourceLocking attributes to work, so I've spent quite a bit of time trying out different scenarios and configurations, under the impression that I must be missing something simple.however, I've not yet found a situation where either attribute has any effect on deploy/undeploy. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 5.5 - JMX
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, these are not distibuted with tomcat 5.5.x anymore. All you have to do is to download compatibility package (jakarta-tomcat-5.5.x-compat.zip) and extract it to your tomcat directory. /dd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 5.5 - JMX
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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
