Apache Tomcat/4.1.30-LE-jdk14 error in version 5.5

Question

I have been using FuegoBPM Studio 5.5 for the past 18 months. All my projects have worked as expected until now. For whatever reason, I can no longer launch the Work Portal from Studio. I have been getting the error:
"HTTP Status 404 - /testProcess
type Status report
message /testProcess
description The requested resource (/testProcess) is not available.
Apache Tomcat/4.1.30-LE-jdk14"
"Tomcat error: 'ContextConfig[CustomerSetup] Exception processing JAR at resource path /WEB-INF/lib/fuegoblock-web-net.jar
javax.servlet.ServletException: Exception processing JAR at resource path /WEB-INF/lib/fuegoblock-web-net.jar at org.apache.catalina.startup.ContextConfig.tldScanJar(ContextConfig.java:930)     at org.apache.catalina.startup.ContextConfig.tldScan(ContextConfig.java:868"
"----- Root Cause -----
java.util.zip.ZipException: The process cannot access the file because it is being used by another process
     at java.util.zip.ZipFile.open(Native Method)
     at java.util.zip.ZipFile.<init>(ZipFile.java:111)
     at java.util.jar.JarFile.<init>(JarFile.java:127)"
I am not sure what's causing the problem.
Please help!
Thanks,
Edited by gman at 07/01/2008 1:45 PM

Answer 1

I am providing the info below..just to add to your knowledge.
You can also administer your Tomcat using the URL
http://localhost:8080/admin
Here you will be prompted for a username and password.
To have the right to administer cd to %CATALINA_HOME%\conf
Look for tomcat-user.xml file.
Modify it as below:
<?xml version='1.0' encoding='utf-8'?>
<tomcat-users>
<role rolename="admin"/>
<role rolename="user"/>
<role rolename="tomcat"/>
<role rolename="role1"/>
<user username="tomcat" password="tomcat" roles="tomcat,admin"/>
<user username="role1" password="tomcat" roles="role1"/>
<user username="both" password="tomcat" roles="tomcat,role1"/>
</tomcat-users>
After doing that. Restart tomcat.
Your user name is :tomcat
password :tomcat (from line 7 in the file above)
Now u can administer your server without having to worry about tweaking your server.xml file.
The interface allows an easy to use mechanism for you to administer your server and it is more enjoyable than digging the server.xml file.
And ..any luck so far with the soution to your problem?