This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | java.util.concurrent.RejectedExecutionException: Task org.xnio.AbstractIoFuture$1@7ac8890d rejected from org.xnio.XnioWorker$TaskPool@740f6824[Terminated, pool size = 0, active threads = 0, queued tas | ||
---|---|---|---|
Product: | serverplugins | Reporter: | Exceptions Reporter <exceptions_reporter> |
Component: | WildFly | Assignee: | ehsavoie <ehsavoie> |
Status: | REOPENED --- | ||
Severity: | normal | CC: | arthurgregorio, cmac, fleka, flynnk, GenoDaGawd, jherkel, jomu, MackSix, makweru, miibx5, misterm, muellermi, samyomar82, terje7601, vachr |
Priority: | P3 | ||
Version: | 8.0 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 212732 |
Attachments: |
stacktrace
stacktrace stacktrace stacktrace stacktrace stacktrace stacktrace stacktrace stacktrace Logfile for Comment #13 stacktrace |
Description
Exceptions Reporter
2014-12-03 02:46:27 UTC
Created attachment 150852 [details]
stacktrace
I don't think the stable version of the plugin is working for WildFly 9, you have to use a nightly build version of Netbeans. The scheme version has changed in WildFly 9 so I think it is trying to connect as for AS 7. Created attachment 151661 [details]
stacktrace
Added WildFly Server 8.2.0 and then right clicked on the node in Services window and tried to start it. This Exception occured while it was starting up
Created attachment 151662 [details]
stacktrace
Restarted NetBeans after exception trying to start newely installed Wildfly Server 8.2.0 Final.
Created attachment 152872 [details]
stacktrace
.
Created attachment 152944 [details]
stacktrace
I want do debug my maven project via class with main function.
Created attachment 153105 [details]
stacktrace
.
Created attachment 153222 [details]
stacktrace
build with dependencies
Created attachment 153844 [details]
stacktrace
start web app
Created attachment 153846 [details]
stacktrace
starting web app
*** Bug 252939 has been marked as a duplicate of this bug. *** Can someone attach the server logs ? (In reply to ehsavoie from comment #12) > Can someone attach the server logs ? If I add WildFly 9.0 to NetBeans 8.0.2, there is no server log generated because the server is not running. The server never starts. This exception is thrown immediately when adding the server to the Services->Servers node. See attached NetBeans Logfile. Product Version: NetBeans IDE 8.0.2 (Build 201411181905) Updates: NetBeans IDE is updated to version NetBeans 8.0.2 Patch 2 Java: 1.8.0_45; Java HotSpot(TM) 64-Bit Server VM 25.45-b02 Runtime: Java(TM) SE Runtime Environment 1.8.0_45-b15 System: Windows 7 version 6.1 running on amd64; UTF8; en_US (nb) Created attachment 154627 [details] Logfile for Comment #13 Calling "F:\wildfly-9.0.0.Final\bin\standalone.conf.bat" "JAVA_OPTS already set in environment; overriding default settings with values: -Xms128m -Xmx512m -server -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true" Setting JAVA property to "C:\Program Files\Java\jdk1.8.0_45\bin\java" =============================================================================== JBoss Bootstrap Environment JBOSS_HOME: "F:\wildfly-9.0.0.Final" JAVA: "C:\Program Files\Java\jdk1.8.0_45\bin\java" JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms128m -Xmx512m -server -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true" =============================================================================== 21:55:12,103 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final 21:55:12,454 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final 21:55:12,560 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Full 9.0.0.Final (WildFly Core 1.0.0.Final) starting 21:55:15,205 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 15) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. 21:55:15,248 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 23) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. 21:55:15,322 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) 21:55:15,398 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.1.Final 21:55:15,417 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.1.Final 21:55:15,498 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem. 21:55:15,570 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem 21:55:15,660 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors 21:55:15,783 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. 21:55:15,784 INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem 21:55:15,940 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main] 21:55:16,361 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem 21:55:16,404 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.9.Final 21:55:16,504 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) 21:55:16,692 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension 21:55:16,919 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.2.Final 21:55:16,933 INFO [org.jboss.as.connector] (MSC service thread 1-8) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final) 21:55:17,011 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0003: Undertow 1.2.8.Final starting 21:55:17,015 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.2.8.Final starting 21:55:17,290 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2 21:55:17,311 INFO [org.jboss.as.naming] (MSC service thread 1-5) WFLYNAM0003: Starting Naming Service 21:55:17,311 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] 21:55:17,484 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path F:\wildfly-9.0.0.Final/welcome-content 21:55:17,596 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0012: Started server default-server. 21:55:17,671 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0018: Host default-host starting 21:55:17,795 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) 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 21:55:18,100 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] 21:55:18,166 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started 21:55:18,214 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) WFLYDS0013: Started FileSystemDeploymentService for directory F:\wildfly-9.0.0.Final\standalone\deployments 21:55:18,274 SEVERE [javax.enterprise.resource.corba._DEFAULT_.rpc.transport] (MSC service thread 1-1) "IOP00410216: (COMM_FAILURE) Unable to create listener thread on the specified port: 3528": org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 216 completed: No at com.sun.corba.se.impl.logging.ORBUtilSystemException.createListenerFailed(ORBUtilSystemException.java:2632) at com.sun.corba.se.impl.logging.ORBUtilSystemException.createListenerFailed(ORBUtilSystemException.java:2651) at com.sun.corba.se.impl.transport.SocketOrChannelAcceptorImpl.initialize(SocketOrChannelAcceptorImpl.java:164) at com.sun.corba.se.impl.transport.CorbaTransportManagerImpl.getAcceptors(CorbaTransportManagerImpl.java:217) at com.sun.corba.se.impl.transport.CorbaTransportManagerImpl.addToIORTemplate(CorbaTransportManagerImpl.java:235) at com.sun.corba.se.spi.oa.ObjectAdapterBase.initializeTemplate(ObjectAdapterBase.java:122) at com.sun.corba.se.impl.oa.poa.POAImpl.initialize(POAImpl.java:404) at com.sun.corba.se.impl.oa.poa.POAImpl.makeRootPOA(POAImpl.java:272) at com.sun.corba.se.impl.oa.poa.POAFactory$1.evaluate(POAFactory.java:205) at com.sun.corba.se.impl.orbutil.closure.Future.evaluate(Future.java:46) at com.sun.corba.se.impl.resolver.LocalResolverImpl.resolve(LocalResolverImpl.java:40) at com.sun.corba.se.impl.resolver.CompositeResolverImpl.resolve(CompositeResolverImpl.java:45) at com.sun.corba.se.impl.orb.ORBImpl.resolve_initial_references(ORBImpl.java:1171) at org.wildfly.iiop.openjdk.service.CorbaPOAService.start(CorbaPOAService.java:156) 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 com.sun.corba.se.impl.transport.DefaultSocketFactoryImpl.createServerSocket(DefaultSocketFactoryImpl.java:83) at com.sun.corba.se.impl.transport.SocketOrChannelAcceptorImpl.initialize(SocketOrChannelAcceptorImpl.java:161) ... 16 more 21:55:18,278 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.iiop-openjdk.poa-service.rootpoa: org.jboss.msc.service.StartException in service jboss.iiop-openjdk.poa-service.rootpoa: WFLYIIOP0098: Failed to resolve initial reference RootPOA at org.wildfly.iiop.openjdk.service.CorbaPOAService.start(CorbaPOAService.java:158) 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: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 216 completed: No at com.sun.corba.se.impl.logging.ORBUtilSystemException.createListenerFailed(ORBUtilSystemException.java:2632) at com.sun.corba.se.impl.logging.ORBUtilSystemException.createListenerFailed(ORBUtilSystemException.java:2651) at com.sun.corba.se.impl.transport.SocketOrChannelAcceptorImpl.initialize(SocketOrChannelAcceptorImpl.java:164) at com.sun.corba.se.impl.transport.CorbaTransportManagerImpl.getAcceptors(CorbaTransportManagerImpl.java:217) at com.sun.corba.se.impl.transport.CorbaTransportManagerImpl.addToIORTemplate(CorbaTransportManagerImpl.java:235) at com.sun.corba.se.spi.oa.ObjectAdapterBase.initializeTemplate(ObjectAdapterBase.java:122) at com.sun.corba.se.impl.oa.poa.POAImpl.initialize(POAImpl.java:404) at com.sun.corba.se.impl.oa.poa.POAImpl.makeRootPOA(POAImpl.java:272) at com.sun.corba.se.impl.oa.poa.POAFactory$1.evaluate(POAFactory.java:205) at com.sun.corba.se.impl.orbutil.closure.Future.evaluate(Future.java:46) at com.sun.corba.se.impl.resolver.LocalResolverImpl.resolve(LocalResolverImpl.java:40) at com.sun.corba.se.impl.resolver.CompositeResolverImpl.resolve(CompositeResolverImpl.java:45) at com.sun.corba.se.impl.orb.ORBImpl.resolve_initial_references(ORBImpl.java:1171) at org.wildfly.iiop.openjdk.service.CorbaPOAService.start(CorbaPOAService.java:156) ... 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 com.sun.corba.se.impl.transport.DefaultSocketFactoryImpl.createServerSocket(DefaultSocketFactoryImpl.java:83) at com.sun.corba.se.impl.transport.SocketOrChannelAcceptorImpl.initialize(SocketOrChannelAcceptorImpl.java:161) ... 16 more 21:55:18,358 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 21:55:18,366 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.http-upgrade-registry.default", "jboss.remoting.remotingConnectorInfoService.http-remoting-connector" ] } } 21:55:18,369 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.http-upgrade-registry.default", "jboss.remoting.remotingConnectorInfoService.http-remoting-connector" ] }} 21:55:18,370 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "iiop-openjdk")]) - failure description: { "WFLYCTL0080: Failed services" => {"jboss.iiop-openjdk.poa-service.rootpoa" => "org.jboss.msc.service.StartException in service jboss.iiop-openjdk.poa-service.rootpoa: WFLYIIOP0098: Failed to resolve initial reference RootPOA Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 216 completed: No 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.iiop-openjdk.naming-service", "jboss.iiop-openjdk.poa-service.irpoa", "jboss.iiop-openjdk.poa-service.namingpoa" ], "Services that may be the cause:" => [ "jboss.http-upgrade-registry.default", "jboss.remoting.remotingConnectorInfoService.http-remoting-connector" ] } } 21:55:18,395 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"}} 21:55:18,399 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "messaging"), ("hornetq-server" => "default") ]) - failure description: { "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.messaging.default is missing [jboss.http-upgrade-registry.default]"], "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.messaging.default.jms.manager"], "Services that may be the cause:" => [ "jboss.http-upgrade-registry.default", "jboss.remoting.remotingConnectorInfoService.http-remoting-connector" ] } } 21:55:18,401 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "jsr77")]) - 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.jsr77.ejb"], "Services that may be the cause:" => [ "jboss.http-upgrade-registry.default", "jboss.remoting.remotingConnectorInfoService.http-remoting-connector" ] }} 21:55:18,407 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.http-upgrade-registry.default", "jboss.remoting.remotingConnectorInfoService.http-remoting-connector" ] }} 21:55:18,408 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]"]} 21:55:18,497 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report WFLYCTL0184: New missing/unsatisfied dependencies: service jboss.http-upgrade-registry.default (missing) dependents: [service jboss.messaging.default] service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service jboss.ejb3.connector] WFLYCTL0186: Services which 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 service jboss.iiop-openjdk.poa-service.rootpoa: org.jboss.msc.service.StartException in service jboss.iiop-openjdk.poa-service.rootpoa: WFLYIIOP0098: Failed to resolve initial reference RootPOA service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener 21:55:18,748 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0063: Http management interface is not enabled 21:55:18,748 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled 21:55:18,749 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.0.Final (WildFly Core 1.0.0.Final) started (with errors) in 7060ms - Started 197 of 401 services (15 services failed or missing dependencies, 221 services are lazy, passive or on-demand) I changed the ports: http 8585, management 8888 Now, if i start wildfly from its bin directory, it start without errors. Although I removed Wildfly from NB and re-added with the new ports, NB tries to use a wrong port (8090) and WildFly never starts: ------------------------------------------------------------------------ BUILD SUCCESS ------------------------------------------------------------------------ Total time: 4.222s Finished at: Tue Jul 14 22:15:16 CEST 2015 Final Memory: 16M/224M ------------------------------------------------------------------------ NetBeans: Deploying on wildfly-deployer:localhost:8090#standalone&F:\wildfly-9.0.0.Final profile mode: false debug mode: false force redeploy: true BTW: NB queries the ports, although they could have been read from the config. After the initial setting of the ports, there is no dialog to change it. If read from config: Omit that query. If not read from config: Provide a screen to change. WildFly 9 is not supported in 8.0.2, you'll have to wait for 8.1 or use the nightly builds. (In reply to muellermi from comment #17) > BTW: NB queries the ports, although they could have been read from the > config. After the initial setting of the ports, there is no dialog to change > it. > If read from config: Omit that query. > If not read from config: Provide a screen to change. Also, NetBeans does not change the port values in the config if you change them in NetBeans when you add the server. This is not how the other server plugins work. NetBeans changes the values of the server config files. Re-opend, cause the problem occurs with the nightly build (In reply to muellermi from comment #20) > Re-opend, cause the problem occurs with the nightly build How do you know if your nightly build actually contains the fix? I think you should wait for a message from Quality Engineering (like e.g. https://netbeans.org/bugzilla/show_bug.cgi?id=236152#c41 ) before testing again. Still no server log. @MackSix: the 'problem' is that you may have different management interfaces with different protocols in WildFly so which one should I change ? Changing/parsing the XML config means supposing that the default one is used and that no runtime parameters are set. Also what would happen if you 'attach' yourself to a running server ? (In reply to ehsavoie from comment #22) > Still no server log. > @MackSix: the 'problem' is that you may have different management interfaces > with different protocols in WildFly so which one should I change ? > Changing/parsing the XML config means supposing that the default one is used > and that no runtime parameters are set. Also what would happen if you > 'attach' yourself to a running server ? I am not the judge of that. At the least should we be able to click on a Wildfly server, view properties and change the NetBeans server and management port numbers without having to remove the server and add it again? That would be helpful. I don't know how to do that without removing the node and adding it again. Chaning the port in the XML config is easy enough. Am I missing something? (In reply to muellermi from comment #20) > Re-opend, cause the problem occurs with the nightly build I cannot, for the life of me, get this exception to happen in the latest nightly build with Wildfly 9.0 or 8.0.2. So I am not help with this. :) Product Version: NetBeans IDE Dev (Build 201507140001) Java: 1.8.0_45; Java HotSpot(TM) 64-Bit Server VM 25.45-b02 Runtime: Java(TM) SE Runtime Environment 1.8.0_45-b15 System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb) *** Bug 253525 has been marked as a duplicate of this bug. *** Created attachment 157488 [details]
stacktrace
.
|