EAP 7 start up hangs on logging socket handler

Solution Unverified - Updated

Environment

  • JBoss Enterprise Application Platform (EAP) 7.x

Issue

  • We use a socket-handler in our logging subsystem and if that destination socket handler is not available and reachable, we see JBoss start up hangs:
"MSC service thread 1-2" #18 prio=5 os_prio=0 cpu=616.95ms elapsed=120.44s tid=0x000055790ece0000 nid=0x78b runnable  [0x00007f37a1ee8000]
   java.lang.Thread.State: RUNNABLE
    at java.net.PlainSocketImpl.socketConnect(java.base@11.0.9/Native Method)
    at java.net.AbstractPlainSocketImpl.doConnect(java.base@11.0.9/AbstractPlainSocketImpl.java:399)
    - locked <0x00000000d64c8470> (a java.net.SocksSocketImpl)
    at java.net.AbstractPlainSocketImpl.connectToAddress(java.base@11.0.9/AbstractPlainSocketImpl.java:242)
    at java.net.AbstractPlainSocketImpl.connect(java.base@11.0.9/AbstractPlainSocketImpl.java:224)
    at java.net.SocksSocketImpl.connect(java.base@11.0.9/SocksSocketImpl.java:403)
    at java.net.Socket.connect(java.base@11.0.9/Socket.java:609)
    at java.net.Socket.connect(java.base@11.0.9/Socket.java:558)
    at org.jboss.as.network.OutboundSocketBinding.connect(OutboundSocketBinding.java:125)
    at org.jboss.as.logging.handlers.SocketHandlerResourceDefinition$WildFlyClientSocketFactory.createSocket(SocketHandlerResourceDefinition.java:441)
    at org.jboss.logmanager.handlers.TcpOutputStream.<init>(TcpOutputStream.java:165)
    at org.jboss.logmanager.handlers.SocketHandler.createOutputStream(SocketHandler.java:453)
    at org.jboss.logmanager.handlers.SocketHandler.initialize(SocketHandler.java:422)
    at org.jboss.logmanager.handlers.SocketHandler.doPublish(SocketHandler.java:211)
    - locked <0x00000000f49b7a10> (a java.lang.Object)
    at org.jboss.logmanager.ExtHandler.publish(ExtHandler.java:77)
    at org.jboss.logmanager.handlers.DelayedHandler.publishToChildren(DelayedHandler.java:213)
    at org.jboss.logmanager.handlers.DelayedHandler.activate(DelayedHandler.java:205)
    - locked <0x00000000f49b55f0> (a org.jboss.logmanager.handlers.DelayedHandler)
    at org.jboss.logmanager.handlers.DelayedHandler.setHandlers(DelayedHandler.java:124)
    at org.jboss.as.logging.handlers.SocketHandlerResourceDefinition$1$2$1.start(SocketHandlerResourceDefinition.java:252)
    - locked <0x00000000f49b55a0> (a org.jboss.as.logging.handlers.SocketHandlerResourceDefinition$1$2$1)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
    at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
    at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)
    at java.lang.Thread.run(java.base@11.0.9/Thread.java:834)

Root Cause

SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.