Wildfly 10.1.0. Финальный запуск без прослушивания порта 8443 - PullRequest
0 голосов
/ 06 июня 2018

Wildfly запускается нормально, но при попытке прослушивания порта 8443 истекает время ожидания, даже если этот порт ничего не слушает.

Происходит следующее, последняя строка остается такой до 300происходит второй тайм-аут вместо обычной загрузки.Это происходит только после того, как я заменяю сертификат по умолчанию своим собственным.Я попробовал несколько сертификатов, но ничего не запускается.Что странно, это то, что это работало раньше.

2018-06-06 10:22:23,535 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
2018-06-06 10:22:23,547 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
2018-06-06 10:22:23,549 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
2018-06-06 10:22:23,754 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
2018-06-06 10:22:23,754 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-3) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
2018-06-06 10:22:23,754 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-6) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
2018-06-06 10:22:23,754 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
2018-06-06 10:22:23,935 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221007: Server is now live
2018-06-06 10:22:23,935 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-017 [nodeID=6be48663-6957-11e8-a06d-a78f0f48648c]
2018-06-06 10:22:23,939 INFO  [org.apache.activemq.artemis.jms.server] (ServerService Thread Pool -- 64) AMQ121005: Invalid "host" value "0.0.0.0" detected for "http-connector" connector. Switching to "TESTAPP1". If this new address is incorrect please manually configure the connector to use the proper one.
2018-06-06 10:22:23,953 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 64) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
2018-06-06 10:22:23,958 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 66) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue
2018-06-06 10:22:23,966 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 65) AMQ221003: trying to deploy queue jms.queue.DLQ
2018-06-06 10:22:23,967 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 67) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
2018-06-06 10:22:23,995 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007: Registered connection factory java:/JmsXA
2018-06-06 10:22:24,024 INFO  [org.apache.activemq.artemis.ra] (MSC service thread 1-3) Resource adaptor started
2018-06-06 10:22:24,024 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatoractivemq-ra
2018-06-06 10:22:24,026 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]
2018-06-06 10:22:24,026 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory

И это исключение, которое происходит после тайм-аута:

2018-06-06 23:40:36,887 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0348: Timeout after [600] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'add' at address '[
    ("core-service" => "management"),
    ("management-interface" => "http-interface")
]'
2018-06-06 23:40:41,897 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0190: Step handler org.jboss.as.domain.management.security.SecurityRealmAddHandler$ServiceInstallStepHandler@befd376 for operation {"address" => [("core-service" => "management"),("security-realm" => "ApplicationRealm")],"operation" => "add","map-groups-to-roles" => undefined} at address [
    ("core-service" => "management"),
    ("security-realm" => "ApplicationRealm")
] failed handling operation rollback -- java.util.concurrent.TimeoutException: java.util.concurrent.TimeoutException
    at org.jboss.as.controller.OperationContextImpl.waitForRemovals(OperationContextImpl.java:498)
    at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1369)
    at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1328)
    at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1311)
    at org.jboss.as.controller.AbstractOperationContext$Step.access$300(AbstractOperationContext.java:1185)
    at org.jboss.as.controller.AbstractOperationContext.executeResultHandlerPhase(AbstractOperationContext.java:767)
    at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:644)
    at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
    at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1329)
    at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:493)
    at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:387)
    at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:349)
    at org.jboss.as.server.ServerService.boot(ServerService.java:397)
    at org.jboss.as.server.ServerService.boot(ServerService.java:366)
    at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299)
    at java.lang.Thread.run(Thread.java:748)

2018-06-06 23:40:41,898 ERROR [org.jboss.as.controller.client] (Controller Boot Thread) WFLYCTL0190: Step handler org.jboss.as.domain.management.security.SecurityRealmAddHandler$ServiceInstallStepHandler@befd376 for operation {"address" => [("core-service" => "management"),("security-realm" => "ApplicationRealm")],"operation" => "add","map-groups-to-roles" => undefined} at address [
    ("core-service" => "management"),
    ("security-realm" => "ApplicationRealm")
] failed handling operation rollback -- java.util.concurrent.TimeoutException
2018-06-06 23:40:46,899 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0190: Step handler org.jboss.as.domain.management.security.SecurityRealmAddHandler$ServiceInstallStepHandler@befd376 for operation {"address" => [("core-service" => "management"),("security-realm" => "ManagementRealm")],"operation" => "add","map-groups-to-roles" => false} at address [
    ("core-service" => "management"),
    ("security-realm" => "ManagementRealm")
] failed handling operation rollback -- java.util.concurrent.TimeoutException: java.util.concurrent.TimeoutException
    at org.jboss.as.controller.OperationContextImpl.waitForRemovals(OperationContextImpl.java:498)
    at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1369)
    at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1328)
    at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1311)
    at org.jboss.as.controller.AbstractOperationContext$Step.access$300(AbstractOperationContext.java:1185)
    at org.jboss.as.controller.AbstractOperationContext.executeResultHandlerPhase(AbstractOperationContext.java:767)
    at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:644)
    at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
    at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1329)
    at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:493)
    at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:387)
    at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:349)
    at org.jboss.as.server.ServerService.boot(ServerService.java:397)
    at org.jboss.as.server.ServerService.boot(ServerService.java:366)
    at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299)
    at java.lang.Thread.run(Thread.java:748)

2018-06-06 23:40:46,900 ERROR [org.jboss.as.controller.client] (Controller Boot Thread) WFLYCTL0190: Step handler org.jboss.as.domain.management.security.SecurityRealmAddHandler$ServiceInstallStepHandler@befd376 for operation {"address" => [("core-service" => "management"),("security-realm" => "ManagementRealm")],"operation" => "add","map-groups-to-roles" => false} at address [
    ("core-service" => "management"),
    ("security-realm" => "ManagementRealm")
] failed handling operation rollback -- java.util.concurrent.TimeoutException
2018-06-06 23:40:46,902 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA]
2018-06-06 23:40:46,903 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
2018-06-06 23:40:46,904 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 85) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
2018-06-06 23:40:46,906 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 86) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/ConnectionFactory
2018-06-06 23:40:46,919 INFO  [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 83) AMQ151003: resource adaptor stopped
2018-06-06 23:40:47,006 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 83) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-017 [6be48663-6957-11e8-a06d-a78f0f48648c] stopped
2018-06-06 23:40:51,900 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0190: Step handler org.jboss.as.controller.AbstractControllerService$ModelControllerServiceInitializationBootStepHandler$1@59924be2 for operation {"operation" => "boottime-controller-initializer-step","address" => []} at address [] failed handling operation rollback -- java.util.concurrent.TimeoutException: java.util.concurrent.TimeoutException
    at org.jboss.as.controller.OperationContextImpl.waitForRemovals(OperationContextImpl.java:498)
    at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1369)
    at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1328)
    at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1311)
    at org.jboss.as.controller.AbstractOperationContext$Step.access$300(AbstractOperationContext.java:1185)
    at org.jboss.as.controller.AbstractOperationContext.executeResultHandlerPhase(AbstractOperationContext.java:767)
    at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:644)
    at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
    at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1329)
    at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:493)
    at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:387)
    at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:349)
    at org.jboss.as.server.ServerService.boot(ServerService.java:397)
    at org.jboss.as.server.ServerService.boot(ServerService.java:366)
    at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299)
    at java.lang.Thread.run(Thread.java:748)

1 Ответ

0 голосов
/ 20 июня 2018

Есть ли причина, по которой вам понадобится интерфейс управления http?Если это происходит в среде CI, вероятно, вы все равно хотите отключить это.Необходимая конфигурация должна быть в любом случае в вашем файле production-standalone.xml или настроена через EAR / WAR / JAR приложений в нем через XML. https://access.redhat.com/solutions/192483

Что мне также интересно, если машина / кластер/ pod, на котором вы это разместили, не разрешает трафик на этот порт.

Если тайм-аут является проблемой, вы также можете отрегулировать это с помощью флага JAVA_OPS, и другие сообщили, что это происходит при запуске из отладки.режим в их IDE: Исключение одновременного тайм-аута при запуске сервера Jboss Wildfly 9.02

Кроме того, вы не можете использовать правильную конфигурацию для области безопасности или ее необходимо настроить для этогоокружающая среда.

...