2 Replies Latest reply on Jun 17, 2014 7:04 AM by rareddy

    wildfly 8 with eclipse

    724150880

      hello , i want to use eclipse to debug jboss EAP 6.1 + TEIID 8.8 ,and i use Eclipse Java EE IDE for Web Developers for version 4.2. but when i create a new server ,there isn't the option of Jboss EAP.

      90d7be72-db26-4cac-87e7-55c8fa9a3036.jpg

       

      and i see the wildfly option , so i want to know if threre is a match version of teiid for wildfly ?

       

       

       

      by the way , i startup the wildfly 8 by bingding address 192.168.7.88  which is correct , it occurs errors:

       

      17:42:10,743 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-15) JBAS017531: Host default-host starting

      17:42:10,778 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-17) MSC000001: Failed to start service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener

              at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:135)

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]

              at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]

      Caused by: java.net.BindException: Address already in use

              at sun.nio.ch.Net.bind0(Native Method) [rt.jar:1.7.0_25]

              at sun.nio.ch.Net.bind(Net.java:444) [rt.jar:1.7.0_25]

              at sun.nio.ch.Net.bind(Net.java:436) [rt.jar:1.7.0_25]

              at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214) [rt.jar:1.7.0_25]

              at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) [rt.jar:1.7.0_25]

              at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67) [rt.jar:1.7.0_25]

              at org.xnio.nio.NioXnioWorker.createTcpConnectionServer(NioXnioWorker.java:175)

              at org.xnio.XnioWorker.createStreamConnectionServer(XnioWorker.java:242) [xnio-api-3.2.0.Final.jar:3.2.0.Final]

              at org.wildfly.extension.undertow.HttpListenerService.startListening(HttpListenerService.java:112)

              at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:132)

              ... 5 more

       

       

      17:42:10,960 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

      17:42:10,960 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-24) JBAS010400: Bound data source [java:/sybiq85DS]

      17:42:10,961 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-24) JBAS010400: Bound data source [java:/sybiq88DS]

      17:42:10,961 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-24) JBAS010400: Bound data source [java:/mysql82DS]

      17:42:11,002 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-20) JBAS015012: Started FileSystemDeploymentService for directory /jboss/wildfly-8.0.0.Final/standalone/deployments

      17:42:11,005 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-14) JBAS015876: Starting deployment of "MyTest-vdb.xml" (runtime-name: "MyTest-vdb.xml")

      17:42:11,044 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-11) MSC000001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: JBAS015811: Failed to start the http-interface service

              at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:258) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]

              at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]

      Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use

              at org.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpServer.java:156) [wildfly-domain-http-interface-8.0.0.Final.jar:8.0.0.Final]

              at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:224) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]

              ... 5 more

      Caused by: java.net.BindException: Address already in use

              at sun.nio.ch.Net.bind0(Native Method) [rt.jar:1.7.0_25]

              at sun.nio.ch.Net.bind(Net.java:444) [rt.jar:1.7.0_25]

              at sun.nio.ch.Net.bind(Net.java:436) [rt.jar:1.7.0_25]

              at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214) [rt.jar:1.7.0_25]

              at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) [rt.jar:1.7.0_25]

              at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67) [rt.jar:1.7.0_25]

              at org.xnio.nio.NioXnioWorker.createTcpConnectionServer(NioXnioWorker.java:175)

              at org.xnio.XnioWorker.createStreamConnectionServer(XnioWorker.java:242) [xnio-api-3.2.0.Final.jar:3.2.0.Final]

              at org.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpServer.java:135) [wildfly-domain-http-interface-8.0.0.Final.jar:8.0.0.Final]

              ... 6 more

       

       

      17:42:11,119 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([

          ("core-service" => "management"),

          ("management-interface" => "http-interface")

      ]) - failure description: {"JBAS014671: Failed services" => {"jboss.serverManagement.controller.management.http" => "org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: JBAS015811: Failed to start the http-interface service

          Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use

          Caused by: java.net.BindException: Address already in use"}}

      17:42:11,122 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "MyTest-vdb.xml")]) - failure description: {"JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {

          "Services that were unable to start:" => ["jboss.deployment.unit.\"MyTest-vdb.xml\".INSTALL"],

          "Services that may be the cause:" => ["jboss.remoting.remotingConnectorInfoService.http-remoting-connector"]

      }}

      17:42:11,125 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: {"JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {

          "Services that were unable to start:" => ["jboss.ws.config"],

          "Services that may be the cause:" => ["jboss.remoting.remotingConnectorInfoService.http-remoting-connector"]

      }}

      17:42:11,126 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([

          ("subsystem" => "undertow"),

          ("server" => "default-server"),

          ("http-listener" => "default")

      ]) - failure description: {"JBAS014671: Failed services" => {"jboss.undertow.listener.default" => "org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener

          Caused by: java.net.BindException: Address already in use"}}

      17:42:11,128 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([

          ("subsystem" => "ejb3"),

          ("service" => "remote")

      ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"]}

      17:42:11,175 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 29) JBAS018559: Deployed "MyTest-vdb.xml" (runtime-name : "MyTest-vdb.xml")

      17:42:11,177 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report

      JBAS014775:    New missing/unsatisfied dependencies:

            service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service jboss.ejb3.connector]

      JBAS014777:   Services which failed to start:      service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: JBAS015811: Failed to start the http-interface service

            service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener

       

       

      17:42:11,317 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015964: Http management interface is not enabled

      17:42:11,317 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled

      17:42:11,317 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.0.0.Final "WildFly" started (with errors) in 2581ms - Started 208 of 267 services (5 services failed or missing dependencies, 82 services are lazy, passive or on-demand)

       

       

      and follow is my configuration for that :

       

                  <wsdl-host>${jboss.bind.address:192.168.7.88}</wsdl-host>

                  <endpoint-config name="Standard-Endpoint-Config"/>

                  <endpoint-config name="Recording-Endpoint-Config">

                      <pre-handler-chain name="recording-handlers" protocol-bindings="##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM">

                          <handler name="RecordingHandler" class="org.jboss.ws.common.invocation.RecordingServerHandler"/>

                      </pre-handler-chain>

                  </endpoint-config>

                  <client-config name="Standard-Client-Config"/>

              </subsystem>

              <subsystem xmlns="urn:jboss:domain:weld:2.0"/>

          </profile>

          <interfaces>

              <interface name="management">

                 <inet-address value="${jboss.bind.address.management:192.168.7.88}"/>

              </interface>

              <interface name="public">

                  <inet-address value="${jboss.bind.address:192.168.7.88}"/>

              </interface>

              <interface name="unsecure">

                  <inet-address value="${jboss.bind.address.unsecure:192.168.7.88}"/>

              </interface>

          </interfaces>

       

      i don't know if there is something wrong? thanks a lot.

        • 1. Re: wildfly 8 with eclipse
          rareddy

          There no Wildfly compatible Teiid yet. For the 8.x series we are going to use JBoss EAP 7.x series, for Teiid 9.x we are planning on Wildfly. It may be towards the end of 2014 we will have a compatible version.

           

          Ramesh..

          • 2. Re: wildfly 8 with eclipse
            rareddy

            For workaround, you can choose JBoss AS 7.1, or 7.2, however start the server externally (outside of the Designer) and then when you click on start inside the Designer, select manage the server externally to work with previously started server.

             

            Ramesh..