[ 
https://issues.apache.org/jira/browse/TOMEE-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Zowalla resolved TOMEE-1412.
------------------------------------
    Resolution: Auto Closed

Hi there!

We wanted to reach out and let you know that we're currently working on 
cleaning up open issues in Jira that specifically impact unsupported versions, 
including 1.7.x, 7.0.x, and 7.1.x.

If you had previously reported this issue on one of these unsupported versions, 
we kindly ask you to check if the problem still persists and can be reproduced 
on a supported version such as 8.0.x or 9.0.x. If you find that it is indeed 
reproducible on a supported version, you're more than welcome to re-open this 
issue.

Thanks!


> Extra unversioned context displayed when using parallel deployment
> ------------------------------------------------------------------
>
>                 Key: TOMEE-1412
>                 URL: https://issues.apache.org/jira/browse/TOMEE-1412
>             Project: TomEE
>          Issue Type: Test
>    Affects Versions: 1.7.1
>         Environment: Amazon Linux, latest version
> LMDE, latest version
> Java 7 update 67
>            Reporter: Felipe Jaekel
>            Priority: Minor
>              Labels: test
>
> When using parallel deployment, TomEE 1.7.1 displays an additional 
> unversioned context in manager and webaccess applications. Another detail is 
> that on manager the undeploy option is disabled for this unversioned context. 
> This doesn't happen on a regular Tomcat 7.0.55.
> I haven't found any actual problems, but as i'm not using TomEE in production 
> yet, my tests were limited, so I would appreciate some investigation if this 
> can impact on session routing somehow.
> Sample:
> https://dl.dropboxusercontent.com/u/66737052/mavenproject%23%2320140924-1600.war
> https://dl.dropboxusercontent.com/u/66737052/mavenproject%23%2320140924-1615.war
> Thanks



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to