CODEWITHSUNDEEP
mavenjbosswildflyweb-deploymentmaven-plugin
BenMansourNizar
BenMansourNizar

Reputation: 1628

Connection timed out when deploying on Jboss EAP 6.4 using maven plugin

I'm using Jboss EAP 6.4 and I want to use the maven jboss plugin to deploy on Jboss.
But I'm getting this error

Failed to execute goal org.jboss.as.plugins:jboss-as-maven-plugin:7.6.Final:undeploy (default-cli) on project MyProject: Could not execute goal undeploy on E:\Work\trunk\MyProject\target\MyProject.war. Reason: I/O Error could not execute operation '{
[ERROR] "operation" => "read-attribute",
[ERROR] "address" => [],
[ERROR] "name" => "launch-type"
[ERROR] }': java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9990. The connection timed out

this is my configuration

<plugin>
    <groupId>org.jboss.as.plugins</groupId>
    <artifactId>jboss-as-maven-plugin</artifactId>

    <configuration>
            <force>true</force>
            <hostname>127.0.0.1/hostname>
            <username>admin</username>
            <password>admin</password>
            <port>9990</port>
            <fileNames>
                <fileName>target/MyProject.war</fileName>
            </fileNames>
    </configuration>
</plugin>

I was able to log in at the admin jboss console using the password admin and admin (http://127.0.0.1:9990/console)

Upvotes: 0

Views: 1089

Answers (1)

James R. Perkins
James R. Perkins

Reputation: 17780

On JBoss EAP 6.4 the default native management port is 9999. The web console uses port 9990 as that is the http management port.

There also is no fileNames configuration property. The other properties, with the exception of the username and password are using the defaults so they shouldn't be required.

The username and password are also not generally required if you're deploying to localhost. The client should authenticate locally. Of course that does depend on how the server is configured.

Upvotes: 2

Related Questions