Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] jetty and cargo-jetty-deployer problem 
Hi Jan, thanks for responding.
I'm afraid there's no jetty log activity happening whenever I do the cargo deploy process. The process just fails with a HTTP ERROR 404 - Not Found. 

More info:
When I go to the link http://www.hostname.com/cargo-jetty-deployer/deploy, I get a HTTP ERROR 404 - Not Found. But if I go to http://www.hostname.com/cargo-jetty-deployer (without the /deploy part of the url), I get a directory listing which includes META-INF and WEB-INF folders. This means that cargo-jetty-deployer.war is actually deployed and running. The /deploy part of the url is necessary and used by the cargo deployer app to identify which action to do; deploy, undeploy, etc.
It seems like the url (with the /deploy part) is treated by jetty as part of the context path that's why jetty can't find it? 

-don

Jan Bartel wrote:

Don,

We're going to need some more info - do you have any jetty log output
or stack traces?

Jan

On 06/11/10 06:09, Don Santillan wrote:

up up

Don Santillan wrote:

Hello,

I'm using the latest cargo release, 1.0.4, and the latest jetty
release, 7.2.0.v20101020. In the older versions of this two
techologies (cargo 1.0.1 and jetty 7.1.4), mvn cargo:deploy was
working fine. Not until I updated to these latest versions.

I'm getting this:
[INFO] [cargo:deploy {execution: default-cli}]
[INFO]
------------------------------------------------------------------------ 
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------ 
[INFO] Failed to deploy [/path/to/webapp/root.war]
Response when calling
http://www.hostname.com:80/cargo-jetty-deployer/deploy?path=/ was:
[INFO]
------------------------------------------------------------------------ 
[INFO] Trace
org.codehaus.cargo.container.ContainerException: Failed to deploy
[/path/to/webapp/root.war]
at
org.codehaus.cargo.container.jetty.JettyRemoteDeployer.deploy(JettyRemoteDeployer.java:121) 
at
org.codehaus.cargo.maven2.DeployerDeployMojo.performDeployerActionOnSingleDeployable(DeployerDeployMojo.java:80) 
at
org.codehaus.cargo.maven2.AbstractDeployerMojo.performDeployerActionOnAllDeployables(AbstractDeployerMojo.java:115) 
at
org.codehaus.cargo.maven2.AbstractDeployerMojo.doExecute(AbstractDeployerMojo.java:58) 
at
org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:268) 
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) 
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) 
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) 
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) 
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) 
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) 
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) 
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) 
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
at java.lang.reflect.Method.invoke(Method.java:616)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) 
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.codehaus.cargo.container.ContainerException: Response
when calling
http://www.hostname.com:80/cargo-jetty-deployer/deploy?path=/ was:
at
org.codehaus.cargo.container.jetty.JettyRemoteDeployer.deploy(JettyRemoteDeployer.java:114) 
... 23 more
org.codehaus.cargo.container.ContainerException: Response when calling
http://www.hostname.com:80/cargo-jetty-deployer/deploy?path=/ was:
at
org.codehaus.cargo.container.jetty.JettyRemoteDeployer.deploy(JettyRemoteDeployer.java:114) 
at
org.codehaus.cargo.maven2.DeployerDeployMojo.performDeployerActionOnSingleDeployable(DeployerDeployMojo.java:80) 
at
org.codehaus.cargo.maven2.AbstractDeployerMojo.performDeployerActionOnAllDeployables(AbstractDeployerMojo.java:115) 
at
org.codehaus.cargo.maven2.AbstractDeployerMojo.doExecute(AbstractDeployerMojo.java:58) 
at
org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:268) 
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) 
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) 
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) 
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) 
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) 
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) 
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) 
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) 
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
at java.lang.reflect.Method.invoke(Method.java:616)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) 
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]
------------------------------------------------------------------------ 
[INFO] Total time: 46 seconds
[INFO] Finished at: Fri Nov 05 21:41:28 PHT 2010
[INFO] Final Memory: 17M/302M


I also tried accessing directly the url
http://www.hostname.com/cargo-jetty-deployer/deploy?path=/
<http://ec2-50-16-49-248.compute-1.amazonaws.com/cargo-jetty-deployer/deploy> 
but it display the error:


    HTTP ERROR 404

Problem accessing /cargo-jetty-deployer/deploy. Reason:

     Not Found
------------------------------------------------------------------------ 
/Powered by Jetty:///


It seems like this url is being blocked somehow.

I also tried the same link running the old version of cargo and jetty
and it went through.

Anybody experienced this issue?


-don





_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-users

Back to the top