0 Replies Latest reply on May 6, 2012 5:07 PM by jambay

    Minimum JBoss 7 configuration file that is able to deploy

    jambay Newbie

      I'm running a server in an environment where available ports are limited. I'm trying with a standalone server and removing parts of the standalone.xml configuration for the socket-bindings to reduce the ports required. Here is the message I've been seeing when trying a to only use the http socket binding when I deploy a simple.war file:


      13:55:53,991 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "simple.war" was rolled back with failure message JBAS014750: Operation handler failed to complete

      13:55:54,027 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015877: Stopped deployment simple.war in 35ms

      13:55:54,028 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "JBAS014750: Operation handler failed to complete"}}


      What is the minimum socket bindings required to make sure a deployment still works? It appears I can get away with also doing transactions like this:


              <socket-binding name="http" port="8080"/>

              <socket-binding name="txn-recovery-environment" port="4712"/>

              <socket-binding name="txn-status-manager" port="4713"/>


      Can I get rid of the transaction socket bindings too and still do a deployment?