RE: War files don't work

Tang, Thanks for the reply. Unfortunantly, that isn't the behavior I am seeing, and I think the other poster had the same issue. If I don't have a context for my war file in the server.xml, then it unpacks fine. But, if I do have a context, then it won't unpack, and I have to do it manually.

RE: how-to specify Java runtime options -Xmx128m, w/ Tomcat 4 as Win2k service

Would this tool help? I also saw a wiki page for tomcat on setting memory in the registry.. http://web.bvu.edu/staff/david/tcservcfg/ I guess my question is what it sthe right way to set options like this when running as an Win2k service? Eric Pugh -Original Message- From: Simon

RE: War files don't work

What the Automatic Applcation Deployment doc says is that if you have a WAR file, it won't be expanded if you have a context element in the server.xml document. It will only be run from that war file in an unexpanded format. correct? Eric -Original Message- From: John Turner To: Tomcat

RE: War files don't work

I'm joining this thread late, but I posted a couple weeks ago the same problem.. I am running JDK1.4.2 and Tomcat 4.1.24. If I have a context specified in server.xml, then the war file DOESN'T unpack. If I don't have a context specified, then it DOES unpack. Setting the docBase to fortius.war

War file with server.xml context won't unpack, without server.xml context will

Hi all, My question is basically the subject. I have a war file called fortius.war. If I drop it in my webapp/ directory it will not unpack using tomcat 4.1.24. However, if I rename it to anything else, like fortius-new.war, it will! I attribute this to having a context in the server.xml file:

Mime Type Header errors!

Hi, I just moved my Turbine application from one server to another. The new one has jdk1.4.1 and tomcat 4.1.24. My users are complaining of clicking links, and getting back a page not found error. If they refresh, then it does hit the page. I looked into the logs, and found these errors:

Upgraded to Tomcat 4.1.24 and J2SE1.4_02, JSP's failing

Hi All, I just upgraded my production box to Tomcat 4.1.24 and j2SE1.4_02 from TC4.1.18 and J2SE1.3_x, and now my JSP's are failing: org.apache.jasper.JasperException: Unable to compile class for JSP An error occurred at line: -1 in the jsp file: null Generated servlet error: [javac] Since

RE: Upgraded to Tomcat 4.1.24 and J2SE1.4_02, JSP's failing

I tracked down the error message, attached it below.. It seems to be failing due to not being able to create a temp file in my c:\java\system32\ directory: snip Caused by: java.io.FileNotFoundException: C:\WINNT\system32\files1850283357 (The system cannot find the file specified) at

RE: Upgraded to Tomcat 4.1.24 and J2SE1.4_02, JSP's failing

I guess I should have held off longer before looking for help.. The problem was an NT permissions issue, although it seems like a bug to me in the JSP compiler. The account tomcat was using was changed when I did the upgrade (I should have remembered that). The account did not have write

RE: win2000 issue with tomcat4.1.24

I am wrestling with the same issue... I think it is caused by the javac program not being in your path... But I am not 100% percent sure.. Also, the nt service logon user needs write permssions to c:\winnt\system32... look at your logs.. If you make progress, please let me know..