Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-31794

Wildfly Deployer plugin error

XMLWordPrintable

      I'm working in a project using Jenkins. I tried to deploy a War file to Jboss server with Wildfly Deployer plugin.
      When I deploy with Jboss AS 8 server (renamed to Wildfly) => It worked.
      But when I deploy with Jboss AS 7(or older) or Jboss EAP => It failed(Error: FATAL: Unable to connect to controller.).

      In the main page of Wildfly Deployer plugin(https://wiki.jenkins-ci.org/display/JENKINS/WildFly+Deployer+Plugin) they said:
      "Deploys an application to a WildFly/JBoss server or server group."

      Why it is not work with me.

          [JENKINS-31794] Wildfly Deployer plugin error

          Dan Dillingham added a comment -

          The WildFly Deployer Plugin works with WildFly and JBoss EAP versions that use http remoting for CLI access. Its been tested with WildFly 8.1 and JBoss EAP 7.0 Beta.

          JBoss EAP 6.4 is not supported.

          Dan Dillingham added a comment - The WildFly Deployer Plugin works with WildFly and JBoss EAP versions that use http remoting for CLI access. Its been tested with WildFly 8.1 and JBoss EAP 7.0 Beta. JBoss EAP 6.4 is not supported.

          Dan Dillingham added a comment -

          see latest comment

          Dan Dillingham added a comment - see latest comment

          Erra Jaggi added a comment -

          Hi Dan,

          could you please share the commands to use for http remoting for CLI access on JBoss EAP 7.

          Erra Jaggi added a comment - Hi Dan, could you please share the commands to use for http remoting for CLI access on JBoss EAP 7.

          aron christopher added a comment -

          I think if the datasource is properly configured this plugin may work

          aron christopher added a comment - I think if the datasource is properly configured this plugin may work

          aron christopher added a comment -

          and also the socket binding management for port 9990 should be set to public in standalone.xml file

          aron christopher added a comment - and also the socket binding management for port 9990 should be set to public in standalone.xml file

          aron christopher added a comment -

          Anyone having any update about this plugin?

          aron christopher added a comment - Anyone having any update about this plugin?

            ddilling Dan Dillingham
            nvccntt Peter Nhu
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: