Junv Junv - 1 year ago 92
Java Question

jboss-as-maven-plugin can't deploy to remote JBoss AS7?

I've tried for days to use

to deploy web projects to remote JBoss AS7, but it didn't work.

Here is my

<!-- JBoss Application Server -->
<!-- Only remote server needs -->

Using this configuration I can deploy to localhost without
, even no

To deploy to my real IP address, I modified ${JBOSS_HOME}/configuration/standlone.xml, by changing
from to (to unbind JBoss address), so I can deploy projects by using:

<!-- is my ip -->

It works too, but by changing
to point to my other computer (in the same router) it doesn't work but that computer receives a request, and the request is cut by something. (I thought it may be JBoss)

The error message in Maven console is as follows:

INFO: JBoss Remoting version 3.2.0.CR8
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 30.572s
[INFO] Finished at: Fri Feb 10 23:41:25 CST 2012
[INFO] Final Memory: 18M/170M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.jboss.as.plugins:jboss-as-maven-plugin:7.1.0.
CR1b:deploy (default) on project MessagePushX-RELEASE: Could not execute goal de
ploy on MessagePush.war. Reason: java.net.ConnectException: JBAS012144: Could no
t connect to remote:// The connection timed out -> [Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions, please rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Who can tell me is JBoss as 7.1.0 is not allowed remote deploy?

For some security issues?

Answer Source

It is definitely not a security issue.

The plugin you are referring uses the JBoss AS7 ability to deploy applications using the Server Deployment Manager (this is new feature in AS7). Previously the deployment was only possible via JMX console, which required the deployment artifact to be reachable by server (local file or URL).

You need to make sure:

  • is running JBoss AS7 with Server Deployment Manager listening on port 9999.
  • The port should not be bound to localhost iface (not but *:9999).
  • There is no firewall between you and rejecting packets to port 9999.
Recommended from our users: Dynamic Network Monitoring from WhatsUp Gold from IPSwitch. Free Download