[
https://issues.apache.org/jira/browse/GEODE-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081349#comment-16081349
]
ASF subversion and git services commented on GEODE-2901:
--------------------------------------------------------
Commit 6e86762385b14ab9a35a1f045251ea5a7411e23a in geode's branch
refs/heads/develop from [~DivineEnder]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=6e86762 ]
GEODE-2901: Resolving possible session testing concurrency issues
Updated installation and container management to allow more container
independence.
Previously, containers edited files within the installation, leading to several
containers modifying the same file. Given the concurrent nature of runs, this
could become a problem if containers ever wrote something to the same part of
each file.
Containers now create their own separate and unique files that they use to run,
hopefully removing any concurrency problems that might arise.
Also tried to optimize for long term sanity of whoever must maintain this code.
This closes #619
> Add more tests of http session replication module
> -------------------------------------------------
>
> Key: GEODE-2901
> URL: https://issues.apache.org/jira/browse/GEODE-2901
> Project: Geode
> Issue Type: Improvement
> Components: http session
> Reporter: Dan Smith
> Assignee: David Anuta
>
> We should add more integration tests of http session replication with
> failover, expiration, and multiple containers.
> We currently have some junit tests of the generic session replication module
> in geode-modules-session and a couple of dunit tests of the tomcat session
> module in geode-modules-tomcat8.
> However, we really want a comprehensive set of tests that run against both
> session modules and multiple containers.
> I think we can get to that point if we use something like
> [cargo|https://codehaus-cargo.github.io/cargo/Home.html]. We could do
> something like the dunit tests we have where we use httpunit from the client,
> but use cargo to actually launch the containers.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
