Problem deploying EAR at domain EAP 6.0
First of all , sorry for hijacking other post at this forum, I thought that my problem was the same that the one at the commented post.
We are having a similar problem at our Production Box, while we are deploying ok at Development Box with the same setup.
[DEBUG] Configuring mojo org.jboss.as.plugins:jboss-as-maven-plugin:7.3.Final:deploy from plugin realm ClassRealm[plugin>org.jboss.as.plugins:jboss-as-maven-plugin:7.3.Final, parent: sun.misc.Launcher$AppClassLoader@35ce36]
[DEBUG] Configuring mojo 'org.jboss.as.plugins:jboss-as-maven-plugin:7.3.Final:deploy' with basic configurator -->
[DEBUG] (f) checkPackaging = false
[DEBUG] (f) serverGroups = [misumi-group]
[DEBUG] (f) profiles = [default, ha, full, full-ha]
[DEBUG] (f) domain = org.jboss.as.plugin.deployment.domain.Domain@578dfb
[DEBUG] (f) filename = MISUMI-ear.ear
[DEBUG] (f) force = true
[DEBUG] (f) hostname = slx00010479.xxxxxxxx.es
[DEBUG] (f) password = xxxxxx
[DEBUG] (f) port = 9999
[DEBUG] (f) project = MavenProject: es.xxxxxxx:MISUMI:1.0-SNAPSHOT @ /home/ic/jenkins/jenkins_home/workspace/misumi_kepa_desa/pom.xml
[DEBUG] (f) skip = false
[DEBUG] (f) targetDir = /home/ic/jenkins/jenkins_home/workspace/misumi_kepa_desa/target
[DEBUG] (f) username = admin
[DEBUG] -- end configuration --
Current policy properties:
mmc.sess_pe_act.block_unsigned: false
window.num_max: 5
jscan.sess_applet_act.sig_trusted: pass
file.destructive.state: disabled
jscan.sess_applet_act.block_all: false
window.num_limited: true
jscan.sess_applet_act.unsigned: instrument
mmc.sess_pe_act.action: validate
jscan.session.daemon_protocol: http
file.read.state: enabled
mmc.sess_pe_act.block_invalid: true
mmc.sess_pe_act.block_blacklisted: false
net.bind_enable: false
jscan.session.policyname: TU1DIERlZmF1bHQgUG9saWN5
mmc.sess_cab_act.block_unsigned: false
file.nondestructive.state: disabled
jscan.session.origin_uri: http://repo1.maven.org/maven2/org/jboss/as/plugins/jboss-as-maven-plugin/7.3.Final/jboss-as-maven-plugin-7.3.Final.jar
mmc.sess_cab_act.action: validate
net.connect_other: false
jscan.session.user_ipaddr: 127.0.0.1
jscan.sess_applet_act.sig_invalid: block
mmc.sess_cab_act.block_invalid: true
thread.thread_num_max: 8
jscan.sess_applet_act.sig_blacklisted: block
net.connect_src: true
thread.thread_num_limited: true
jscan.sess_applet_act.stub_out_blocked_applet: true
mmc.sess_cab_act.block_blacklisted: false
mmc.sess_pe_act.enforce_for_com_objects_only: true
thread.threadgroup_create: false
file.write.state: enabled
23-ene-2013 15:21:19 org.xnio.Xnio <clinit>
INFO: XNIO Version 3.0.7.GA
23-ene-2013 15:21:19 org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.0.7.GA
23-ene-2013 15:21:19 org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 3.2.12.GA
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] MISUMI Maven Enterprise Application ............... FAILURE [6.670s]
[INFO] MISUMI-web Java EE 6 Webapp ....................... SKIPPED
[INFO] MISUMI-ear JavaEE6 Assembly ....................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7.215s
[INFO] Finished at: Wed Jan 23 15:21:25 CET 2013
[INFO] Final Memory: 7M/16M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.jboss.as.plugins:jboss-as-maven-plugin:7.3.Final:deploy (default-cli) on project MISUMI: Could not execute goal deploy on /home/ic/jenkins/jenkins_home/workspace/misumi_kepa_desa/target/MISUMI-ear.ear. Reason: Error could not execute operation '{
[ERROR] "address" => [],
[ERROR] "operation" => "read-attribute",
[ERROR] "name" => "launch-type"
[ERROR] }'. java.net.ConnectException: JBAS012144: Could not connect to remote://slx00010479.xxxxxxx.es:9999. The connection timed out
[ERROR] -> [Help 1]
If we use "<force>true</force> then we get this error....but if we do not use <force> at pom.xml , then we get this :
Current policy properties:
mmc.sess_pe_act.block_unsigned: false
window.num_max: 5
jscan.sess_applet_act.sig_trusted: pass
file.destructive.state: disabled
jscan.sess_applet_act.block_all: false
window.num_limited: true
jscan.sess_applet_act.unsigned: instrument
mmc.sess_pe_act.action: validate
jscan.session.daemon_protocol: http
file.read.state: enabled
mmc.sess_pe_act.block_invalid: true
mmc.sess_pe_act.block_blacklisted: false
net.bind_enable: false
jscan.session.policyname: TU1DIERlZmF1bHQgUG9saWN5
mmc.sess_cab_act.block_unsigned: false
file.nondestructive.state: disabled
jscan.session.origin_uri: http://repo1.maven.org/maven2/org/jboss/as/plugins/jboss-as-maven-plugin/7.3.Final/jboss-as-maven-plugin-7.3.Final.jar
mmc.sess_cab_act.action: validate
net.connect_other: false
jscan.session.user_ipaddr: 127.0.0.1
jscan.sess_applet_act.sig_invalid: block
mmc.sess_cab_act.block_invalid: true
thread.thread_num_max: 8
jscan.sess_applet_act.sig_blacklisted: block
net.connect_src: true
thread.thread_num_limited: true
jscan.sess_applet_act.stub_out_blocked_applet: true
mmc.sess_cab_act.block_blacklisted: false
mmc.sess_pe_act.enforce_for_com_objects_only: true
thread.threadgroup_create: false
file.write.state: enabled
23-ene-2013 15:28:56 org.xnio.Xnio <clinit>
INFO: XNIO Version 3.0.7.GA
23-ene-2013 15:28:56 org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.0.7.GA
23-ene-2013 15:28:56 org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 3.2.12.GA
and the process remains for ever.....
This is our configuration, properties are overwritten by Maven settings.xml
<plugin>
<groupId>org.jboss.as.plugins</groupId>
<artifactId>jboss-as-maven-plugin</artifactId>
<version>7.3.Final</version>
<inherited>false</inherited>
<configuration>
<!-- <force>true</force> -->
<hostname>${misumi_hostname}</hostname>
<port>${misumi_port}</port>
<username>${misumi_username}</username>
<password>${misumi_password}</password>
<filename>MISUMI-ear.ear</filename>
<domain>
<server-groups>
<server-group>${misumi_grupo}</server-group>
</server-groups>
<profiles>
<profile>default</profile>
<profile>ha</profile>
<profile>full</profile>
<profile>full-ha</profile>
</profiles>
</domain>
<checkPackaging>false</checkPackaging>
</configuration>
</plugin>
Could anybody help ?