You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hivemind.apache.org by "Daniel Tomsu (JIRA)" <hi...@jakarta.apache.org> on 2006/08/13 15:36:14 UTC
[jira] Created: (HIVEMIND-182) undeploying of webapps in Servlet
container
undeploying of webapps in Servlet container
-------------------------------------------
Key: HIVEMIND-182
URL: http://issues.apache.org/jira/browse/HIVEMIND-182
Project: HiveMind
Issue Type: Bug
Components: framework
Affects Versions: 1.1.1, 1.1
Environment: Apache Tomcat/5.5.17 JDK 1.5.0_07-b03 Sun Microsystems Inc. Windows XP 5.1 x86
Reporter: Daniel Tomsu
The hot undeployment of war files is not working from the tomcat environment, because the hivemind is blocked by a file handle.
The necessary libraries (hivemind, tapestry) are normally bundled in the war file.
The only way around it is to either have the jar files in your common/lib folder of the tomcat or to restart the service. But this has serious drawbacks in a productive environment, because the service might be used in different projects, too.
The message in the Tomcat Manager is: OK - Undeployed application at context path <application_name>
There is no error message in the log files. Process Explorer shows that there is one handle on the file.
Anyone has information about this bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HIVEMIND-182) undeploying of webapps in Servlet
container
Posted by "Michael Gloegl (JIRA)" <hi...@jakarta.apache.org>.
[ https://issues.apache.org/jira/browse/HIVEMIND-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463549 ]
Michael Gloegl commented on HIVEMIND-182:
-----------------------------------------
The deployment issue can be fixed by adding antiJARLocking="true" to your web application context. Still, this seems to be a bug.
> undeploying of webapps in Servlet container
> -------------------------------------------
>
> Key: HIVEMIND-182
> URL: https://issues.apache.org/jira/browse/HIVEMIND-182
> Project: HiveMind
> Issue Type: Bug
> Components: framework
> Affects Versions: 1.1, 1.1.1
> Environment: Apache Tomcat/5.5.17 JDK 1.5.0_07-b03 Sun Microsystems Inc. Windows XP 5.1 x86
> Reporter: Daniel Tomsu
>
> The hot undeployment of war files is not working from the tomcat environment, because the hivemind is blocked by a file handle.
> The necessary libraries (hivemind, tapestry) are normally bundled in the war file.
> The only way around it is to either have the jar files in your common/lib folder of the tomcat or to restart the service. But this has serious drawbacks in a productive environment, because the service might be used in different projects, too.
> The message in the Tomcat Manager is: OK - Undeployed application at context path <application_name>
> There is no error message in the log files. Process Explorer shows that there is one handle on the file.
> Anyone has information about this bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira