[JBoss Remoting Development] - Threads Hanging in MicroSocketClientInvoker.readVersion()
by Nathan Ciliberto
Nathan Ciliberto [http://community.jboss.org/people/snacker] created the discussion
"Threads Hanging in MicroSocketClientInvoker.readVersion()"
To view the discussion, visit: http://community.jboss.org/message/548604#548604
--------------------------------------------------------------
Note: this issue was originally reported here:
https://community.jboss.org/message/548382#548382 https://community.jboss.org/message/548382#548382
On the web server side we see occasionally see threads with this stack:
75: [Thread[jrpp-1390,5,jrpp]]/id=49440/hc=13398717/shc=*/state=RUNNABLE/name=*
java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketInputStream.read(SocketInputStream.java:129)
java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
java.io.BufferedInputStream.read(BufferedInputStream.java:237)
java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2249)
java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2429)
java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2499)
java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2571)
java.io.ObjectInputStream.read(ObjectInputStream.java:820)
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.*readVersion*(MicroSocketClientInvoker.java:1263)
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:838)
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:165)
org.jboss.remoting.Client.invoke(Client.java:1724)
org.jboss.remoting.Client.invoke(Client.java:629)
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
org.jboss.ejb3.security.client.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
$Proxy5.invoke(Unknown Source)
org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207)
org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164)
$Proxy1643.completeMyOrder(Unknown Source)
... rest of our business process thread stack...
On the jboss server for each thread above we usually see at least 2 jboss threads with the following stack:
816: [WorkerThread#10[10.1.4.245:46454]]/id=6923/hc=1806701791/shc=*/state=RUNNABLE/name=*
java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketInputStream.read(SocketInputStream.java:129)
java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
java.io.BufferedInputStream.read(BufferedInputStream.java:237)
java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2249)
java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2429)
java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2499)
java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2571)
java.io.ObjectInputStream.read(ObjectInputStream.java:820)
org.jboss.remoting.transport.socket.ServerThread.*readVersion*(ServerThread.java:1038)
org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:673)
org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:551)
org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
I am not sure what is going on, but it looks like there is something that occasionally gets messed up with these "readVersion(...)" methods.
These threads will hang for hours and days.
The only way we can get these to stop hanging is to send a Thread.interrupt() to the threads on the web server side.
Sending the interrupt to the thread on the jboss side only moves the problem to a different thread and doesn't stop the web server threads from hanging.
We are not sure what is causing this, but it appears to be a bug in jboss.
We are using 5.1.0 GA.
It looks like the class allows for timeout and retry settings, but I am not sure how to set these on the client side.
http://anonsvn.jboss.org/repos/jbossremoting/remoting2/tags/2.5.1/src/mai... http://anonsvn.jboss.org/repos/jbossremoting/remoting2/tags/2.5.1/src/mai...
The MANIFEST.MF of our jboss-remoting.jar shows version "2.5.1"
Is this related to https://jira.jboss.org/browse/JBREM-1188 https://jira.jboss.org/browse/JBREM-1188 ?
If so, I think the default of 30 seconds would be too long for us.
Is there a way to change that via a config file on the client side?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/548604#548604]
Start a new discussion in JBoss Remoting Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 10 months
[Beginner's Corner] - Incomplete specification of datasource for h2
by David Goldstein
David Goldstein [http://community.jboss.org/people/drdaveg] created the discussion
"Incomplete specification of datasource for h2"
To view the discussion, visit: http://community.jboss.org/message/548589#548589
--------------------------------------------------------------
I think this is trivial. I am trying to configure a datasource "testDS" for using H2 under JBoss.
<?xml version="1.0" encoding="UTF-8"?>
<datasources>
<local-tx-datasource>
<jndi-name>jdbc/testDS</jndi-name>
<connection-url>jdbc:h2:mem:mydb</connection-url>
<driver-class>org.h2.jdbcx.JdbcDataSource</driver-class>
<user-name>sa</user-name>
<password></password>
</local-tx-datasource>
</datasources>
and get the following - what am I missing? Thanks in advance!
David
--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@a4c217e { url=file:/C:/ blah blah path /jboss-4.2.3.GA/server/default/deploy/testDS.xml }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/C:/Documents and Settings/ blah blah path /jboss-4.2.3.GA/server/default/deploy/testDS.xml
altDD: null
lastDeployed: 1276802264395
lastModified: 1276802264379
mbeans:
--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@a4c217e { url=file:/C:/ blah blah path jboss-4.2.3.GA/server/default/deploy/testDS.xml }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/C:/ blah blah path /jboss-4.2.3.GA/server/default/deploy/testDS.xml
altDD: null
lastDeployed: 1276802264395
lastModified: 1276802264379
mbeans:
--- MBeans waiting for other MBeans ---
ObjectName: persistence.units:unitName=default
State: NOTYETINSTALLED
I Depend On:
jboss.jca:name=testDS,service=DataSourceBinding
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jca:name=testDS,service=DataSourceBinding
State: NOTYETINSTALLED
Depends On Me:
persistence.units:unitName=default
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/548589#548589]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 10 months
[JBoss Remoting] - Remote MDBs seem to stop after marshalling exception
by Mike Miller
Mike Miller [http://community.jboss.org/people/mikemil] created the discussion
"Remote MDBs seem to stop after marshalling exception"
To view the discussion, visit: http://community.jboss.org/message/548580#548580
--------------------------------------------------------------
Environment
-------------------------
JBoss 4.2.3
JBoss Messaging 1.4.4
JBoss Remoting 2.2.3
We have a couple servers and each have local queues and remote mdbs. After running for a couple of hours, we see the following exception - which mentions 'marshalling exception'. The problem is - after this exception, the remote mdbs for that server never seem to get triggered. We have to restart the JBoss server in order to the MDBs triggered.
{noformat}
2010-06-11 11:05:18,777 ERROR [org.jboss.remoting.transport.socket.SocketClientInvoker] Got marshalling exception, exiting
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:197)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:229)
at java.io.BufferedInputStream.read(BufferedInputStream.java:246)
at java.io.FilterInputStream.read(FilterInputStream.java:89)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1077)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:682)
at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:458)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:141)
at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:474)
at org.jboss.remoting.Client.setupClientLease(Client.java:1912)
at org.jboss.remoting.Client.connect(Client.java:1800)
at org.jboss.remoting.Client.connect(Client.java:652)
at org.jboss.jms.client.remoting.JMSRemotingConnection$1.run(JMSRemotingConnection.java:362)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:356)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:165)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:80)
at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:101)
at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:95)
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:187)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:188)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java:615)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl$ExceptionListenerRunnable.run(JMSContainerInvoker.java:1533)
at java.lang.Thread.run(Thread.java:810)
2010-06-11 11:05:18,778 DEBUG [org.jboss.remoting.InvokerRegistry] removed SocketClientInvoker[1d2c1d2c, bisocket://cholpos01p.na.odcorp.net:14457] from registry
2010-06-11 11:05:18,778 DEBUG [org.jboss.remoting.transport.socket.MicroSocketClientInvoker] SocketClientInvoker[1d2c1d2c, bisocket://cholpos01p.na.odcorp.net:14457] disconnecting ...
2010-06-11 11:05:18,778 DEBUG [org.jboss.remoting.Client] Client[302125570:a1jn4v-s8ubem-gaai3x6d-1-gab58h4q-2yw] is disconnected
2010-06-11 11:05:18,778 DEBUG [org.jboss.remoting.Client] Client[376575602:a1jn4v-s8ubem-gaai3x6d-1-gab58h4q-2yx] is disconnected
2010-06-11 11:05:18,778 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Initialization failed DLQHandler
org.jboss.jms.exception.MessagingNetworkFailureException
at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:240)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:198)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:80)
at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:101)
at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:95)
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:187)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:188)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java:615)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl$ExceptionListenerRunnable.run(JMSContainerInvoker.java:1533)
at java.lang.Thread.run(Thread.java:810)
Caused by:
org.jboss.remoting.CannotConnectException: Error setting up client lease upon performing connect.
at org.jboss.remoting.Client.connect(Client.java:1804)
at org.jboss.remoting.Client.connect(Client.java:652)
at org.jboss.jms.client.remoting.JMSRemotingConnection$1.run(JMSRemotingConnection.java:362)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:356)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:165)
... 14 more
Caused by:
java.lang.Exception: Error setting up client lease
at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:508)
at org.jboss.remoting.Client.setupClientLease(Client.java:1912)
at org.jboss.remoting.Client.connect(Client.java:1800)
... 19 more
Caused by:
java.rmi.MarshalException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is:
java.net.SocketException: Connection reset
at org.jboss.remoting.transport.socket.SocketClientInvoker.handleException(SocketClientInvoker.java:127)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:740)
at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:458)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:141)
at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:474)
... 21 more
Caused by:
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:197)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:229)
at java.io.BufferedInputStream.read(BufferedInputStream.java:246)
at java.io.FilterInputStream.read(FilterInputStream.java:89)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1077)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:682)
... 24 more
2010-06-11 11:05:18,778 ERROR [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Reconnect failed: JMS provider failure detected for ImportMerchandiseMDB
org.jboss.jms.exception.MessagingNetworkFailureException
at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:240)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:198)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:80)
at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:101)
at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:95)
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:187)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:188)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java:615)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl$ExceptionListenerRunnable.run(JMSContainerInvoker.java:1533)
at java.lang.Thread.run(Thread.java:810)
Caused by:
org.jboss.remoting.CannotConnectException: Error setting up client lease upon performing connect.
at org.jboss.remoting.Client.connect(Client.java:1804)
at org.jboss.remoting.Client.connect(Client.java:652)
at org.jboss.jms.client.remoting.JMSRemotingConnection$1.run(JMSRemotingConnection.java:362)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:356)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:165)
... 14 more
Caused by:
java.lang.Exception: Error setting up client lease
at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:508)
at org.jboss.remoting.Client.setupClientLease(Client.java:1912)
at org.jboss.remoting.Client.connect(Client.java:1800)
... 19 more
Caused by:
java.rmi.MarshalException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is:
java.net.SocketException: Connection reset
at org.jboss.remoting.transport.socket.SocketClientInvoker.handleException(SocketClientInvoker.java:127)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:740)
at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:458)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:141)
at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:474)
... 21 more
Caused by:
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:197)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:229)
at java.io.BufferedInputStream.read(BufferedInputStream.java:246)
at java.io.FilterInputStream.read(FilterInputStream.java:89)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1077)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:682)
... 24 more
2010-06-11 11:05:18,778 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] innerStop
2010-06-11 11:05:18,778 DEBUG [org.jboss.jms.asf.StdServerSessionPool] Clearing 0 from ServerSessionPool
2010-06-11 11:05:18,778 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Destroying DLQHandler
2010-06-11 11:05:18,778 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Destroyed DLQHandler
2010-06-11 11:05:18,778 INFO [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Waiting for reconnect internal 10000ms for ImportMerchandiseMDB
2010-06-11 11:05:28,778 INFO [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Trying to reconnect to JMS provider for ImportMerchandiseMDB
2010-06-11 11:05:28,778 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Initializing
2010-06-11 11:05:28,779 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Looking up provider adapter: java:/RemoteJMSProvider
2010-06-11 11:05:28,779 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Provider adapter: org.jboss.jms.jndi.JNDIProviderAdapter@13ae13ae
2010-06-11 11:05:28,779 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Creating DLQHandler
2010-06-11 11:05:28,956 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Using factory: JBossConnectionFactory->ConnectionFactoryDelegate[jboss.messaging.connectionfactory:service=ConnectionFactory, SID=0]
{noformat}
Looking for suggestions on this. Customer is considering migrating back to MQ from Messaging because we didn't see these types of connection issues.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/548580#548580]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 10 months