You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Oleg Lyashko (JIRA)" <ji...@apache.org> on 2008/02/09 12:22:07 UTC
[jira] Commented: (AXIS2-3052) Undeploy fails to persist sessions
on Tomcat 5.5 and 6
[ https://issues.apache.org/jira/browse/AXIS2-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567296#action_12567296 ]
Oleg Lyashko commented on AXIS2-3052:
-------------------------------------
workaround to this problem (on Linux)
1 Create axis2 context file ${catalina.home}/conf/Catalina/localhost/axis2.xml as follows
<?xml version="1.0" encoding="UTF-8"?>
<Context workDir="${catalina.home}/work/Catalina/localhost/axis2/fooapp"/>
2. Create subdirecroties axis2 and axis2/fooapp in the ${catalina.home}/work/Catalina/localhost
3. Set permissions for user account running Tomcat so, that tomcat (and axis2) have read/write access to fooapp directory but read-only access to axis2 directory. As result tomcat and axis2 will be able to create files and write in the axis2/fooapp and in the same time bad code in axis1.3 will not be able to delete fooapp directory.
P.S. Actually I had hope that bad code, not been able to delete fooapp directory, will "reveal" itself and throw exception, but undeployment end quietly :(
> Undeploy fails to persist sessions on Tomcat 5.5 and 6
> ------------------------------------------------------
>
> Key: AXIS2-3052
> URL: https://issues.apache.org/jira/browse/AXIS2-3052
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: Tomcat 5.5.20
> Axis 1.3
> Reporter: simishag
> Assignee: Deepal Jayasinghe
> Attachments: tomcat552.JPG
>
>
> Reloading the webapp from the Tomcat Manager causes the following exception:
> org.apache.catalina.session.ManagerBase - IOException while saving persisted sessions:
> java.io.FileNotFoundException: /var/lib/tomcat-5.5/work/Catalina/localhost/axis2/SESSIONS.ser (No such file or directory)
> I verified that the directory exists and is writable by the Tomcat user. I tried creating the SESSIONS.ser file in advance, setting permissions then reloading. Same exception happens, and the file actually gets removed.
> I have only seen this problem since I started using 1.3-RC2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org