I am using wildfly-9.0.0.CR2 server for my Spring MVC application, on a sudden wildfly server stooping for every 10 mins!. I don't think my application is requesting server for shutdown and I didn't use any third party APIs.
When I observe the server log I couldn't figure out the issue.
2018-12-05 12:36:57,438 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.
2018-12-05 12:36:57,466 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0019: Stopped Driver service with driver-name = DCTWebApp.war_com.mysql.jdbc.Driver_5_1
2018-12-05 12:36:57,477 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) WFLYJCA0010: Unbound data source [java:/thalesdbDocTool]
2018-12-05 12:36:57,477 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:/thalesdbtool]
2018-12-05 12:36:57,498 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 75) WFLYUT0022: Unregistered web context: /
2018-12-05 12:36:57,528 INFO [io.undertow.servlet] (ServerService Thread Pool -- 75) Destroying Spring FrameworkServlet 'mvc-dispatcher'
2018-12-05 12:36:57,538 INFO [org.springframework.web.context.support.XmlWebApplicationContext] (ServerService Thread Pool -- 75) Closing WebApplicationContext for namespace 'mvc-dispatcher-servlet': startup date [Wed Dec 05 12:29:45 IST 2018]; parent: Root WebApplicationContext
2018-12-05 12:36:57,575 INFO [io.undertow.servlet] (ServerService Thread Pool -- 75) Closing Spring root WebApplicationContext
2018-12-05 12:36:57,582 INFO [org.springframework.web.context.support.XmlWebApplicationContext] (ServerService Thread Pool -- 75) Closing Root WebApplicationContext: startup date [Wed Dec 05 12:29:35 IST 2018]; root of context hierarchy
2018-12-05 12:36:57,598 ERROR [org.springframework.beans.factory.support.DefaultListableBeanFactory] (ServerService Thread Pool -- 75) Destroy method on bean with name '(inner bean)#305d8fe1' threw an exception: java.lang.NullPointerException
at org.springframework.security.oauth2.provider.BaseClientDetails.hashCode(BaseClientDetails.java:279)
at java.util.concurrent.ConcurrentHashMap.replaceNode(ConcurrentHashMap.java:1106)
at java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:1097)
at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor.postProcessBeforeDestruction(PersistenceAnnotationBeanPostProcessor.java:374)
at org.springframework.beans.factory.support.DisposableBeanAdapter.destroy(DisposableBeanAdapter.java:239)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroyBean(DefaultSingletonBeanRegistry.java:578)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingleton(DefaultSingletonBeanRegistry.java:554)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.destroySingleton(DefaultListableBeanFactory.java:900)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroyBean(DefaultSingletonBeanRegistry.java:589)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingleton(DefaultSingletonBeanRegistry.java:554)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.destroySingleton(DefaultListableBeanFactory.java:900)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingletons(DefaultSingletonBeanRegistry.java:523)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.destroySingletons(DefaultListableBeanFactory.java:907)
at org.springframework.context.support.AbstractApplicationContext.destroyBeans(AbstractApplicationContext.java:908)
at org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:884)
at org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:836)
at org.springframework.web.context.ContextLoader.closeWebApplicationContext(ContextLoader.java:579)
at org.springframework.web.context.ContextLoaderListener.contextDestroyed(ContextLoaderListener.java:115)
at io.undertow.servlet.core.ApplicationListeners.contextDestroyed(ApplicationListeners.java:185)
at io.undertow.servlet.core.DeploymentImpl.destroy(DeploymentImpl.java:224)
at io.undertow.servlet.core.DeploymentManagerImpl.undeploy(DeploymentManagerImpl.java:578)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:145)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$2.run(UndertowDeploymentService.java:121)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
2018-12-05 12:36:57,604 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0019: Stopped Driver service with driver-name = mysql
2018-12-05 12:36:57,803 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0019: Host default-host stopping
2018-12-05 12:36:57,822 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
2018-12-05 12:36:57,838 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0019: Stopped Driver service with driver-name = h2
2018-12-05 12:36:57,855 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0008: Undertow HTTP listener default suspending
2018-12-05 12:36:57,860 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0008: Undertow HTTPS listener default-ssl suspending
2018-12-05 12:36:57,863 INFO [oinfluncerg.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0007: Undertow HTTP listener default stopped, was bound to localhost/127.0.0.1:4714
2018-12-05 12:36:57,870 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0007: Undertow HTTPS listener default-ssl stopped, was bound to localhost/127.0.0.1:8080
2018-12-05 12:36:57,886 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Undertow 1.2.8.Final stopping
2018-12-05 12:36:57,925 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment DCTWebApp.war (runtime-name: DCTWebApp.war) in 472ms
2018-12-05 12:36:57,941 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Full 9.0.0.Final (WildFly Core 1.0.0.Final) stopped in 473ms
Please help me to understand what could influence the server shutdown.
Related
I'm using JBOSS EAP version 7.3 and Eclipse Version: 2021-12 M1 (4.22.0 M1) with JDK 1.8.0. I'm able to deploy my services as a war and application fine until when I navigate to some steps in application, JBOSS shutdown with below error message.
This is happening on window machine
19:41:04,206 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0272: Suspending server
19:41:04,210 INFO [org.jboss.as.ejb3] (Thread-2) WFLYEJB0493: EJB subsystem suspension complete
19:41:04,215 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested via an OS signal
19:41:04,247 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0019: Stopped Driver service with driver-name = ABCDService.war_oracle.jdbc.OracleDriver_11_2
19:41:04,280 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0019: Stopped Driver service with driver-name = ABCDService.war_com.mysql.fabric.jdbc.FabricMySQLDriver_5_1
19:41:04,281 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = XYZService.war_com.mysql.fabric.jdbc.FabricMySQLDriver_5_1
19:41:04,283 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = XYZService.war
19:41:04,284 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0019: Stopped Driver service with driver-name = ABCDService.war_com.mysql.jdbc.Driver_5_1
19:41:04,284 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0019: Stopped Driver service with driver-name = ABCDService.war
19:41:04,293 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0010: Unbound data source [java:jboss/datasources/abcd]
19:41:04,316 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0019: Stopped Driver service with driver-name = XYZService.war_com.mysql.jdbc.Driver_5_1
19:41:04,323 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
19:41:04,333 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 10) WFLYUT0022: Unregistered web context: '/XYZService' from server 'default-server'
19:41:04,351 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 113) WFLYUT0022: Unregistered web context: '/ABCDService' from server 'default-server'
19:41:04,371 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0019: Stopped Driver service with driver-name = MySqlJDBCDriver
19:41:04,372 INFO [io.undertow.servlet] (ServerService Thread Pool -- 113) Destroying Spring FrameworkServlet 'ABCDService'
19:41:04,387 INFO [io.undertow.servlet] (ServerService Thread Pool -- 111) Destroying Spring FrameworkServlet 'dispatcherServlet'
19:41:04,392 INFO [io.undertow.servlet] (ServerService Thread Pool -- 111) Closing Spring root WebApplicationContext
19:41:04,394 INFO [io.undertow.servlet] (ServerService Thread Pool -- 10) Closing Spring root WebApplicationContext
19:41:04,394 INFO [io.undertow.servlet] (ServerService Thread Pool -- 111) Closing Spring root WebApplicationContext
19:41:04,438 INFO [io.undertow.servlet] (ServerService Thread Pool -- 113) Closing Spring root WebApplicationContext
19:41:04,453 INFO [io.undertow.servlet] (ServerService Thread Pool -- 115) Closing Spring root WebApplicationContext
19:41:04,808 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 122) WFLYCLINF0003: Stopped client-mappings cache from ejb container
19:41:04,842 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0019: Host default-host stopping
19:41:04,868 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
19:41:04,894 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0019: Stopped Driver service with driver-name = h2
19:41:04,914 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0008: Undertow HTTP listener default suspending
19:41:04,915 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0008: Undertow HTTPS listener https suspending
19:41:04,916 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0007: Undertow HTTPS listener https stopped, was bound to 127.0.0.1:8443
19:41:04,918 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080
19:41:04,923 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0004: Undertow 2.0.28.SP1-redhat-00001 stopping
19:41:05,824 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment XYZServices (runtime-name: XYZService.war) in 1602ms
19:41:05,964 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment ABCDService (runtime-name: ABCDService.war) in 1737ms
19:41:05,977 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: JBoss EAP 7.3.0.GA (WildFly Core 10.1.2.Final-redhat-00001) stopped in 1722ms
I tried looking at other threads on mysteries shutdown but no luck https://developer.jboss.org/docs/DOC-11456 .
i am not so familiar with ejb. I had hard time to set up realm authorization at wildfly, (13) all the time i had same error:
20:33:55,037 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "RaportGeneratorEE-0.0.1-SNAPSHOT.war")]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.security.security-domain.exampleApplicationDomain"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"RaportGeneratorEE-0.0.1-SNAPSHOT.war\".component.ProgrammaticScheduler.CREATE is missing [jboss.security.security-domain.exampleApplicationDomain]"]
}
After this i have removed #Singleton Annotation from "ProgrammaticScheduler" and with out it my realm authentication works well. But than my scheduler doesnt work at all. When i remove lane with
exampleApplicationDomain
Scheduler works, realm doesnt. Where is the point? This two componenst dont have any common classes.. (well.. i dont know about any). Any one have some ideas? I have seen many familiar problems here but almost all of them were about missing or wrong line in standalone.xml.
Ps. I had another class with #stateless annotation and this class was in error too, but i didnt need it and jsut removed it. Full error log, standalone, jboss-web.xml below. Hope some will find solution
standalone.xml
<security-domains>
<security-domain name="ApplicationDomain" default-realm="ApplicationRealm" permission-mapper="default-permission-mapper">
<realm name="ApplicationRealm" role-decoder="groups-to-roles"/>
<realm name="local"/>
</security-domain>
<security-domain name="ManagementDomain" default-realm="ManagementRealm" permission-mapper="default-permission-mapper">
<realm name="ManagementRealm" role-decoder="groups-to-roles"/>
<realm name="local" role-mapper="super-user-mapper"/>
</security-domain>
<security-domain name="jdbcdomain" default-realm="jdbcRealm">
<realm name="jdbcRealm"/>
</security-domain>
<security-domain name="exampleDbSD" default-realm="exampleDbRealm" permission-mapper="default-permission-mapper">
<realm name="exampleDbRealm" role-decoder="groups-to-roles"/>
</security-domain>
</security-domains>
ProgrammaticScheduler
#Singleton
public class ProgrammaticScheduler {
#Schedule(hour="20", minute="33")
public void removeExpiredSearches() throws IOException{
System.out.println("Kick off!");
}
#Timeout()
public void onTimeout(Timer timer){
}
}
Error log
20:33:34,908 INFO [org.jboss.modules] (main) JBoss Modules version 1.8.5.Final
20:33:36,349 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.2.Final
20:33:36,373 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.2.Final
20:33:36,662 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 13.0.0.Final (WildFly Core 5.0.0.Final) starting
20:33:40,940 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
20:33:41,000 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 17) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
20:33:41,004 INFO [org.wildfly.security] (ServerService Thread Pool -- 7) ELY00001: WildFly Elytron version 1.3.3.Final
20:33:41,220 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found RaportGeneratorEE-0.0.1-SNAPSHOT.war in deployment directory. To trigger deployment create a file called RaportGeneratorEE-0.0.1-SNAPSHOT.war.dodeploy
20:33:41,324 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
20:33:41,409 INFO [org.xnio] (MSC service thread 1-8) XNIO version 3.6.3.Final
20:33:41,421 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.6.3.Final
20:33:41,674 INFO [org.jboss.as.security] (ServerService Thread Pool -- 60) WFLYSEC0002: Activating Security Subsystem
20:33:41,683 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 64) WFLYWS0002: Activating WebServices Extension
20:33:41,666 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 62) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
20:33:41,677 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 47) WFLYRS0016: RESTEasy version 3.5.1.Final
20:33:41,682 INFO [org.jboss.as.security] (MSC service thread 1-5) WFLYSEC0001: Current PicketBox version=5.0.2.Final
20:33:41,705 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 52) WFLYJSF0007: Activated the following JSF Implementations: [main]
20:33:41,718 INFO [org.jboss.as.ee] (ServerService Thread Pool -- 41) WFLYEE0119: The system property 'ee8.preview.mode' is NOT set to 'true'. For provided EE 8 APIs where the EE 8 version of the API differs from what is supported in EE 7, the EE 7 variant of the API will be used. Support for this setting will be removed once all EE 8 APIs are provided and certified.
20:33:41,737 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 45) WFLYCLINF0001: Activating Infinispan subsystem.
20:33:41,743 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 54) WFLYNAM0001: Activating Naming Subsystem
20:33:41,818 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0003: Undertow 2.0.9.Final starting
20:33:41,863 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 38) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
20:33:41,885 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.9.Final)
20:33:41,932 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = h2
20:33:42,046 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service
20:33:42,056 INFO [org.jboss.as.mail.extension] (MSC service thread 1-6) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
20:33:42,419 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 63) WFLYUT0014: Creating file handler for path 'C:\Users\Wiki\Downloads\wildfly-13.0.0.Final\wildfly-13.0.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
20:33:42,886 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 46) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
20:33:42,904 INFO [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
20:33:42,913 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
20:33:43,056 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 5.0.7.Final
20:33:43,060 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0012: Started server default-server.
20:33:43,101 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0018: Host default-host starting
20:33:43,112 INFO [org.jboss.as.patching] (MSC service thread 1-5) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
20:33:43,226 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore C:\Users\Wiki\Downloads\wildfly-13.0.0.Final\wildfly-13.0.0.Final\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
20:33:43,236 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-8) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Users\Wiki\Downloads\wildfly-13.0.0.Final\wildfly-13.0.0.Final\standalone\deployments
20:33:43,265 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "mysql" (runtime-name: "mysql-connector-java-5.1.44-bin.jar")
20:33:43,271 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "RaportGeneratorEE-0.0.1-SNAPSHOT.war" (runtime-name: "RaportGeneratorEE-0.0.1-SNAPSHOT.war")
20:33:43,301 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
20:33:43,345 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0493: EJB subsystem suspension complete
20:33:44,142 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
20:33:44,619 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
20:33:44,801 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBossWS 5.2.1.Final (Apache CXF 3.2.4.jbossorg-1)
20:33:45,530 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
20:33:45,536 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.fabric.jdbc.FabricMySQLDriver (version 5.1)
20:33:45,705 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = mysql-connector-java-5.1.44-bin.jar_com.mysql.fabric.jdbc.FabricMySQLDriver_5_1
20:33:45,706 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = mysql-connector-java-5.1.44-bin.jar_com.mysql.jdbc.Driver_5_1
20:33:45,736 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:/MysqlXADS]
20:33:45,745 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0001: Bound data source [java:/examplePostgresDS]
20:33:47,033 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Gaina' 9.2.4.Final
20:33:48,039 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66) WFLYCLINF0002: Started client-mappings cache from ejb container
20:33:52,002 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry xml-apis.jar in /C:/Users/Wiki/Downloads/wildfly-13.0.0.Final/wildfly-13.0.0.Final/standalone/deployments/RaportGeneratorEE-0.0.1-SNAPSHOT.war/WEB-INF/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
20:33:52,007 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry xercesImpl.jar in /C:/Users/Wiki/Downloads/wildfly-13.0.0.Final/wildfly-13.0.0.Final/standalone/deployments/RaportGeneratorEE-0.0.1-SNAPSHOT.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
20:33:52,007 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry xml-apis.jar in /C:/Users/Wiki/Downloads/wildfly-13.0.0.Final/wildfly-13.0.0.Final/standalone/deployments/RaportGeneratorEE-0.0.1-SNAPSHOT.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
20:33:52,007 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry serializer.jar in /C:/Users/Wiki/Downloads/wildfly-13.0.0.Final/wildfly-13.0.0.Final/standalone/deployments/RaportGeneratorEE-0.0.1-SNAPSHOT.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
20:33:53,000 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment RaportGeneratorEE-0.0.1-SNAPSHOT.war
20:33:53,923 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.3.6.Final
20:33:54,036 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'ProgrammaticScheduler' in deployment unit 'deployment "RaportGeneratorEE-0.0.1-SNAPSHOT.war"' are as follows:
java:global/RaportGeneratorEE-0.0.1-SNAPSHOT/ProgrammaticScheduler!czesak.raportgenerator.service.ProgrammaticScheduler
java:app/RaportGeneratorEE-0.0.1-SNAPSHOT/ProgrammaticScheduler!czesak.raportgenerator.service.ProgrammaticScheduler
java:module/ProgrammaticScheduler!czesak.raportgenerator.service.ProgrammaticScheduler
ejb:RaportGeneratorEE-0.0.1-SNAPSHOT/ProgrammaticScheduler!czesak.raportgenerator.service.ProgrammaticScheduler
java:global/RaportGeneratorEE-0.0.1-SNAPSHOT/ProgrammaticScheduler
java:app/RaportGeneratorEE-0.0.1-SNAPSHOT/ProgrammaticScheduler
java:module/ProgrammaticScheduler
20:33:54,485 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
20:33:54,490 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.fabric.jdbc.FabricMySQLDriver (version 5.1)
20:33:54,500 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 8.0)
20:33:54,539 INFO [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900: 3.0.4 (Final)
20:33:54,721 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = RaportGeneratorEE-0.0.1-SNAPSHOT.war_com.mysql.fabric.jdbc.FabricMySQLDriver_5_1
20:33:54,722 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = RaportGeneratorEE-0.0.1-SNAPSHOT.war_com.mysql.jdbc.Driver_5_1
20:33:54,724 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = RaportGeneratorEE-0.0.1-SNAPSHOT.war_com.mysql.cj.jdbc.Driver_8_0
20:33:55,037 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "RaportGeneratorEE-0.0.1-SNAPSHOT.war")]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.security.security-domain.exampleApplicationDomain"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"RaportGeneratorEE-0.0.1-SNAPSHOT.war\".component.ProgrammaticScheduler.CREATE is missing [jboss.security.security-domain.exampleApplicationDomain]"]
}
20:33:55,057 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "mysql" (runtime-name : "mysql-connector-java-5.1.44-bin.jar")
20:33:55,058 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "RaportGeneratorEE-0.0.1-SNAPSHOT.war" (runtime-name : "RaportGeneratorEE-0.0.1-SNAPSHOT.war")
20:33:55,064 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.security.security-domain.exampleApplicationDomain (missing) dependents: [service jboss.deployment.unit."RaportGeneratorEE-0.0.1-SNAPSHOT.war".component.ProgrammaticScheduler.CREATE]
WFLYCTL0448: 225 additional services are down due to their dependencies being missing or failed
There is need to add aplication-security-domain (using security-domain) in ejb3 services:
subsystem=ejb3/application-security-domain=exampleApplicationDomain:add(security-domain=exampleDbSD)
I am referring to the following helloworld example
My application is successfully deployed on my eclipse using WildFly 9.x as shown in the screenshot and the console log below:
Here's the eclipse console log details :
14:08:16,447 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final
14:08:17,156 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
14:08:17,293 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0049: WildFly Full 9.0.2.Final (WildFly Core 1.0.2.Final) starting
14:08:19,873 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 19) 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.
14:08:19,890 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 11) 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.
14:08:19,908 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found JAX-RS_examples.war in deployment directory. To trigger deployment create a file called JAX-RS_examples.war.dodeploy
14:08:19,953 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
14:08:19,993 INFO [org.xnio] (MSC service thread 1-3) XNIO version 3.3.1.Final
14:08:20,007 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.3.1.Final
14:08:20,075 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 4.0.9.Final
14:08:20,106 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.2.9.Final starting
14:08:20,213 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.
14:08:20,183 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]
14:08:20,179 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem
14:08:20,110 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0003: Undertow 1.2.9.Final starting
14:08:20,164 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.
14:08:20,164 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension
14:08:20,136 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
14:08:20,106 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem
14:08:20,377 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
14:08:20,684 INFO [org.jboss.as.connector] (MSC service thread 1-3) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.5.Final)
14:08:20,975 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2
14:08:20,985 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service
14:08:21,016 INFO [org.jboss.as.security] (MSC service thread 1-3) WFLYSEC0001: Current PicketBox version=4.9.2.Final
14:08:21,158 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
14:08:21,194 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path D:\Users\dan\wildfly-9.0.2.Final/welcome-content
14:08:21,246 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: Started server default-server.
14:08:21,264 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
14:08:21,727 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTP listener default listening on localhost/127.0.0.1:8080
14:08:22,413 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) WFLYDS0013: Started FileSystemDeploymentService for directory D:\Users\dan\wildfly-9.0.2.Final\standalone\deployments
14:08:22,475 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "JAX-RS_examples.war" (runtime-name: "JAX-RS_examples.war")
14:08:22,885 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final
14:08:23,423 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
14:08:25,131 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (ServerService Thread Pool -- 61) Deploying javax.ws.rs.core.Application: class com.thejavageek.jaxrs.ExampleApplication
14:08:25,203 INFO [org.hibernate.validator.internal.util.Version] (ServerService Thread Pool -- 61) HV000001: Hibernate Validator 5.1.3.Final
14:08:25,283 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0021: Registered web context: /JAX-RS_examples
14:08:25,463 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "JAX-RS_examples.war" (runtime-name : "JAX-RS_examples.war")
14:08:25,939 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
14:08:25,941 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
14:08:25,942 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 9.0.2.Final (WildFly Core 1.0.2.Final) started in 9899ms - Started 272 of 453 services (221 services are lazy, passive or on-demand)
I am trying to access the application like this :
http://127.0.0.1:9990/JAX-RS_examples/rest/HelloWorld/sayHello
And getting 404 not found.
Came across similar thread but can't figure out :
WildFly running, project deployed, but 404
someone already told you.
You call your REST service with the port 9990.
But, this port is form the admin console.
by default, the correct port should be 8080. So, just call:
http://127.0.0.1:8080/JAX-RS_examples/rest/HelloWorld/sayHello
The runtime name needs to have a .war estension.
I am trying to access a jboss-as-7.1.1-Final admin console, but when I try to reach for the address: ip_address:9991 (I changed the port from 9990 to 9991) the browser seems it cannot move on from the loading spinner:
jboss admin console spinner
I already edited the standalone.xml file to allow any IP to reach the interface (so it is not limited to 127.0.0.1) and I disabled iptables to prevent any possible issue.
I have no problems reaching the deployed web applications or the server welcome-page on the 8080 port.
12:45:20,721 INFO [org.jboss.as.osgi] (MSC service thread 1-5) JBAS011942:
Stopping OSGi Framework
12:45:20,732 INFO [org.apache.catalina.core.StandardContext] (MSC service thread 1-4) Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started
12:45:38,335 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
12:45:38,379 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
12:45:38,419 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
12:45:38,423 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
12:45:38,461 INFO [org.jboss.as.connector] (MSC service thread 1-7) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
12:45:38,480 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
12:45:38,564 INFO [org.jboss.as.security] (MSC service thread 1-6) JBAS013100: Current PicketBox version=4.0.7.Final
12:45:38,573 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
12:45:38,648 INFO [org.jboss.as.naming] (MSC service thread 1-8) JBAS011802: Starting Naming Service
12:45:38,677 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default]
12:45:38,758 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
12:45:39,148 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.2.GA
12:45:39,230 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-5) Starting Coyote HTTP/1.1 on http--0.0.0.0-8080
12:45:39,467 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) JBAS015012: Started FileSystemDeploymentService for directory /opt/jboss-as-7.1.1.Final/standalone/deployments
12:45:39,485 INFO [org.jboss.as.remoting] (MSC service thread 1-5) JBAS017100: Listening on /0.0.0.0:9999
12:45:39,485 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /0.0.0.0:4447
12:45:39,626 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
-- Deployment info cut --
12:45:54,326 INFO [net.fckeditor.connector.ConnectorServlet] (MSC service thread 1-7) ConnectorServlet successfully initialized!
12:45:54,471 INFO [net.fckeditor.connector.ConnectorServlet] (MSC service thread 1-5) ConnectorServlet successfully initialized!
-- Deployment info cut --
12:45:57,994 INFO [org.jboss.as] (MSC service thread 1-7) JBAS015951: Admin console listening on http://0.0.0.0:9991
12:45:57,995 INFO [org.jboss.as] (MSC service thread 1-7) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 21387ms - Started 999 of 1078 services (78 services are passive or on-demand)
JBoss is running (as a service) on a CentOS7 x64 server.
Does anyone know how to fix this issue?
Thanks in advance for your time.
please help me to find solution to this error, while I'm trying to start Jboss 7.1.1 ( JEE eclipse )
01:41:07,497 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
01:41:07,678 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
01:41:07,726 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
01:41:08,771 INFO [org.xnio] XNIO Version 3.0.3.GA
01:41:08,772 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
01:41:08,783 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
01:41:08,793 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
01:41:08,812 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
01:41:08,819 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
01:41:08,832 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
01:41:08,846 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
01:41:08,854 INFO [org.jboss.as.connector] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
01:41:08,865 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
01:41:08,875 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
01:41:08,906 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
01:41:08,932 INFO [org.jboss.as.naming] (MSC service thread 1-5) JBAS011802: Starting Naming Service
01:41:08,941 INFO [org.jboss.as.security] (MSC service thread 1-5) JBAS013100: Current PicketBox version=4.0.7.Final
01:41:08,980 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.0)
01:41:08,992 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
01:41:09,017 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
01:41:09,136 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA
01:41:09,431 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) JBAS015012: Started FileSystemDeploymentService for directory D:\ESPRIT\4SIM3\Architecures N-Tiers JEE (4SIM)\S1 (Intro + EJB)\JEE6ToolsEsprit\JEE6ToolsEsprit\Server\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\standalone\deployments
01:41:09,436 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found firstJB.jar in deployment directory. To trigger deployment create a file called firstJB.jar.dodeploy
01:41:09,587 INFO [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on localhost/127.0.0.1:4447
01:41:09,607 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Démarrage de Coyote HTTP/1.1 sur http-localhost-127.0.0.1-8383
01:41:09,619 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.remoting.server.management: org.jboss.msc.service.StartException in service jboss.remoting.server.management: JBAS017112: Address already in use: bind /127.0.0.1:9999
at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:109)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_23]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_23]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_23]
Caused by: java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_23]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126) [rt.jar:1.6.0_23]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.jar:1.6.0_23]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) [rt.jar:1.6.0_23]
at org.xnio.nio.NioXnioWorker.createTcpServer(NioXnioWorker.java:287)
at org.xnio.XnioWorker.createStreamServer(XnioWorker.java:135)
at org.jboss.remoting3.remote.RemoteConnectionProvider$ProviderInterface.createServer(RemoteConnectionProvider.java:209)
at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:101)
... 5 more
01:41:09,736 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:/mysql]
01:41:09,736 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
01:41:09,752 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.remoting.server.management: org.jboss.msc.service.StartException in service jboss.remoting.server.management: JBAS017112: Address already in use: bind /127.0.0.1:9999
org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed
to start service jboss.remoting.server.management:
org.jboss.msc.service.StartException in service
jboss.remoting.server.management: JBAS017112: Address already in use:
bind /127.0.0.1:9999
It looks like the address is already bound. I would check that you don't already have another process previously started listening on that port. Kill it and try to start again if it does exist.
On Windows:
Try "netstat -aon" command.
Running this command would list all current processes and the ports (Local Address) using.
Example:
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 864
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 127.0.0.1:5432 0.0.0.0:0 LISTENING 2004
TCP 127.0.0.1:5432 127.0.0.1:49285 ESTABLISHED 2004
Find the process with bind address you are having issues with (in your case /127.0.0.1:9999)
Try killing the process using "taskkill /f /pid PID"