[jira] [Updated] (TOMEE-1634) Problem wih context name not unique

["Felipe Jaekel (JIRA)" <ji...@apache.org>]

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

Felipe Jaekel updated TOMEE-1634:
---------------------------------
    Attachment: fail.log

Creating application failed: /home/ec2-user/apache-tomee-plus/webapps/colaborador##20150930-1450: addChild:  Child name '/colaborador' is not unique

> Problem wih context name not unique
> -----------------------------------
>
>                 Key: TOMEE-1634
>                 URL: https://issues.apache.org/jira/browse/TOMEE-1634
>             Project: TomEE
>          Issue Type: Bug
>          Components: TomEE Core Server
>    Affects Versions: 1.7.2
>            Reporter: Felipe Jaekel
>         Attachments: fail.log
>
>
> Hi,
> I have this config in system.properties:
> openejb.deploymentId.format = {ejbJarId}/{ejbName}
> openejb.jndiname.format = {deploymentId}{interfaceType.annotationName}
> I'm using parallel deployment with TomEE 1.7.2 for some months without problem, but since some weeks ago, sometimes I get an exception when I try to deploy a newer version, telling that the context name is not unique. But if after some minutes I try to deploy the same webapp with a different version it works.
> I also noticed that the extra unversioned context I mentioned on issue 1412 is not appearing on tomcat manager anymore. https://issues.apache.org/jira/browse/TOMEE-1412
> I'm having a hard time to figure this out. I thought it could be related to some changes I made on context.xml and pom.xml, but I reverted them and the problem still happens.
> I'll attach the server logs of a deployment that failed and one that succeeded. 
> Any help is welcome,
> Thanks



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)