[jira] [Commented] (TOMEE-2183) org.apache.commons.codec filtered by the classloader but not provided by TomEE WebProfile
[
https://issues.apache.org/jira/browse/TOMEE-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538090#comment-16538090
]
Violeta Georgieva commented on TOMEE-2183:
--
I confirm that using the system property above the app is working.
Thanks,
Violeta
> org.apache.commons.codec filtered by the classloader but not provided by
> TomEE WebProfile
> -
>
> Key: TOMEE-2183
> URL: https://issues.apache.org/jira/browse/TOMEE-2183
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 7.0.4
>Reporter: Violeta Georgieva
>Assignee: Jonathan Gallimore
>Priority: Major
>
> Hi,
>
> I have an EAR file with "lib" folder that contains "commons-codec" and a WAR
> file that uses the libraries located in the "lib" folder. I do not have
> issues with the other libraries in that folder but with "commons-codec" I
> receive the exception below.
>
> I'm using TomEE 7.0.4 WebProfile and in that distribution there is no
> "commons-codec" provided by TomEE itself because of this I'm providing it
> with the EAR file.
>
> While debugging I saw that "org.apache.commons.codec" is intentionally
> filtered by the classloader
>
> [https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/util/classloader/URLClassLoaderFirst.java#L305]
>
> How it is supposed to provide this library so that my application can use it?
>
> Thanks,
> Violeta
>
> {code}
> java.lang.ClassNotFoundException: org.apache.commons.codec.binary.Base64
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1285)
>
> org.apache.tomee.catalina.TomEEWebappClassLoader.loadClass(TomEEWebappClassLoader.java:208)
>
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1119)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (TOMEE-2183) org.apache.commons.codec filtered by the classloader but not provided by TomEE WebProfile
[
https://issues.apache.org/jira/browse/TOMEE-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16537311#comment-16537311
]
Violeta Georgieva edited comment on TOMEE-2183 at 7/9/18 5:37 PM:
--
Hmmm
It is strange.
Use this app
[https://github.com/cloudfoundry-community/tomee-buildpack/issues/23#issuecomment-369632408]
(use the provided ear and request https:///backend-ssmm-cloud/contrato/,
ignore the rest in the comment)
When the system is slow or I enable debugging and try to follow the
[https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/util/classloader/URLClassLoaderFirst.java#L305]
I can reproduce the issue,
But if the system is fast there is no problem.
Regards,
Violeta
was (Author: violetagg):
Hmmm
It is strange.
Use this app
[https://github.com/cloudfoundry-community/tomee-buildpack/issues/23#issuecomment-369632408]
When the system is slow or I enable debugging and try to follow the
[https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/util/classloader/URLClassLoaderFirst.java#L305]
I can reproduce the issue,
But if the system is fast there is no problem.
Regards,
Violeta
> org.apache.commons.codec filtered by the classloader but not provided by
> TomEE WebProfile
> -
>
> Key: TOMEE-2183
> URL: https://issues.apache.org/jira/browse/TOMEE-2183
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 7.0.4
>Reporter: Violeta Georgieva
>Assignee: Jonathan Gallimore
>Priority: Major
>
> Hi,
>
> I have an EAR file with "lib" folder that contains "commons-codec" and a WAR
> file that uses the libraries located in the "lib" folder. I do not have
> issues with the other libraries in that folder but with "commons-codec" I
> receive the exception below.
>
> I'm using TomEE 7.0.4 WebProfile and in that distribution there is no
> "commons-codec" provided by TomEE itself because of this I'm providing it
> with the EAR file.
>
> While debugging I saw that "org.apache.commons.codec" is intentionally
> filtered by the classloader
>
> [https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/util/classloader/URLClassLoaderFirst.java#L305]
>
> How it is supposed to provide this library so that my application can use it?
>
> Thanks,
> Violeta
>
> {code}
> java.lang.ClassNotFoundException: org.apache.commons.codec.binary.Base64
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1285)
>
> org.apache.tomee.catalina.TomEEWebappClassLoader.loadClass(TomEEWebappClassLoader.java:208)
>
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1119)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TOMEE-2183) org.apache.commons.codec filtered by the classloader but not provided by TomEE WebProfile
[
https://issues.apache.org/jira/browse/TOMEE-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16537311#comment-16537311
]
Violeta Georgieva commented on TOMEE-2183:
--
Hmmm
It is strange.
Use this app
[https://github.com/cloudfoundry-community/tomee-buildpack/issues/23#issuecomment-369632408]
When the system is slow or I enable debugging and try to follow the
[https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/util/classloader/URLClassLoaderFirst.java#L305]
I can reproduce the issue,
But if the system is fast there is no problem.
Regards,
Violeta
> org.apache.commons.codec filtered by the classloader but not provided by
> TomEE WebProfile
> -
>
> Key: TOMEE-2183
> URL: https://issues.apache.org/jira/browse/TOMEE-2183
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 7.0.4
>Reporter: Violeta Georgieva
>Assignee: Jonathan Gallimore
>Priority: Major
>
> Hi,
>
> I have an EAR file with "lib" folder that contains "commons-codec" and a WAR
> file that uses the libraries located in the "lib" folder. I do not have
> issues with the other libraries in that folder but with "commons-codec" I
> receive the exception below.
>
> I'm using TomEE 7.0.4 WebProfile and in that distribution there is no
> "commons-codec" provided by TomEE itself because of this I'm providing it
> with the EAR file.
>
> While debugging I saw that "org.apache.commons.codec" is intentionally
> filtered by the classloader
>
> [https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/util/classloader/URLClassLoaderFirst.java#L305]
>
> How it is supposed to provide this library so that my application can use it?
>
> Thanks,
> Violeta
>
> {code}
> java.lang.ClassNotFoundException: org.apache.commons.codec.binary.Base64
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1285)
>
> org.apache.tomee.catalina.TomEEWebappClassLoader.loadClass(TomEEWebappClassLoader.java:208)
>
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1119)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TOMEE-2183) org.apache.commons.codec filtered by the classloader but not provided by TomEE WebProfile
[
https://issues.apache.org/jira/browse/TOMEE-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16536962#comment-16536962
]
Violeta Georgieva commented on TOMEE-2183:
--
Hi,
In which TomEE version I may expect any fix?
Thanks in advance,
Violeta
> org.apache.commons.codec filtered by the classloader but not provided by
> TomEE WebProfile
> -
>
> Key: TOMEE-2183
> URL: https://issues.apache.org/jira/browse/TOMEE-2183
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 7.0.4
>Reporter: Violeta Georgieva
>Assignee: Jonathan Gallimore
>Priority: Major
>
> Hi,
>
> I have an EAR file with "lib" folder that contains "commons-codec" and a WAR
> file that uses the libraries located in the "lib" folder. I do not have
> issues with the other libraries in that folder but with "commons-codec" I
> receive the exception below.
>
> I'm using TomEE 7.0.4 WebProfile and in that distribution there is no
> "commons-codec" provided by TomEE itself because of this I'm providing it
> with the EAR file.
>
> While debugging I saw that "org.apache.commons.codec" is intentionally
> filtered by the classloader
>
> [https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/util/classloader/URLClassLoaderFirst.java#L305]
>
> How it is supposed to provide this library so that my application can use it?
>
> Thanks,
> Violeta
>
> {code}
> java.lang.ClassNotFoundException: org.apache.commons.codec.binary.Base64
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1285)
>
> org.apache.tomee.catalina.TomEEWebappClassLoader.loadClass(TomEEWebappClassLoader.java:208)
>
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1119)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (TOMEE-2183) org.apache.commons.codec filtered by the classloader but not provided by TomEE WebProfile
[
https://issues.apache.org/jira/browse/TOMEE-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1651#comment-1651
]
Violeta Georgieva edited comment on TOMEE-2183 at 6/25/18 12:31 PM:
[~jgallimore] just create an EAR file with "lib" folder that contains
"commons-codec" and from the WAR file try to load a class from "commons-codec"
and that's only for WebProfile
was (Author: violetagg):
[~jgallimore] just create an EAR file with "lib" folder that contains
"commons-codec" and from the WAR file try to load a class from "commons-codec"
> org.apache.commons.codec filtered by the classloader but not provided by
> TomEE WebProfile
> -
>
> Key: TOMEE-2183
> URL: https://issues.apache.org/jira/browse/TOMEE-2183
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 7.0.4
>Reporter: Violeta Georgieva
>Assignee: Jonathan Gallimore
>Priority: Major
>
> Hi,
>
> I have an EAR file with "lib" folder that contains "commons-codec" and a WAR
> file that uses the libraries located in the "lib" folder. I do not have
> issues with the other libraries in that folder but with "commons-codec" I
> receive the exception below.
>
> I'm using TomEE 7.0.4 WebProfile and in that distribution there is no
> "commons-codec" provided by TomEE itself because of this I'm providing it
> with the EAR file.
>
> While debugging I saw that "org.apache.commons.codec" is intentionally
> filtered by the classloader
>
> [https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/util/classloader/URLClassLoaderFirst.java#L305]
>
> How it is supposed to provide this library so that my application can use it?
>
> Thanks,
> Violeta
>
> {code}
> java.lang.ClassNotFoundException: org.apache.commons.codec.binary.Base64
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1285)
>
> org.apache.tomee.catalina.TomEEWebappClassLoader.loadClass(TomEEWebappClassLoader.java:208)
>
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1119)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TOMEE-2183) org.apache.commons.codec filtered by the classloader but not provided by TomEE WebProfile
[
https://issues.apache.org/jira/browse/TOMEE-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1651#comment-1651
]
Violeta Georgieva commented on TOMEE-2183:
--
[~jgallimore] just create an EAR file with "lib" folder that contains
"commons-codec" and from the WAR file try to load a class from "commons-codec"
> org.apache.commons.codec filtered by the classloader but not provided by
> TomEE WebProfile
> -
>
> Key: TOMEE-2183
> URL: https://issues.apache.org/jira/browse/TOMEE-2183
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 7.0.4
>Reporter: Violeta Georgieva
>Assignee: Jonathan Gallimore
>Priority: Major
>
> Hi,
>
> I have an EAR file with "lib" folder that contains "commons-codec" and a WAR
> file that uses the libraries located in the "lib" folder. I do not have
> issues with the other libraries in that folder but with "commons-codec" I
> receive the exception below.
>
> I'm using TomEE 7.0.4 WebProfile and in that distribution there is no
> "commons-codec" provided by TomEE itself because of this I'm providing it
> with the EAR file.
>
> While debugging I saw that "org.apache.commons.codec" is intentionally
> filtered by the classloader
>
> [https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/util/classloader/URLClassLoaderFirst.java#L305]
>
> How it is supposed to provide this library so that my application can use it?
>
> Thanks,
> Violeta
>
> {code}
> java.lang.ClassNotFoundException: org.apache.commons.codec.binary.Base64
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1285)
>
> org.apache.tomee.catalina.TomEEWebappClassLoader.loadClass(TomEEWebappClassLoader.java:208)
>
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1119)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (TOMEE-2183) org.apache.commons.codec filtered by the classloader but not provided by TomEE WebProfile
Violeta Georgieva created TOMEE-2183:
Summary: org.apache.commons.codec filtered by the classloader but
not provided by TomEE WebProfile
Key: TOMEE-2183
URL: https://issues.apache.org/jira/browse/TOMEE-2183
Project: TomEE
Issue Type: Bug
Components: TomEE Core Server
Affects Versions: 7.0.4
Reporter: Violeta Georgieva
Hi,
I have an EAR file with "lib" folder that contains "commons-codec" and a WAR
file that uses the libraries located in the "lib" folder. I do not have issues
with the other libraries in that folder but with "commons-codec" I receive the
exception below.
I'm using TomEE 7.0.4 WebProfile and in that distribution there is no
"commons-codec" provided by TomEE itself because of this I'm providing it with
the EAR file.
While debugging I saw that "org.apache.commons.codec" is intentionally filtered
by the classloader
[https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/util/classloader/URLClassLoaderFirst.java#L305]
How it is supposed to provide this library so that my application can use it?
Thanks,
Violeta
{code}
java.lang.ClassNotFoundException: org.apache.commons.codec.binary.Base64
org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1285)
org.apache.tomee.catalina.TomEEWebappClassLoader.loadClass(TomEEWebappClassLoader.java:208)
org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1119)
\{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (TOMEE-2183) org.apache.commons.codec filtered by the classloader but not provided by TomEE WebProfile
[
https://issues.apache.org/jira/browse/TOMEE-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Violeta Georgieva updated TOMEE-2183:
-
Description:
Hi,
I have an EAR file with "lib" folder that contains "commons-codec" and a WAR
file that uses the libraries located in the "lib" folder. I do not have issues
with the other libraries in that folder but with "commons-codec" I receive the
exception below.
I'm using TomEE 7.0.4 WebProfile and in that distribution there is no
"commons-codec" provided by TomEE itself because of this I'm providing it with
the EAR file.
While debugging I saw that "org.apache.commons.codec" is intentionally filtered
by the classloader
[https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/util/classloader/URLClassLoaderFirst.java#L305]
How it is supposed to provide this library so that my application can use it?
Thanks,
Violeta
{code}
java.lang.ClassNotFoundException: org.apache.commons.codec.binary.Base64
org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1285)
org.apache.tomee.catalina.TomEEWebappClassLoader.loadClass(TomEEWebappClassLoader.java:208)
org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1119)
{code}
was:
Hi,
I have an EAR file with "lib" folder that contains "commons-codec" and a WAR
file that uses the libraries located in the "lib" folder. I do not have issues
with the other libraries in that folder but with "commons-codec" I receive the
exception below.
I'm using TomEE 7.0.4 WebProfile and in that distribution there is no
"commons-codec" provided by TomEE itself because of this I'm providing it with
the EAR file.
While debugging I saw that "org.apache.commons.codec" is intentionally filtered
by the classloader
[https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/util/classloader/URLClassLoaderFirst.java#L305]
How it is supposed to provide this library so that my application can use it?
Thanks,
Violeta
{code}
java.lang.ClassNotFoundException: org.apache.commons.codec.binary.Base64
org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1285)
org.apache.tomee.catalina.TomEEWebappClassLoader.loadClass(TomEEWebappClassLoader.java:208)
org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1119)
\{code}
> org.apache.commons.codec filtered by the classloader but not provided by
> TomEE WebProfile
> -
>
> Key: TOMEE-2183
> URL: https://issues.apache.org/jira/browse/TOMEE-2183
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 7.0.4
>Reporter: Violeta Georgieva
>Priority: Major
>
> Hi,
>
> I have an EAR file with "lib" folder that contains "commons-codec" and a WAR
> file that uses the libraries located in the "lib" folder. I do not have
> issues with the other libraries in that folder but with "commons-codec" I
> receive the exception below.
>
> I'm using TomEE 7.0.4 WebProfile and in that distribution there is no
> "commons-codec" provided by TomEE itself because of this I'm providing it
> with the EAR file.
>
> While debugging I saw that "org.apache.commons.codec" is intentionally
> filtered by the classloader
>
> [https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/util/classloader/URLClassLoaderFirst.java#L305]
>
> How it is supposed to provide this library so that my application can use it?
>
> Thanks,
> Violeta
>
> {code}
> java.lang.ClassNotFoundException: org.apache.commons.codec.binary.Base64
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1285)
>
> org.apache.tomee.catalina.TomEEWebappClassLoader.loadClass(TomEEWebappClassLoader.java:208)
>
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1119)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (TOMEE-2054) When in EAR, the web app doc base is a directory ending with .war do not handle it as a file
[
https://issues.apache.org/jira/browse/TOMEE-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Violeta Georgieva updated TOMEE-2054:
-
Description:
When in the EAR file, the web application's binaries are a directory and the
directory name ends with .war, do not handle it as a file.
With the current implementation the exception below is thrown. Note that the
name of the directory inside of EAR file is *test.war* and not *test*.
{code}
07-Jun-2017 23:33:34.961 SEVERE
[ContainerBackgroundProcessor[StandardEngine[Catalina]]]
sun.reflect.NativeMethodAccessorImpl.invoke ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/test]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
at
org.apache.tomee.catalina.TomcatWebAppBuilder.deployWar(TomcatWebAppBuilder.java:651)
at
org.apache.tomee.catalina.TomcatWebAppBuilder.deployWebApps(TomcatWebAppBuilder.java:589)
at
org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:997)
at
org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:718)
at
org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:714)
at
org.apache.tomee.catalina.TomcatWebAppBuilder.checkHost(TomcatWebAppBuilder.java:2223)
at
org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:141)
at
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
at
org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1164)
at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1388)
at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1392)
at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1360)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.catalina.LifecycleException: Failed to start component
[org.apache.catalina.webresources.StandardRoot@71ffc4f4]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)
at
org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4842)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4974)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 16 more
Caused by: java.lang.IllegalArgumentException: The main resource set specified
[//test] is not valid
at
org.apache.catalina.webresources.StandardRoot.createMainResourceSet(StandardRoot.java:732)
at
org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:690)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 19 more
{code}
was:
When in the EAR file, the web application's binaries are a directory
and the directory name ends with .war, do not handle it as a file.
With the current implementation the exception below is thrown. Note that the
name of the directory inside of EAR file is *test.war* and not *test*.
{code}
07-Jun-2017 23:33:34.961 SEVERE
[ContainerBackgroundProcessor[StandardEngine[Catalina]]]
sun.reflect.NativeMethodAccessorImpl.invoke ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/test]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
at
org.apache.tomee.catalina.TomcatWebAppBuilder.deployWar(TomcatWebAppBuilder.java:651)
at
org.apache.tomee.catalina.TomcatWebAppBuilder.deployWebApps(TomcatWebAppBuilder.java:589)
at
org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:997)
at
org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:718)
at
org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:714)
at
org.apache.tomee.catalina.TomcatWebAppBuilder.checkHost(TomcatWebAppBuilder.java:2223)
at
org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:1
[jira] [Commented] (TOMEE-2054) When in EAR, the web app doc base is a directory ending with .war do not handle it as a file
[
https://issues.apache.org/jira/browse/TOMEE-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042566#comment-16042566
]
Violeta Georgieva commented on TOMEE-2054:
--
I created the following PR
https://github.com/apache/tomee/pull/69
> When in EAR, the web app doc base is a directory ending with .war do not
> handle it as a file
>
>
> Key: TOMEE-2054
> URL: https://issues.apache.org/jira/browse/TOMEE-2054
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 7.0.3
>Reporter: Violeta Georgieva
>
> When in the EAR file, the web application's binaries are a directory
> and the directory name ends with .war, do not handle it as a file.
> With the current implementation the exception below is thrown. Note that the
> name of the directory inside of EAR file is *test.war* and not *test*.
> {code}
> 07-Jun-2017 23:33:34.961 SEVERE
> [ContainerBackgroundProcessor[StandardEngine[Catalina]]]
> sun.reflect.NativeMethodAccessorImpl.invoke ContainerBase.addChild: start:
> org.apache.catalina.LifecycleException: Failed to start component
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/test]]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
> at
> org.apache.tomee.catalina.TomcatWebAppBuilder.deployWar(TomcatWebAppBuilder.java:651)
> at
> org.apache.tomee.catalina.TomcatWebAppBuilder.deployWebApps(TomcatWebAppBuilder.java:589)
> at
> org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:997)
> at
> org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:718)
> at
> org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:714)
> at
> org.apache.tomee.catalina.TomcatWebAppBuilder.checkHost(TomcatWebAppBuilder.java:2223)
> at
> org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:141)
> at
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
> at
> org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1164)
> at
> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1388)
> at
> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1392)
> at
> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1360)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.catalina.LifecycleException: Failed to start component
> [org.apache.catalina.webresources.StandardRoot@71ffc4f4]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)
> at
> org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4842)
> at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4974)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> ... 16 more
> Caused by: java.lang.IllegalArgumentException: The main resource set
> specified [//test] is not valid
> at
> org.apache.catalina.webresources.StandardRoot.createMainResourceSet(StandardRoot.java:732)
> at
> org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:690)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> ... 19 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (TOMEE-2054) When in EAR, the web app doc base is a directory ending with .war do not handle it as a file
Violeta Georgieva created TOMEE-2054:
Summary: When in EAR, the web app doc base is a directory ending
with .war do not handle it as a file
Key: TOMEE-2054
URL: https://issues.apache.org/jira/browse/TOMEE-2054
Project: TomEE
Issue Type: Bug
Components: TomEE Core Server
Affects Versions: 7.0.3
Reporter: Violeta Georgieva
When in the EAR file, the web application's binaries are a directory
and the directory name ends with .war, do not handle it as a file.
With the current implementation the exception below is thrown. Note that the
name of the directory inside of EAR file is *test.war* and not *test*.
{code}
07-Jun-2017 23:33:34.961 SEVERE
[ContainerBackgroundProcessor[StandardEngine[Catalina]]]
sun.reflect.NativeMethodAccessorImpl.invoke ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/test]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
at
org.apache.tomee.catalina.TomcatWebAppBuilder.deployWar(TomcatWebAppBuilder.java:651)
at
org.apache.tomee.catalina.TomcatWebAppBuilder.deployWebApps(TomcatWebAppBuilder.java:589)
at
org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:997)
at
org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:718)
at
org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:714)
at
org.apache.tomee.catalina.TomcatWebAppBuilder.checkHost(TomcatWebAppBuilder.java:2223)
at
org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:141)
at
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
at
org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1164)
at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1388)
at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1392)
at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1360)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.catalina.LifecycleException: Failed to start component
[org.apache.catalina.webresources.StandardRoot@71ffc4f4]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)
at
org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4842)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4974)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 16 more
Caused by: java.lang.IllegalArgumentException: The main resource set specified
[//test] is not valid
at
org.apache.catalina.webresources.StandardRoot.createMainResourceSet(StandardRoot.java:732)
at
org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:690)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 19 more
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (TOMEE-1993) When using symbolic links the @WebServlet is not processed
[
https://issues.apache.org/jira/browse/TOMEE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799080#comment-15799080
]
Violeta Georgieva commented on TOMEE-1993:
--
It's working.
Thanks,
Violeta
> When using symbolic links the @WebServlet is not processed
> --
>
> Key: TOMEE-1993
> URL: https://issues.apache.org/jira/browse/TOMEE-1993
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 7.0.2
>Reporter: Violeta Georgieva
>
> Hi,
> @WebServlet is not processed when the web app files are symbolic links, but
> the root web app directory is not.
> The use case is the following:
> TomEE structure:
> {code}
> - TomEE root
> ...
> - webapps
> - myapp
> content -> /some/other/location/...
> {code}
> When the root of the app (in my case my app dir is not a symbolic link) then
> the war path will point to the location under TomEE directory.
> https://github.com/apache/tomee/blob/master/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/Contexts.java#L62
> Later when processing the @WebServlet the actual file path will point to
> "/some/other/location/..." but the "info.name" will point to the location
> under TomEE directory.
> https://github.com/apache/tomee/blob/master/tomee/tomee-catalina/src/main/java/org/apache/catalina/startup/OpenEJBContextConfig.java#L569
> If I change the symbolic link to the following:
> {code}
> - TomEE root
> ...
> - webapps
> - myapp -> /some/other/location
> content -> /some/other/location/...
> {code}
> Then everything is OK and the servlets are found.
> I'm reproducing this with TomEE 7.0.2 and I do not reproduce this behavior
> with TomEE 1.7.2
> Best Regards,
> Violeta Georgieva
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TOMEE-1993) When using symbolic links the @WebServlet is not processed
[
https://issues.apache.org/jira/browse/TOMEE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798497#comment-15798497
]
Violeta Georgieva commented on TOMEE-1993:
--
Hi,
Can you please provide a link to the snapshot?
Thanks,
Violeta
> When using symbolic links the @WebServlet is not processed
> --
>
> Key: TOMEE-1993
> URL: https://issues.apache.org/jira/browse/TOMEE-1993
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 7.0.2
>Reporter: Violeta Georgieva
>
> Hi,
> @WebServlet is not processed when the web app files are symbolic links, but
> the root web app directory is not.
> The use case is the following:
> TomEE structure:
> {code}
> - TomEE root
> ...
> - webapps
> - myapp
> content -> /some/other/location/...
> {code}
> When the root of the app (in my case my app dir is not a symbolic link) then
> the war path will point to the location under TomEE directory.
> https://github.com/apache/tomee/blob/master/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/Contexts.java#L62
> Later when processing the @WebServlet the actual file path will point to
> "/some/other/location/..." but the "info.name" will point to the location
> under TomEE directory.
> https://github.com/apache/tomee/blob/master/tomee/tomee-catalina/src/main/java/org/apache/catalina/startup/OpenEJBContextConfig.java#L569
> If I change the symbolic link to the following:
> {code}
> - TomEE root
> ...
> - webapps
> - myapp -> /some/other/location
> content -> /some/other/location/...
> {code}
> Then everything is OK and the servlets are found.
> I'm reproducing this with TomEE 7.0.2 and I do not reproduce this behavior
> with TomEE 1.7.2
> Best Regards,
> Violeta Georgieva
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TOMEE-1993) When using symbolic links the @WebServlet is not processed
[
https://issues.apache.org/jira/browse/TOMEE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15796127#comment-15796127
]
Violeta Georgieva commented on TOMEE-1993:
--
Sure I'll test it.
Thanks,
Violeta
> When using symbolic links the @WebServlet is not processed
> --
>
> Key: TOMEE-1993
> URL: https://issues.apache.org/jira/browse/TOMEE-1993
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 7.0.2
>Reporter: Violeta Georgieva
>
> Hi,
> @WebServlet is not processed when the web app files are symbolic links, but
> the root web app directory is not.
> The use case is the following:
> TomEE structure:
> {code}
> - TomEE root
> ...
> - webapps
> - myapp
> content -> /some/other/location/...
> {code}
> When the root of the app (in my case my app dir is not a symbolic link) then
> the war path will point to the location under TomEE directory.
> https://github.com/apache/tomee/blob/master/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/Contexts.java#L62
> Later when processing the @WebServlet the actual file path will point to
> "/some/other/location/..." but the "info.name" will point to the location
> under TomEE directory.
> https://github.com/apache/tomee/blob/master/tomee/tomee-catalina/src/main/java/org/apache/catalina/startup/OpenEJBContextConfig.java#L569
> If I change the symbolic link to the following:
> {code}
> - TomEE root
> ...
> - webapps
> - myapp -> /some/other/location
> content -> /some/other/location/...
> {code}
> Then everything is OK and the servlets are found.
> I'm reproducing this with TomEE 7.0.2 and I do not reproduce this behavior
> with TomEE 1.7.2
> Best Regards,
> Violeta Georgieva
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TOMEE-1993) When using symbolic links the @WebServlet is not processed
[
https://issues.apache.org/jira/browse/TOMEE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15796086#comment-15796086
]
Violeta Georgieva commented on TOMEE-1993:
--
I have the following
{code}
{code}
this url works
http://localhost:8080/moviefun/
but this does not work because the annotation was not processed
http://localhost:8080/moviefun/moviefun
{code}
package org.superbiz.moviefun;
...
@WebServlet(urlPatterns={"/moviefun/*"})
public class ActionServlet extends HttpServlet {
...
}
{code}
> When using symbolic links the @WebServlet is not processed
> --
>
> Key: TOMEE-1993
> URL: https://issues.apache.org/jira/browse/TOMEE-1993
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 7.0.2
>Reporter: Violeta Georgieva
>
> Hi,
> @WebServlet is not processed when the web app files are symbolic links, but
> the root web app directory is not.
> The use case is the following:
> TomEE structure:
> {code}
> - TomEE root
> ...
> - webapps
> - myapp
> content -> /some/other/location/...
> {code}
> When the root of the app (in my case my app dir is not a symbolic link) then
> the war path will point to the location under TomEE directory.
> https://github.com/apache/tomee/blob/master/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/Contexts.java#L62
> Later when processing the @WebServlet the actual file path will point to
> "/some/other/location/..." but the "info.name" will point to the location
> under TomEE directory.
> https://github.com/apache/tomee/blob/master/tomee/tomee-catalina/src/main/java/org/apache/catalina/startup/OpenEJBContextConfig.java#L569
> If I change the symbolic link to the following:
> {code}
> - TomEE root
> ...
> - webapps
> - myapp -> /some/other/location
> content -> /some/other/location/...
> {code}
> Then everything is OK and the servlets are found.
> I'm reproducing this with TomEE 7.0.2 and I do not reproduce this behavior
> with TomEE 1.7.2
> Best Regards,
> Violeta Georgieva
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TOMEE-1993) When using symbolic links the @WebServlet is not processed
[
https://issues.apache.org/jira/browse/TOMEE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15796008#comment-15796008
]
Violeta Georgieva commented on TOMEE-1993:
--
Here it is:
{code}
macbook-pro:apache-tomee-webprofile-7.0.2 vgeorgieva$ pwd
/Users/vgeorgieva/Downloads/apache-tomee-webprofile-7.0.2
macbook-pro:apache-tomee-webprofile-7.0.2 vgeorgieva$ ls -lh webapps/
total 0
drwxr-xr-x 8 vgeorgieva staff 272B Jan 3 21:37 moviefun
macbook-pro:apache-tomee-webprofile-7.0.2 vgeorgieva$ ls -lh webapps/moviefun
total 48
lrwxr-xr-x 1 vgeorgieva staff45B Jan 3 21:36 META-INF ->
/Users/vgeorgieva/Downloads/moviefun/META-INF
lrwxr-xr-x 1 vgeorgieva staff44B Jan 3 21:37 WEB-INF ->
/Users/vgeorgieva/Downloads/moviefun/WEB-INF
lrwxr-xr-x 1 vgeorgieva staff43B Jan 3 21:36 assets ->
/Users/vgeorgieva/Downloads/moviefun/assets
lrwxr-xr-x 1 vgeorgieva staff48B Jan 3 21:37 default.css ->
/Users/vgeorgieva/Downloads/moviefun/default.css
lrwxr-xr-x 1 vgeorgieva staff46B Jan 3 21:37 index.jsp ->
/Users/vgeorgieva/Downloads/moviefun/index.jsp
lrwxr-xr-x 1 vgeorgieva staff46B Jan 3 21:37 setup.jsp ->
/Users/vgeorgieva/Downloads/moviefun/setup.jsp
{code}
> When using symbolic links the @WebServlet is not processed
> --
>
> Key: TOMEE-1993
> URL: https://issues.apache.org/jira/browse/TOMEE-1993
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 7.0.2
>Reporter: Violeta Georgieva
>
> Hi,
> @WebServlet is not processed when the web app files are symbolic links, but
> the root web app directory is not.
> The use case is the following:
> TomEE structure:
> {code}
> - TomEE root
> ...
> - webapps
> - myapp
> content -> /some/other/location/...
> {code}
> When the root of the app (in my case my app dir is not a symbolic link) then
> the war path will point to the location under TomEE directory.
> https://github.com/apache/tomee/blob/master/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/Contexts.java#L62
> Later when processing the @WebServlet the actual file path will point to
> "/some/other/location/..." but the "info.name" will point to the location
> under TomEE directory.
> https://github.com/apache/tomee/blob/master/tomee/tomee-catalina/src/main/java/org/apache/catalina/startup/OpenEJBContextConfig.java#L569
> If I change the symbolic link to the following:
> {code}
> - TomEE root
> ...
> - webapps
> - myapp -> /some/other/location
> content -> /some/other/location/...
> {code}
> Then everything is OK and the servlets are found.
> I'm reproducing this with TomEE 7.0.2 and I do not reproduce this behavior
> with TomEE 1.7.2
> Best Regards,
> Violeta Georgieva
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TOMEE-1993) When using symbolic links the @WebServlet is not processed
[
https://issues.apache.org/jira/browse/TOMEE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15795918#comment-15795918
]
Violeta Georgieva commented on TOMEE-1993:
--
In my case only the root web application directory is not a symbolic link, the
rest of the content is symbolic links.
WEB-INF/classes and WEB-INF/classes/* are not split by symbolic links.
> When using symbolic links the @WebServlet is not processed
> --
>
> Key: TOMEE-1993
> URL: https://issues.apache.org/jira/browse/TOMEE-1993
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 7.0.2
>Reporter: Violeta Georgieva
>
> Hi,
> @WebServlet is not processed when the web app files are symbolic links, but
> the root web app directory is not.
> The use case is the following:
> TomEE structure:
> {code}
> - TomEE root
> ...
> - webapps
> - myapp
> content -> /some/other/location/...
> {code}
> When the root of the app (in my case my app dir is not a symbolic link) then
> the war path will point to the location under TomEE directory.
> https://github.com/apache/tomee/blob/master/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/Contexts.java#L62
> Later when processing the @WebServlet the actual file path will point to
> "/some/other/location/..." but the "info.name" will point to the location
> under TomEE directory.
> https://github.com/apache/tomee/blob/master/tomee/tomee-catalina/src/main/java/org/apache/catalina/startup/OpenEJBContextConfig.java#L569
> If I change the symbolic link to the following:
> {code}
> - TomEE root
> ...
> - webapps
> - myapp -> /some/other/location
> content -> /some/other/location/...
> {code}
> Then everything is OK and the servlets are found.
> I'm reproducing this with TomEE 7.0.2 and I do not reproduce this behavior
> with TomEE 1.7.2
> Best Regards,
> Violeta Georgieva
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (TOMEE-1993) When using symbolic links the @WebServlet is not processed
Violeta Georgieva created TOMEE-1993:
Summary: When using symbolic links the @WebServlet is not processed
Key: TOMEE-1993
URL: https://issues.apache.org/jira/browse/TOMEE-1993
Project: TomEE
Issue Type: Bug
Components: TomEE Core Server
Affects Versions: 7.0.2
Reporter: Violeta Georgieva
Hi,
@WebServlet is not processed when the web app files are symbolic links, but the
root web app directory is not.
The use case is the following:
TomEE structure:
{code}
- TomEE root
...
- webapps
- myapp
content -> /some/other/location/...
{code}
When the root of the app (in my case my app dir is not a symbolic link) then
the war path will point to the location under TomEE directory.
https://github.com/apache/tomee/blob/master/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/Contexts.java#L62
Later when processing the @WebServlet the actual file path will point to
"/some/other/location/..." but the "info.name" will point to the location
under TomEE directory.
https://github.com/apache/tomee/blob/master/tomee/tomee-catalina/src/main/java/org/apache/catalina/startup/OpenEJBContextConfig.java#L569
If I change the symbolic link to the following:
{code}
- TomEE root
...
- webapps
- myapp -> /some/other/location
content -> /some/other/location/...
{code}
Then everything is OK and the servlets are found.
I'm reproducing this with TomEE 7.0.2 and I do not reproduce this behavior
with TomEE 1.7.2
Best Regards,
Violeta Georgieva
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
