GUJ Discussões   :   últimos tópicos   |   categorias   |   GUJ Respostas

[RESOLVIDO] Meu servidor wildfly não está inicializando


#1

Boa noite, estou com problema no meu servidor wildfly, ele não está subindo pq na porta 9990 está sendo usada e não consigo finalizar o serviço, segue abaixo a mensagem:
13:07:52,123 INFO [org.jboss.modules] (main) JBoss Modules version 1.8.7.Final
13:07:52,853 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.5.Final
13:07:52,867 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.2.Final
13:07:53,074 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 15.0.1.Final (WildFly Core 7.0.0.Final) starting
13:07:54,373 INFO [org.wildfly.security] (ServerService Thread Pool – 27) ELY00001: WildFly Elytron version 1.7.0.Final
13:07:55,362 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.
13:07:55,433 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool – 8) 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.
13:07:55,538 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
13:07:55,574 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.6.5.Final
13:07:55,585 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.6.5.Final
13:07:55,734 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool – 49) WFLYCLINF0001: Activating Infinispan subsystem.
13:07:55,903 INFO [org.jboss.as.webservices] (ServerService Thread Pool – 72) WFLYWS0002: Activating WebServices Extension
13:07:55,869 INFO [org.jboss.as.jsf] (ServerService Thread Pool – 56) WFLYJSF0007: Activated the following JSF Implementations: [main]
13:07:55,914 INFO [org.jboss.as.mail.extension] (MSC service thread 1-5) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
13:07:55,809 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.11.Final)
13:07:55,783 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool – 51) WFLYRS0016: RESTEasy version 3.6.2.Final
13:07:55,770 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool – 42) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
13:07:55,945 INFO [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool – 59) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
13:07:55,954 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2
13:07:55,950 INFO [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool – 58) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
13:07:55,968 INFO [org.jboss.as.security] (ServerService Thread Pool – 68) WFLYSEC0002: Activating Security Subsystem
13:07:55,971 WARN [org.jboss.as.txn] (ServerService Thread Pool – 70) 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.
13:07:56,029 INFO [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool – 61) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
13:07:56,040 INFO [org.jboss.as.naming] (ServerService Thread Pool – 62) WFLYNAM0001: Activating Naming Subsystem
13:07:56,059 INFO [org.jboss.as.security] (MSC service thread 1-5) WFLYSEC0001: Current PicketBox version=5.0.3.Final
13:07:56,071 INFO [org.wildfly.extension.microprofile.metrics.smallrye] (ServerService Thread Pool – 60) WFLYMETRICS0001: Activating Eclipse MicroProfile Metrics Subsystem
13:07:56,077 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0003: Undertow 2.0.15.Final starting
13:07:56,108 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
13:07:56,243 INFO [io.smallrye.metrics] (MSC service thread 1-1) Converted [2] config entries and added [4] replacements
13:07:56,273 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
13:07:56,305 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
13:07:56,339 INFO [io.smallrye.metrics] (MSC service thread 1-1) Converted [3] config entries and added [18] replacements
13:07:56,410 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool – 71) WFLYUT0014: Creating file handler for path ‘C:\Program Files\wildfly-15.0.1.Final/welcome-content’ with options [directory-listing: ‘false’, follow-symlink: ‘false’, case-sensitive: ‘true’, safe-symlink-paths: ‘[]’]
13:07:57,187 INFO [org.wildfly.extension.io] (ServerService Thread Pool – 50) WFLYIO001: Worker ‘default’ has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
13:07:57,205 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) 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.
13:07:57,204 INFO [org.jboss.as.ejb3] (MSC service thread 1-8) 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.
13:07:57,269 INFO [org.jboss.as.patching] (MSC service thread 1-8) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
13:07:57,323 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-5) WFLYDM0111: Keystore C:\Program Files\wildfly-15.0.1.Final\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
13:07:57,357 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Program Files\wildfly-15.0.1.Final\standalone\deployments
13:07:57,383 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 5.0.8.Final
13:07:57,386 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: Started server default-server.
13:07:57,393 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0018: Host default-host starting
13:07:57,495 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
13:07:57,548 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
13:07:57,606 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service org.wildfly.management.http.extensible: org.jboss.msc.service.StartException in service org.wildfly.management.http.extensible: java.net.BindException: Address already in use: bind localhost/127.0.0.1:9990
at org.jboss.as.server@7.0.0.Final//org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:349)
at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
at org.jboss.threads@2.3.2.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.base/java.lang.Thread.run(Thread.java:834)

13:07:57,698 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0493: EJB subsystem suspension complete
13:07:57,789 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBossWS 5.2.4.Final (Apache CXF 3.2.5.jbossorg-1)
13:07:57,828 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
13:07:57,833 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” => {“org.wildfly.management.http.extensible” => “java.net.BindException: Address already in use: bind localhost/127.0.0.1:9990”}}
13:07:57,838 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” => {“org.wildfly.management.http.extensible” => “java.net.BindException: Address already in use: bind localhost/127.0.0.1:9990”}}

Como posso arrumar isso para poder subir minhas aplicações?


#2

Muda a porta de conexão do wildfly!


#3

Boa noite amigo.

A porta 9990 é padrão para a interface de administração do wildfly, o que parece é ele não está encontrando o arquivo de configuração do standalone.


#4

eu tento mudar, mas não estou conseguindo mudar essa porta para outra qualquer


#5

sim, a placa de video está sendo inicializada nessa porta 9990, na vdd é o drivers de atualização da placa de video que está sendo inicializada, como que posso trocar a porta para poder inicializar o meu servidor?


#6

Será que está fazendo da forma correta?

Você tem que alterar lá nas propriedades do seu arquivo standalone.xml

Veja:


#7

maninho muito obrigado,conseguir alterar a portas do meu servidor e está rodando lisinho, muito obrigado pela atenção