Java Wildfly 9.0.0和Netbeans 8.0.2

Java Wildfly 9.0.0和Netbeans 8.0.2,java,netbeans,wildfly,Java,Netbeans,Wildfly,我已经从JBossAS 7.1.1迁移到WildFly 9.0.0。当我尝试调试应用程序时,它启动失败,并显示以下消息: C:…\build impl.xml:1181:尚未部署该模块。有关详细信息,请参阅服务器日志 build impl.xml:1181: <nbstartserver debugmode="true"/> <antcall target="connect-debugger"/> <nbdeploy clientUrlPar

我已经从JBossAS 7.1.1迁移到WildFly 9.0.0。当我尝试调试应用程序时,它启动失败,并显示以下消息:

C:…\build impl.xml:1181:尚未部署该模块。有关详细信息,请参阅服务器日志

build impl.xml:1181:

    <nbstartserver debugmode="true"/>
    <antcall target="connect-debugger"/>
    <nbdeploy clientUrlPart="${client.urlPart}" debugmode="true" forceRedeploy="true"/>
    <antcall target="debug-display-browser-old"/>
    <antcall target="debug-display-browser"/>
    <antcall target="connect-client-debugger"/>

我能做什么?提前感谢。

问题出在Nvidia服务:它运行在阻止http:localhost:8080\console的hihden进程中

尝试杀死所有nvidia进程

  • Nvidia实际上拥有wildfly所需的端口。使用wildfly配置文件中的offset参数移动所有wildfly端口。我使用偏移量=100
  • Netbeans 8.0.2的wildfly插件不起作用。当您第一次尝试启动应用程序时,它会启动wildfly,但之后不会停止。当您第二次尝试启动应用程序时,Wildfly已经运行(因为NetBeans/plugin没有正确关闭它),并且Wildfly端口显然正在使用中。这就是wildfly所抱怨的。解决方法是使用wildfly cli手动启动/停止服务器
    我也有类似的问题,在启动wildfly时,在我的系统中,已经有一个应用程序在端口8080上运行,卸载了该应用程序,然后启动了wildfly 10,没有绑定异常。

    看起来您已经在端口8080上监听了一些内容。我已经查找了netstat,但没有使用此端口。我还将端口更改为8081和8088-没有任何更改错误消息后,您肯定在http端口和http管理端口上侦听了一些内容。也许你不知何故要发射两次。
    Listening for transport dt_socket at address: 8787
    03:39:35,677 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final
    03:39:35,995 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.4.Final
    03:39:36,104 INFO  [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 9.0.0.CR1 (WildFly Core 1.0.0.CR1) starting
    03:39:38,077 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 14) WFLYCTL0028: Attribute enabled is deprecated, and it might be removed in future version!
    03:39:38,080 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 14) WFLYCTL0028: Attribute enabled is deprecated, and it might be removed in future version!
    03:39:38,192 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
    03:39:38,223 INFO  [org.xnio] (MSC service thread 1-4) XNIO version 3.3.1.Final
    03:39:38,254 INFO  [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.3.1.Final
    03:39:38,368 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 54) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
    03:39:38,371 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem
    03:39:38,398 INFO  [org.jboss.as.security] (MSC service thread 1-7) WFLYSEC0001: Current PicketBox version=4.9.0.Beta2
    03:39:38,409 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension
    03:39:38,449 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.
    03:39:38,451 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem
    03:39:38,503 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
    03:39:38,551 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0003: Undertow 1.2.4.Final starting
    03:39:38,555 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.2.4.Final starting
    03:39:38,561 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]
    03:39:38,598 INFO  [org.jboss.as.naming] (MSC service thread 1-3) WFLYNAM0003: Starting Naming Service
    03:39:38,628 INFO  [org.jboss.as.connector] (MSC service thread 1-3) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final)
    03:39:38,645 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-5) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
    03:39:38,666 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
    03:39:38,868 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = mysql
    03:39:38,905 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
    03:39:38,909 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = h2
    03:39:39,111 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path C:\WildFly/welcome-content
    03:39:39,174 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0012: Started server default-server.
    03:39:39,215 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0018: Host default-host starting
    03:39:39,241 INFO  [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 4.0.9.Final
    03:39:39,379 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) 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:150)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
    Caused by: java.net.BindException: Address already in use: bind
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:437)
        at sun.nio.ch.Net.bind(Net.java:429)
        at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67)
        at org.xnio.nio.NioXnioWorker.createTcpConnectionServer(NioXnioWorker.java:182)
        at org.xnio.XnioWorker.createStreamConnectionServer(XnioWorker.java:243)
        at org.wildfly.extension.undertow.HttpListenerService.startListening(HttpListenerService.java:115)
        at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:147)
        ... 5 more
    
    03:39:39,892 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) WFLYDS0013: Started FileSystemDeploymentService for directory C:\WildFly\standalone\deployments
    03:39:40,024 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service
        at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:269)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
    Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use: bind
        at org.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpServer.java:160)
        at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:235)
        ... 5 more
    Caused by: java.net.BindException: Address already in use: bind
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:437)
        at sun.nio.ch.Net.bind(Net.java:429)
        at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67)
        at org.xnio.nio.NioXnioWorker.createTcpConnectionServer(NioXnioWorker.java:182)
        at org.xnio.XnioWorker.createStreamConnectionServer(XnioWorker.java:243)
        at org.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpServer.java:147)
        ... 6 more
    
    03:39:40,092 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
    03:39:40,093 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) WFLYJCA0001: Bound data source [java:jboss/booking-war]
    03:39:40,102 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
        ("core-service" => "management"),
        ("management-interface" => "http-interface")
    ]) - failure description: {
        "WFLYCTL0080: Failed services" => {"jboss.serverManagement.controller.management.http" => "org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service
        Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use: bind
        Caused by: java.net.BindException: Address already in use: bind"},
        "WFLYCTL0288: 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.serverManagement.controller.management.http.shutdown"],
            "Services that may be the cause:" => ["jboss.remoting.remotingConnectorInfoService.http-remoting-connector"]
        }
    }
    03:39:40,106 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: {"WFLYCTL0288: 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"]
    }}
    03:39:40,107 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
        ("subsystem" => "undertow"),
        ("server" => "default-server"),
        ("http-listener" => "default")
    ]) - failure description: {"WFLYCTL0080: 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: bind"}}
    03:39:40,110 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "ejb3")]) - failure description: {"WFLYCTL0288: 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.ejb.default-local-ejb-receiver-service",
            "jboss.ejb3.ejbClientContext.default",
            "jboss.ejb3.localEjbReceiver.value"
        ],
        "Services that may be the cause:" => ["jboss.remoting.remotingConnectorInfoService.http-remoting-connector"]
    }}
    03:39:40,113 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
        ("subsystem" => "ejb3"),
        ("service" => "remote")
    ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"]}
    03:39:40,228 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
    WFLYCTL0184:    New missing/unsatisfied dependencies:
          service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service jboss.ejb3.connector] 
    WFLYCTL0186:   Services which failed to start:      service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener
          service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service
    
    03:39:40,515 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0063: Http management interface is not enabled
    03:39:40,515 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled
    03:39:40,515 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.0.CR1 (WildFly Core 1.0.0.CR1) started (with errors) in 5244ms - Started 191 of 381 services (8 services failed or missing dependencies, 210 services are lazy, passive or on-demand)