]
Brian Stansberry resolved WFLY-3684.
------------------------------------
Resolution: Rejected
WildFly by default does not open a socket for the native management interface on port
9999. JBoss Remoting based management now use HTTP Upgrade via the http management
interface on port 9990.
If you want to try to still use the jboss-as-maven-plugin you can restore the
native-interface element to the management section of the config. Better though is to use
the wildfly-maven-plugin:
JBAS012144: Could not connect to remote://localhost:9999. The
connection timed out
----------------------------------------------------------------------------------
Key: WFLY-3684
URL:
https://issues.jboss.org/browse/WFLY-3684
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Domain Management
Affects Versions: 8.1.0.Final
Environment: Ubuntu 12.04.4
Reporter: Perry Anderson
Assignee: Brian Stansberry
Labels: mvn
the mvn jboss-as:deploy operation times out complaining that it could not connect:
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 13.662s
[INFO] Finished at: Tue Jul 29 01:26:12 UTC 2014
[INFO] Final Memory: 19M/174M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.jboss.as.plugins:jboss-as-maven-plugin:7.4.Final:deploy (default-cli) on project
jboss-kitchensink-rf: Could not execute goal deploy on
/home/jboss/workspace/jboss-kitchensink-rf/target/jboss-kitchensink-rf.war. Reason: I/O
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://localhost:9999. The connection timed out
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the
following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
I tried the same project with EAP 6.0 and mvn command works fine. This is an issue
narrowed down to 8.1.0.Final.