axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Reinhold (JIRA)" <>
Subject [jira] [Commented] (AXIS2-5444) FileNotFound exception deploying to specific context on Tomcat 7
Date Thu, 01 Nov 2012 14:35:12 GMT


Brian Reinhold commented on AXIS2-5444:

Okay, that was news to me. Learn something new every day. I have only deployed war files in
the webapps directory the old-fashioned way. So might I suggest renaming the war file to axis2.war
and seeing if that works. That would localize the bug better should it work. If that doesn't
work, look inside the war file and see if its contents make sense (see that it has the expected
directories and files). In case you don't know how to do that rename the file to
and then you can take a peek (at least on Windows you can).
> FileNotFound exception deploying to specific context on Tomcat 7
> ----------------------------------------------------------------
>                 Key: AXIS2-5444
>                 URL:
>             Project: Axis2
>          Issue Type: Bug
>          Components: deployment
>    Affects Versions: 1.6.2
>         Environment: Ubuntu 12.04, Tomcat 7.0.32
>            Reporter: Ben Williams
> When I try to deploy the vanilla 1.6.2 axis2.war to a subdirectory context, like /v30/axis2,
I get the exception at the bottom of this description during deployment.
> Steps to reproduce:
> 1. Copy axis2.war to ${TOMCAT_HOME}/webapps/v30#axis2.war
> 2. Start Tomcat with "${TOMCAT_HOME}/bin/ start"
> Expected result:
> axis2.war deploys to /v30/axis2 context without error and is accessible at http://localhost:8080/v30/axis2
> Actual result:
> FileNotFound exception and this stacktrace printed to console:
> [WARN] Exception extracting jars into temporary directory :
/opt/apache-tomcat-7.0.32/webapps/v30 (No such file or directory) : 
> switching to alternate class loading mechanism
> [ERROR] The mtompolicy-1.6.2.mar module, which is not valid, caused
/opt/apache-tomcat-7.0.32/webapps/v30 (No such file or direc
> tory)
> [INFO] Deploying Exception Occured with /opt/apache-tomcat-7.0.32/webapps/v30
(No such file or directory)
> java.lang.RuntimeException: /opt/apache-tomcat-7.0.32/webapps/v30
(No such file or directory)
>   at org.apache.axis2.deployment.util.Utils.findLibJars(
>   at org.apache.axis2.deployment.util.Utils.createClassLoader(
>   at org.apache.axis2.jaxws.framework.JAXWSDeployer.deployServicesInWARClassPath(
>   at org.apache.axis2.jaxws.framework.JAXWSDeployer.init(
>   at org.apache.axis2.deployment.DeploymentEngine.initializeDeployers(
>   at org.apache.axis2.deployment.DeploymentEngine.setConfigContext(
>   at org.apache.axis2.deployment.WarBasedAxisConfigurator.setConfigContext(
>   at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(
>   at org.apache.axis2.transport.http.AxisServlet.initConfigContext(
>   at org.apache.axis2.transport.http.AxisServlet.init(
>   at org.apache.catalina.core.StandardWrapper.initServlet(
>   at org.apache.catalina.core.StandardWrapper.loadServlet(
>   at org.apache.catalina.core.StandardWrapper.load(
>   at org.apache.catalina.core.StandardContext.loadOnStartup(
>   at org.apache.catalina.core.StandardContext.startInternal(
>   at org.apache.catalina.util.LifecycleBase.start(
>   at org.apache.catalina.core.ContainerBase.addChildInternal(
>   at org.apache.catalina.core.ContainerBase.addChild(
>   at org.apache.catalina.core.StandardHost.addChild(
>   at org.apache.catalina.startup.HostConfig.deployWAR(
>   at org.apache.catalina.startup.HostConfig$
>   at java.util.concurrent.Executors$
>   at java.util.concurrent.FutureTask$Sync.innerRun(
>   at
>   at java.util.concurrent.ThreadPoolExecutor.runWorker(
>   at java.util.concurrent.ThreadPoolExecutor$
>   at
> Caused by: /opt/apache-tomcat-7.0.32/webapps/v30 (No such
file or directory)
>   at Method)
>   at<init>(
>   at<init>(
>   at
>   at
>   at
>   at org.apache.axis2.deployment.util.Utils.findLibJars(
>   ... 26 more

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message