« Return to Thread: cargo offline deploy fails

Re: cargo offline deploy fails

by John Singleton-2 :: Rate this Message:

jboss-web.xml:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.3//EN"
"http://www.jboss.org/j2ee/dtd/jboss-web_3_0.dtd">
<jboss-web>
<security-domain>java:/jaas/cert</security-domain>
<context-root>prism</context-root>
</jboss-web>

This is the original that did not work.
Changing to "jboss-web_3_0.dtd" also did not work.
Changing to "/home/jhsingl/prism-home/prism/pkg/jboss/docs/dtd/jboss-web_3_0.dtd" did work.

Cheers,
John Singleton

On Wed, Jul 27, 2011 at 1:47 PM, S. Ali Tokmen <nospam@...> wrote:

Can you please provide a copy of your jboss-web.xml file as well?
Thank you
S. Ali Tokmen
http://ali.tokmen.com/

GSM (ch): +41 79 207 29 22 [Swisscom]
GSM (fr): +33 66 43 00 555 [Orange]
GSM (tr): +90 555 266 52 73 [Avea]

My AIM, ICQ, MSN Messenger and Yahoo IM
contact details are on http://contact.ali.tokmen.com
On 2011/07/27 16:06, John Singleton wrote:
I am not able to copy files from the disconnected machine back to the connected machine. I simulated the issue by turning off the eth0 interface on my connected machine and running "mvn -o -X install". I believe the traces are essentially the same. You can see the result at http://pastebin.com/f8dYDGXj

Hope this helps,

John Singleton
On Tue, Jul 26, 2011 at 4:54 PM, S. Ali Tokmen <nospam@...> wrote:
Thank you, John. So I think the issues are the same.

Can you please also share with us the full stack trace on the Maven side?
Thank you
S. Ali Tokmen
http://ali.tokmen.com/

GSM (ch): +41 79 207 29 22 [Swisscom]
GSM (fr): +33 66 43 00 555 [Orange]
GSM (tr): +90 555 266 52 73 [Avea]

My AIM, ICQ, MSN Messenger and Yahoo IM
contact details are on http://contact.ali.tokmen.com
On 2011/07/26 22:44, John Singleton wrote:
Thanks, Ali. This workaround works, sort of. If I just give the bare filename to the dtd as described, then cargo:deploy looks for it in my current (build) directory. If I give it a full pathname to the jboss installation, cargo:deploy is happy, but this is not portable across developers. I tried using ${jboss.home} to locate the dtd, together with using the <filteringDeploymentDescriptors> configuration on m-war-p, but that doesn't work: it filters web.xml but not jboss-web.xml. I guess I can use a maven-ant task to filter the dtd pathname so I can make this work for now. Hope this helps you find what (if anything) needs to change in cargo.

Cheers,
John Singleton
On Tue, Jul 26, 2011 at 1:20 PM, S. Ali Tokmen <nospam@...> wrote:
Hello

This behaviour looks like https://jira.codehaus.org/browse/CARGO-956

Can you please try the workaround described in the ticket?

If it does work, I guess we'll simply need to apply the "same" fix.

Thank you
S. Ali Tokmen
http://ali.tokmen.com/

GSM (ch): +41 79 207 29 22 [Swisscom]
GSM (fr): +33 66 43 00 555 [Orange]
GSM (tr): +90 555 266 52 73 [Avea]

My AIM, ICQ, MSN Messenger and Yahoo IM
contact details are on http://contact.ali.tokmen.com
On 2011/07/26 17:16, John Singleton wrote:

[reposting from maven user list as suggested]

I have a maven war project and am using maven-cargo-plugin to deploy the war
to the container and also to start/stop the container for functional
testing. All works well on an internet-connected machine, but when I try to
execute my build on a disconnected machine, the cargo:deploy fails. I have
copied the source tree and my maven repository to the disconnected machine
and am running "mvn -o". All other parts of the build complete
successfully. If I manually deploy the war and start the container, the
functional tests run successfully. The disconnected machine is on a
completely isolated network, not just behind a firewall. I have read the
cargo documentation and do not see anything that addresses this use-case.
Judging from the trace, it appears to be trying to contact
www.jboss.org(perhaps trying to validate the war???) Is there a
mistake in my
configuration, or a way to work around this issue?

Thanks,
John Singleton

The failure: (hand typed so possible typos...)
[cargo:deploy {execution: copy-to-jboss}]
Parsed JBoss version = [5.1.0]
------------------------------
----
FATAL ERROR
---------------------------------
Failed to create deployable with implementation class
org.codehaus.cargo.container.jboss.deployable.JBossWAR for the parameters
(container [id = [jboss51x]], deployable type [war])
www.jboss.org
Trace
org.codehaus.cargo.container.ContainerException: Failed to create...
at
org.codehaus.cargo.generic.spi.AbstractGenericHintFactory.createImplementation(AbstractGenericHintFactory.java:154)
---snip---
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
---snip---
Caused by: org.codehaus.cargo.container.ContainerException: Failed to parse
JBoss WAR file in [correct_path_name_here]
at:
org.codehaus.cargo.container.jboss.deployable.JBossWAR.<init>(JBossWAR.java:56)
---snip---
Caused by: java.net.UnknownHostException: www.jboss.org
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
---snip---

maven version 2.2.1
cargo version 1.1.1
java version 1.6.0_20 (connected)/1.6.0_23(disconnected)
OS: ubuntu 11.04 (connected)/RedHat (disconnected)
container: jBoss 5.1

This is the cargo configuration, as specified in the pluginManagement
section of my parent/aggregator pom:

<plugin>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven2-plugin</artifactId>
<version>${version.cargo}</version>
<configuration>
<deployer>
<deployables>
<deployable>
<location>${project.build.directory}/${project.build.finalName}.${project.packaging}</location>
</deployable>
</deployables>
</deployer>
<container>
<containerId>jboss51x</containerId>
<home>${jboss.home}</home>
<type>installed</type>
<systemProperties>
<javax.net.ssl.keyStore>
XXX
</javax.net.ssl.keyStore>
<javax.net.ssl.keyStorePassword>
XXX
</javax.net.ssl.keyStorePassword>
<javax.net.ssl.trustStore>
XXX
</javax.net.ssl.trustStore>
<javax.net.ssl.trustStorePassword>
XXX
</javax.net.ssl.trustStorePassword>
<jena.config.file>
${jena.config.file}
</jena.config.file>
</systemProperties>
</container>
<configuration>
<type>existing</type>
<home>${jboss.server.dir}</home>
<properties>
<cargo.jvmargs>-XX:PermSize=512m -XX:MaxPermSize=1024</cargo.jvmargs>
<cargo.jboss.configuration>
default
</cargo.jboss.configuration>
<cargo.protocol>
https
</cargo.protocol>
<cargo.servlet.port>
8443
</cargo.servlet.port>
<cargo.secure>true</cargo.secure>
<cargo.rmi.port>1099</cargo.rmi.port>
<cargo.client.auth>true</cargo.client.auth>
<cargo.hostname>${jboss.hostname}</cargo.hostname>
</properties>
</configuration>
</configuration>
</plugin>

« Return to Thread: cargo offline deploy fails