[JBoss Messaging] - Socket Timeout wit JBoss Messaging 1.0.1 SP4
by oleznew
Hi,
I am having a client that connects to a reliable queue as a receiver.
It consumes messages correctly, but when no messages arrive, it stops processing after about 60 seconds with the following error:
|
| [07/03/06 15:27:15.348] DEBUG: SocketClientInvoker[4d41e2, socket://10.196.110.62:7776] got exception java.net.SocketTimeoutException: Read timed out
| [07/03/06 15:27:15.349] DEBUG: org.jboss.jms.client.remoting.ClientSocketWrapper@1f42731 closing
| [07/03/06 15:27:15.352] ERROR: Got marshalling exception, exiting
| java.net.SocketTimeoutException: Read timed out
| at java.net.SocketInputStream.socketRead0(Native Method)
| at java.net.SocketInputStream.read(SocketInputStream.java:129)
| at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
| at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
| at java.io.FilterInputStream.read(FilterInputStream.java:66)
| at org.jboss.serial.io.JBossObjectInputStream.read(JBossObjectInputStream.java:193)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:902)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:552)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
| at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:126)
| at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:195)
| at java.util.TimerThread.mainLoop(Timer.java:432)
| at java.util.TimerThread.run(Timer.java:382)
| [07/03/06 15:27:15.419] DEBUG: ConnectionValidator failed to ping via SocketClientInvoker[4d41e2, socket://10.196.110.62:7776]
| java.rmi.MarshalException: Socket timed out. Waited 1000 milliseconds for response while calling on InvokerLocator [socket://10.196.110.62:7776/?clientSock
| etClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&serializationtype=jboss&socket
| .check_connection=false&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat]; nested exception is:
| java.net.SocketTimeoutException: Read timed out
| at org.jboss.remoting.transport.socket.SocketClientInvoker.handleException(SocketClientInvoker.java:117)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:613)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
| at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:126)
| at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:195)
| at java.util.TimerThread.mainLoop(Timer.java:432)
| at java.util.TimerThread.run(Timer.java:382)
| Caused by: java.net.SocketTimeoutException: Read timed out
| at java.net.SocketInputStream.socketRead0(Native Method)
| at java.net.SocketInputStream.read(SocketInputStream.java:129)
| at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
| at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
| at java.io.FilterInputStream.read(FilterInputStream.java:66)
| at org.jboss.serial.io.JBossObjectInputStream.read(JBossObjectInputStream.java:193)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:902)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:552)
| ... 5 more
| [07/03/06 15:27:15.421] DEBUG: ConnectionValidator[SocketClientInvoker[4d41e2, socket://10.196.110.62:7776], pingPeriod=2000 ms]'s connections is invalid
| [07/03/06 15:27:15.427] DEBUG: removed SocketClientInvoker[4d41e2, socket://10.196.110.62:7776] from registry
| [07/03/06 15:27:15.427] DEBUG: SocketClientInvoker[4d41e2, socket://10.196.110.62:7776] disconnecting ...
| [07/03/06 15:27:15.429] DEBUG: ConnectionValidator[SocketClientInvoker[4d41e2, socket://10.196.110.62:7776], pingPeriod=2000 ms] stopped, returning true
| [07/03/06 15:27:15.514] ERROR: Caught exception from connection
| java.lang.Exception: Could not connect to server!
| at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:201)
| at java.util.TimerThread.mainLoop(Timer.java:432)
| at java.util.TimerThread.run(Timer.java:382)
|
|
|
What is the reason for that? How can it be fixed?
Many Thanks,
Leznew
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025421#4025421
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025421
19Â years, 1Â month
[JBossCache] - Re: JBossCache 1.3 - CacheStoreInterceptor does not commit t
by archanaa_panda
Yippppeeeeeeeee!!!!
I have solved the problem!!!
Actually I should have used an XADataSource for the underlying database to use global transactions for the cache.
The clue of the problem was in comments of TxInterceptor.RemoteSynchronizationHandler.afterCompletion()
- // this should really not be done here -
// it is supposed to be post commit not actually run the commit
Actually in 2-phase commit, the transaction would already have been committed, so there is no way that connection.commit() would be called in CacheStoreInterceptor.
I would recommend that this should be included as a part of the faq or jboss cache tutorials - that whenever we are using a backing store with application server's TransactionManager, we should always use an XADataSource.
<attribute name="CacheLoaderConfiguration">
| <config>
| <passivation>false</passivation>
| <preload>/</preload>
| <shared>true</shared>
| <cacheloader>
| <class>org.jboss.cache.loader.JDBCCacheLoader</class>
| <properties>
| cache.jdbc.table.name=jbosscache
| cache.jdbc.table.create=true
| cache.jdbc.table.drop=false
| cache.jdbc.table.primarykey=jbosscache_pk
| cache.jdbc.fqn.column=fqn
| cache.jdbc.fqn.type=varchar(255)
| cache.jdbc.node.column=node
| cache.jdbc.node.type=blob
| cache.jdbc.parent.column=parent
| cache.jdbc.datasource=AshleyCacheDataSource
| </properties>
| <async>false</async>
| <fetchPersistentState>true</fetchPersistentState>
| <ignoreModifications>false</ignoreModifications>
| </cacheloader>
| </config>
| </attribute>
OR
<attribute name="CacheLoaderConfiguration">
| <config>
| <passivation>false</passivation>
| <preload>/</preload>
| <shared>true</shared>
| <cacheloader>
| <class>org.jboss.cache.loader.JDBCCacheLoader</class>
| <properties>
| cache.jdbc.table.name=jbosscache
| cache.jdbc.table.create=true
| cache.jdbc.table.drop=false
| cache.jdbc.table.primarykey=jbosscache_pk
| cache.jdbc.fqn.column=fqn
| cache.jdbc.fqn.type=varchar(255)
| cache.jdbc.node.column=node
| cache.jdbc.node.type=blob
| cache.jdbc.parent.column=parent
| cache.jdbc.driver=oracle.jdbc.xa.client.OracleXADataSource
| cache.jdbc.url=jdbc:oracle:thin:@localhost:1521:ACRMDEV
| cache.jdbc.user=FASTDEV
| cache.jdbc.password=fastdev123$
| </properties>
| <async>false</async>
| <fetchPersistentState>true</fetchPersistentState>
| <ignoreModifications>false</ignoreModifications>
| </cacheloader>
| </config>
| </attribute>
Took me 2 days for this problem but I must say it was a wonderful experience and great sleuthing ;)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025417#4025417
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025417
19Â years, 1Â month