[JBoss JIRA] Created: (JBAS-7781) Update ClusteredDeploymentRepository to deal with VFS3
by Brian Stansberry (JIRA)
Update ClusteredDeploymentRepository to deal with VFS3
------------------------------------------------------
Key: JBAS-7781
URL: https://jira.jboss.org/jira/browse/JBAS-7781
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Clustering, ProfileService
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: JBossAS-6.0.0.M3
There's really two aspects to this:
1) ClusteredDeploymemtRepository.removeDeployment can't use the VirtualFile from ProfileDeployment.getRoot() as an input the the RepositoryClusteringHandler, because that VF is now a special "backup" copy that the handler can't understand. This is the cause of a testsuite failure.
2) AbstractLocalContentManager should mount each of the URIs it monitors in a separate location, so it can scan the original contents even if some children of those URIs are actually copies created by deployers.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 4 months
[JBoss JIRA] Updated: (JBAS-7205) Redeployment of session doesn't acquire session state
by Brian Stansberry (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-7205?page=com.atlassian.jira.plug... ]
Brian Stansberry updated JBAS-7205:
-----------------------------------
Fix Version/s: JBossAS-6.0.0.M4
(was: JBossAS-6.0.0.M3)
> Redeployment of session doesn't acquire session state
> -----------------------------------------------------
>
> Key: JBAS-7205
> URL: https://jira.jboss.org/jira/browse/JBAS-7205
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering, Web (Tomcat) service
> Affects Versions: JBossAS-5.1.0.GA
> Reporter: Bela Ban
> Assignee: Brian Stansberry
> Fix For: JBossAS-6.0.0.M4
>
> Attachments: web.war
>
>
> Here's the scenario:
> - Start instances A and B in a cluster, the webapp is session.war (*exploded* WAR)
> - Create a session, say its session-id is sessionId.A
> - Go to A and remove the WAR, e.g. cd ./deploy ; mv session.war session.war.bak
> - Refresh the session. It fails over to B: sessionId.B
> - Go back to A (/deploy dir) and mv session.war.bak session.war
> - Go to B and remove the session
> ==> The session will fail back to A, but the session's data is gone !
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 4 months