7:22 a.m.
Albert Dabrowski [https://community.jboss.org/people/aldab] created the discussion
"HornetQ issue while started on 7.1.3.Final"
To view the discussion, visit: https://community.jboss.org/message/777162#777162
--------------------------------------------------------------
After suceesful jboss AS 7.1.3.Final startup on standalone-full configuration some warning
regarding disconnection on hornetq occurs. It's raw start-up with no changes and no
deployments.
Do anyone had such similar issues? Once I remove connection pooling this warning will
disapear but would be good to know what's the issue.
Environment: Windows, jboss AS 7.1.3.Final build taken from a tag
09:43:59,872 INFO [org.jboss.modules] JBoss Modules version 1.1.3.GA
09:44:00,012 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
09:44:00,059 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.3.Final "Arges"
starting
09:44:01,044 INFO [org.xnio] XNIO Version 3.0.6.GA
09:44:01,044 INFO [org.jboss.as.server] JBAS015888: Creating http management service
using socket-binding (management-http)
09:44:01,044 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.6.GA
09:44:01,059 INFO [org.jboss.remoting] JBoss Remoting version 3.2.8.SP1
09:44:01,075 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
09:44:01,122 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 32)
JBAS016200: Activating ConfigAdmin Subsystem
09:44:01,137 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread
Pool -- 33) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
09:44:01,169 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 37)
JBAS010280: Activating Infinispan subsystem.
09:44:01,262 INFO [org.jboss.as.jacorb] (ServerService Thread Pool -- 38) JBAS016300:
Activating JacORB Subsystem
09:44:01,325 INFO [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408:
Starting JCA Subsystem (JBoss IronJacamar 1.0.12.Final)
09:44:01,340 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 49) JBAS011906:
Activating OSGi Subsystem
09:44:01,356 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 48) JBAS011800:
Activating Naming Subsystem
09:44:01,356 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting
Naming Service
09:44:01,387 INFO [org.jboss.as.security] (ServerService Thread Pool -- 54) JBAS013171:
Activating Security Subsystem
09:44:01,403 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 58)
JBAS015537: Activating WebServices Extension
09:44:01,403 INFO [org.jboss.jaxr] (MSC service thread 1-1) JBAS014000: Started JAXR
subsystem, binding JAXR connection factory into JNDI as:
java:jboss/jaxr/ConnectionFactory
09:44:01,419 INFO [org.jboss.as.security] (MSC service thread 1-1) JBAS013170: Current
PicketBox version=4.0.13.Final
09:44:01,434 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400:
Bound mail session [java:jboss/mail/Default]
09:44:01,840 WARN [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011600: AIO
wasn't located on this platform, it will fall back to using pure Java NIO. If your
platform is Linux, install LibAIO to enable the AIO journal
09:44:01,840 WARN [jacorb.codeset] (MSC service thread 1-2) Warning - unknown codeset
(Cp1252) - defaulting to ISO-8859-1
09:44:01,872 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016330: CORBA ORB
Service started
09:44:01,919 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4)
Starting Coyote HTTP/1.1 on http-localhost/127.0.0.1:8080
09:44:02,028 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread
1-1) live server is starting with configuration HornetQ Configuration
(clustered=false,backup=false,sharedStore=true,journalDirectory=C:\Motorola\test\jboss-as-7.1.3.Final\standalone\data\messagingjournal,bindingsDirectory=C:\Motorola\test\jboss-as-7.1.3.Final\standalone\data\messagingbindings,largeMessagesDirectory=C:\Motorola\test\jboss-as-7.1.3.Final\standalone\data\messaginglargemessages,pagingDirectory=C
:\Motorola\test\jboss-as-7.1.3.Final\standalone\data\messagingpaging)
09:44:02,028 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread
1-1) Waiting to obtain live lock
09:44:02,169 INFO [org.hornetq.core.persistence.impl.journal.JournalStorageManager] (MSC
service thread 1-1) Using NIO Journal
09:44:02,200 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016328: CORBA Naming
Service started
09:44:02,247 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service
thread 1-3) JBoss Web Services - Stack CXF Server 4.0.5.GA
09:44:02,247 INFO [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread
1-1) Waiting to obtain live lock
09:44:02,247 INFO [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread
1-1) Live Server Obtained live lock
09:44:02,340 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3)
JBAS015012: Started FileSystemDeploymentService for directory
C:\Motorola\test\jboss-as-7.1.3.Final\standalone\deployments
09:44:02,356 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening
on 127.0.0.1:9999
09:44:02,356 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening
on 127.0.0.1:4447
09:44:02,528 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread
1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
09:44:02,559 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service
thread 1-1) Started Netty Acceptor version 3.2.6.Final-20df069 127.0.0.1:5455 for CORE
protocol
09:44:02,559 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service
thread 1-1) Started Netty Acceptor version 3.2.6.Final-20df069 127.0.0.1:5445 for CORE
protocol
09:44:02,559 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread
1-1) Server is now live
09:44:02,559 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread
1-1) HornetQ Server version 2.2.21.SNAPSHOT (HQ_2_2_21_final, 122)
[ec7e3342-321d-11e2-9852-4db017d6b448]) started
09:44:02,575 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601:
Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
09:44:02,575 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601:
Bound messaging object to jndi name java:/ConnectionFactory
09:44:02,606 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-1)
JBAS010406: Registered connection factory java:/JmsXA
09:44:02,637 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-1)
HornetQ resource adaptor started
09:44:02,637 INFO
[org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator]
(MSC service thread 1-1) IJ020002: Deployed: file://RaActivatorhornetq-ra
09:44:02,637 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-1)
JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
09:44:02,669 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management
interface listening on http://127.0.0.1:9990/management
09:44:02,669 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console
listening on http://127.0.0.1:9990
09:44:02,669 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS
7.1.3.Final "Arges" started in 3032ms - Started 166 of 252 services (85 services
are passive or on-demand)
09:46:04,574 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl]
(hornetq-failure-check-thread) Connection failure has been detected: Did not receive data
from invm:0. It is likely the client has exited or crashed without closing its connection,
or the network between the server and client has failed. You also might have configured
connection-ttl and client-failure-check-period incorrectly. Please check user manual for
more information. The connection will now be closed. [code=3]
09:46:04,574 WARN [org.hornetq.jms.server.recovery.RecoveryDiscovery] (Thread-1
(HornetQ-client-global-threads-2022533)) Notified of connection failure in xa discovery,
we will retry on the next recovery: HornetQException[errorCode=2 message=Channel
disconnected]
at
org.hornetq.core.client.impl.ClientSessionFactoryImpl.connectionDestroyed(ClientSessionFactoryImpl.java:381)
[hornetq-core-2.2.21.Final.jar:2.2.21.SNAPSHOT (HQ_2_2_21_final, 122)]
at
org.hornetq.core.remoting.impl.invm.InVMConnector$Listener$1.run(InVMConnector.java:203)
[hornetq-core-2.2.21.Final.jar:2.2.21.SNAPSHOT (HQ_2_2_21_final, 122)]
at
org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100)
[hornetq-core-2.2.21.Final.jar:2.2.21.SNAPSHOT (HQ_2_2_21_final, 122)]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[rt.jar:1.7.0_02]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[rt.jar:1.7.0_02]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_02]
09:46:12,574 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl]
(hornetq-failure-check-thread) Connection failure has been detected: Did not receive data
from invm:0. It is likely the client has exited or crashed without closing its connection,
or the network between the server and client has failed. You also might have configured
connection-ttl and client-failure-check-period incorrectly. Please check user manual for
more information. The connection will now be closed. [code=3]
09:46:12,574 WARN [org.hornetq.core.server.impl.ServerSessionImpl]
(hornetq-failure-check-thread) Client connection failed, clearing up resources for session
4ac5c5dc-3225-11e2-a523-c7d24ec98fd0
09:46:12,574 WARN [org.hornetq.core.server.impl.ServerSessionImpl]
(hornetq-failure-check-thread) Cleared up resources for session
4ac5c5dc-3225-11e2-a523-c7d24ec98fd0
09:46:12,574 WARN [org.hornetq.jms.server.recovery.HornetQXAResourceWrapper] (Thread-0
(HornetQ-client-global-threads-2022533)) Notified of connection failure in xa recovery
connectionFactory for provider ClientSessionFactoryImpl [serverLocator=ServerLocatorImpl
[initialConnectors=[org-hornetq-core-remoting-impl-invm-InVMConnectorFactory?server-id=0],
discoveryGroupConfiguration=null],
connectorConfig=org-hornetq-core-remoting-impl-invm-InVMConnectorFactory?server-id=0,
backupConfig=null] will
attempt reconnect on next pass: HornetQException[errorCode=2 message=Channel
disconnected]
at
org.hornetq.core.client.impl.ClientSessionFactoryImpl.connectionDestroyed(ClientSessionFactoryImpl.java:381)
[hornetq-core-2.2.21.Final.jar:2.2.21.SNAPSHOT (HQ_2_2_21_final, 122)]
at
org.hornetq.core.remoting.impl.invm.InVMConnector$Listener$1.run(InVMConnector.java:203)
[hornetq-core-2.2.21.Final.jar:2.2.21.SNAPSHOT (HQ_2_2_21_final, 122)]
at
org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100)
[hornetq-core-2.2.21.Final.jar:2.2.21.SNAPSHOT (HQ_2_2_21_final, 122)]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[rt.jar:1.7.0_02]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[rt.jar:1.7.0_02]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_02]
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/777162#777162]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]