You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by jaya_srini <jy...@Hotmail.com> on 2008/06/17 00:12:32 UTC
Async exception with no exception listener: java.io.EOFException
hi all
I saw several posts regarding the async exception (listed below) in logs
with ActiveMQ 5.0.0. We are also seeing this exception randomly in the logs,
the bad part is it breaks the connection between Broker and the client even
tho the broker is up and running and there are no network connection issues
between the broker and the client.
I got the impression from the other posts regarding this issue that this has
been fixed in 5.1 release? Can someone confirm this? This is a production
problem for us right now and would really appreciate if someone can provide
a timely response. We are setting the wireFormat.maxInactivityDuration=-1 to
in the connect url and are using durable subscribers.
*WARN 13:50:24.571,ActiveMQ Transport:
,(org.apache.activemq.ActiveMQConnection:1653)> Async exception with no
exception listener: java.io.EOFException
java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:375)
at
org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
at
org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:192)
at
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:184)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:172)
at java.lang.Thread.run(Thread.java:619)
thanks!
jaya
--
View this message in context: http://www.nabble.com/Async-exception-with-no-exception-listener%3A-java.io.EOFException-tp17874356p17874356.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Async exception with no exception listener:
java.io.EOFException
Posted by jaya_srini <jy...@Hotmail.com>.
Thank You!
Is 5.1 backwards compatible with 5.0 configurattion? i.e if we get 5.1, we
shouldn't need to change any of our previous configuration we did with 5.0,
correct? (e.g. connect Url parameters, wireformat parameters etc)
rajdavies wrote:
>
>
> On 16 Jun 2008, at 23:12, jaya_srini wrote:
>
>>
>> hi all
>>
>> I saw several posts regarding the async exception (listed below) in
>> logs
>> with ActiveMQ 5.0.0. We are also seeing this exception randomly in
>> the logs,
>> the bad part is it breaks the connection between Broker and the
>> client even
>> tho the broker is up and running and there are no network connection
>> issues
>> between the broker and the client.
>>
>> I got the impression from the other posts regarding this issue that
>> this has
>> been fixed in 5.1 release? Can someone confirm this? This is a
>> production
>> problem for us right now and would really appreciate if someone can
>> provide
>> a timely response. We are setting the
>> wireFormat.maxInactivityDuration=-1 to
>> in the connect url and are using durable subscribers.
>>
>> *WARN 13:50:24.571,ActiveMQ Transport:
>> ,(org.apache.activemq.ActiveMQConnection:1653)> Async exception
>> with no
>> exception listener: java.io.EOFException
>> java.io.EOFException
>> at java.io.DataInputStream.readInt(DataInputStream.java:375)
>> at
>> org
>> .apache
>> .activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
>> at
>> org
>> .apache
>> .activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:
>> 192)
>> at
>> org
>> .apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:
>> 184)
>> at
>> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:
>> 172)
>> at java.lang.Thread.run(Thread.java:619)
>>
>>
>> thanks!
>> jaya
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Async-exception-with-no-exception-listener%3A-java.io.EOFException-tp17874356p17874356.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
> This is fixed in 5.1
>
>
>
>
> cheers,
>
> Rob
>
> http://open.iona.com/products/enterprise-activemq
> http://rajdavies.blogspot.com/
>
>
>
>
>
>
--
View this message in context: http://www.nabble.com/Async-exception-with-no-exception-listener%3A-java.io.EOFException-tp17874356p17915134.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Async exception with no exception listener:
java.io.EOFException
Posted by jaya_srini <jy...@Hotmail.com>.
ah...figured it out. In my activemq.xml I had the property useDatabaseLock
set as "true" on the JDBCPersistenceAdapter. This was working fine with 5.0
but with 5.1 , this is causing the broker to be terminated? Is this per
design?
Setting this property to "false" fixed it but I was wondering if there were
other impacts if we set the "useDatabaseLock" to false?
thanks!
jaya
jaya_srini wrote:
>
> Hi Rob
>
> I moved to 5.1 release but now I can't even start the broker :( using my
> activemq.xml config for 5.0.0. After a couple of minutes I get the
> following exception. Is there a keepAlive configuration I need to set in
> the URL now?
>
> ERROR ManagedTopicRegion - Could not stop service:
> TopicRegion: dest
> inations=4, subscriptions=2, memory=0%. Reason:
> java.lang.InterruptedException
> java.lang.InterruptedException
> at java.lang.Object.wait(Native Method)
> at
> org.apache.activemq.thread.DedicatedTaskRunner.shutdown(DedicatedTask
> Runner.java:72)
> at
> org.apache.activemq.thread.DedicatedTaskRunner.shutdown(DedicatedTask
> Runner.java:83)
> at org.apache.activemq.broker.region.Topic.stop(Topic.java:469)
> at
> org.apache.activemq.broker.region.AbstractRegion.stop(AbstractRegion.
> java:109)
> at
> org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:41)
> at
> org.apache.activemq.broker.region.RegionBroker.doStop(RegionBroker.ja
> va:627)
> at
> org.apache.activemq.broker.jmx.ManagedRegionBroker.doStop(ManagedRegi
> onBroker.java:109)
> at
> org.apache.activemq.broker.region.RegionBroker.stop(RegionBroker.java
> :187)
> at
> org.apache.activemq.broker.TransactionBroker.stop(TransactionBroker.j
> ava:117)
> at
> org.apache.activemq.broker.BrokerFilter.stop(BrokerFilter.java:157)
> at
> org.apache.activemq.broker.BrokerFilter.stop(BrokerFilter.java:157)
> at
> org.apache.activemq.broker.BrokerService$2.stop(BrokerService.java:15
> 41)
> at
> org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:41)
> at
> org.apache.activemq.broker.BrokerService.stop(BrokerService.java:491)
>
> at
> org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.stopBroker(JDBC
> PersistenceAdapter.java:474)
> at
> org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.databaseLockKee
> pAlive(JDBCPersistenceAdapter.java:466)
> at
> org.apache.activemq.store.jdbc.JDBCPersistenceAdapter$3.run(JDBCPersi
> stenceAdapter.java:260)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:44
> 1)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java
> :317)
> at
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
> access$101(ScheduledThreadPoolExecutor.java:98)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
> runPeriodic(ScheduledThreadPoolExecutor.java:181)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
> run(ScheduledThreadPoolExecutor.java:205)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
> utor.java:885)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
> .java:907)
> at java.lang.Thread.run(Thread.java:619)
> ERROR BrokerService$2 - Could not stop service:
> org.apache.active
> mq.broker.BrokerService$2@273f4e. Reason: java.lang.InterruptedException
> java.lang.InterruptedException
> at java.lang.Object.wait(Native Method)
> at
> org.apache.activemq.thread.DedicatedTaskRunner.shutdown(DedicatedTask
> Runner.java:72)
> at
> org.apache.activemq.thread.DedicatedTaskRunner.shutdown(DedicatedTask
> Runner.java:83)
> at org.apache.activemq.broker.region.Topic.stop(Topic.java:469)
> at
> org.apache.activemq.broker.region.AbstractRegion.stop(AbstractRegion.
> java:109)
> at
> org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:41)
> at
> org.apache.activemq.broker.region.RegionBroker.doStop(RegionBroker.ja
> va:627)
> at
> org.apache.activemq.broker.jmx.ManagedRegionBroker.doStop(ManagedRegi
> onBroker.java:109)
> at
> org.apache.activemq.broker.region.RegionBroker.stop(RegionBroker.java
> :187)
> at
> org.apache.activemq.broker.TransactionBroker.stop(TransactionBroker.j
> ava:117)
> at
> org.apache.activemq.broker.BrokerFilter.stop(BrokerFilter.java:157)
> at
> org.apache.activemq.broker.BrokerFilter.stop(BrokerFilter.java:157)
> at
> org.apache.activemq.broker.BrokerService$2.stop(BrokerService.java:15
> 41)
> at
> org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:41)
> at
> org.apache.activemq.broker.BrokerService.stop(BrokerService.java:491)
>
> at
> org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.stopBroker(JDBC
> PersistenceAdapter.java:474)
> at
> org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.databaseLockKee
> pAlive(JDBCPersistenceAdapter.java:466)
> at
> org.apache.activemq.store.jdbc.JDBCPersistenceAdapter$3.run(JDBCPersi
> stenceAdapter.java:260)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:44
> 1)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java
> :317)
> at
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
> access$101(ScheduledThreadPoolExecutor.java:98)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
> runPeriodic(ScheduledThreadPoolExecutor.java:181)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
> run(ScheduledThreadPoolExecutor.java:205)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
> utor.java:885)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
> .java:907)
> at java.lang.Thread.run(Thread.java:619)
> INFO BrokerService - ActiveMQ JMS Message Broker
> (JayasSuperDu
> perBroker1, ID:SE-JSRINIVA-DT1-1549-1213732885890-0:0) stopped
> WARN JDBCPersistenceAdapter - Failed to stop broker
>
>
> rajdavies wrote:
>>
>>
>> On 16 Jun 2008, at 23:12, jaya_srini wrote:
>>
>>>
>>> hi all
>>>
>>> I saw several posts regarding the async exception (listed below) in
>>> logs
>>> with ActiveMQ 5.0.0. We are also seeing this exception randomly in
>>> the logs,
>>> the bad part is it breaks the connection between Broker and the
>>> client even
>>> tho the broker is up and running and there are no network connection
>>> issues
>>> between the broker and the client.
>>>
>>> I got the impression from the other posts regarding this issue that
>>> this has
>>> been fixed in 5.1 release? Can someone confirm this? This is a
>>> production
>>> problem for us right now and would really appreciate if someone can
>>> provide
>>> a timely response. We are setting the
>>> wireFormat.maxInactivityDuration=-1 to
>>> in the connect url and are using durable subscribers.
>>>
>>> *WARN 13:50:24.571,ActiveMQ Transport:
>>> ,(org.apache.activemq.ActiveMQConnection:1653)> Async exception
>>> with no
>>> exception listener: java.io.EOFException
>>> java.io.EOFException
>>> at java.io.DataInputStream.readInt(DataInputStream.java:375)
>>> at
>>> org
>>> .apache
>>> .activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
>>> at
>>> org
>>> .apache
>>> .activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:
>>> 192)
>>> at
>>> org
>>> .apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:
>>> 184)
>>> at
>>> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:
>>> 172)
>>> at java.lang.Thread.run(Thread.java:619)
>>>
>>>
>>> thanks!
>>> jaya
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Async-exception-with-no-exception-listener%3A-java.io.EOFException-tp17874356p17874356.html
>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>
>> This is fixed in 5.1
>>
>>
>>
>>
>> cheers,
>>
>> Rob
>>
>> http://open.iona.com/products/enterprise-activemq
>> http://rajdavies.blogspot.com/
>>
>>
>>
>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Async-exception-with-no-exception-listener%3A-java.io.EOFException-tp17874356p17936409.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Async exception with no exception listener:
java.io.EOFException
Posted by jaya_srini <jy...@Hotmail.com>.
Hi Rob
I moved to 5.1 release but now I can't even start the broker :( using my
activemq.xml config for 5.0.0. After a couple of minutes I get the following
exception. Is there a keepAlive configuration I need to set in the URL now?
ERROR ManagedTopicRegion - Could not stop service: TopicRegion:
dest
inations=4, subscriptions=2, memory=0%. Reason:
java.lang.InterruptedException
java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at
org.apache.activemq.thread.DedicatedTaskRunner.shutdown(DedicatedTask
Runner.java:72)
at
org.apache.activemq.thread.DedicatedTaskRunner.shutdown(DedicatedTask
Runner.java:83)
at org.apache.activemq.broker.region.Topic.stop(Topic.java:469)
at
org.apache.activemq.broker.region.AbstractRegion.stop(AbstractRegion.
java:109)
at
org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:41)
at
org.apache.activemq.broker.region.RegionBroker.doStop(RegionBroker.ja
va:627)
at
org.apache.activemq.broker.jmx.ManagedRegionBroker.doStop(ManagedRegi
onBroker.java:109)
at
org.apache.activemq.broker.region.RegionBroker.stop(RegionBroker.java
:187)
at
org.apache.activemq.broker.TransactionBroker.stop(TransactionBroker.j
ava:117)
at
org.apache.activemq.broker.BrokerFilter.stop(BrokerFilter.java:157)
at
org.apache.activemq.broker.BrokerFilter.stop(BrokerFilter.java:157)
at
org.apache.activemq.broker.BrokerService$2.stop(BrokerService.java:15
41)
at
org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:41)
at
org.apache.activemq.broker.BrokerService.stop(BrokerService.java:491)
at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.stopBroker(JDBC
PersistenceAdapter.java:474)
at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.databaseLockKee
pAlive(JDBCPersistenceAdapter.java:466)
at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter$3.run(JDBCPersi
stenceAdapter.java:260)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:44
1)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java
:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$101(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
runPeriodic(ScheduledThreadPoolExecutor.java:181)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(ScheduledThreadPoolExecutor.java:205)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:907)
at java.lang.Thread.run(Thread.java:619)
ERROR BrokerService$2 - Could not stop service:
org.apache.active
mq.broker.BrokerService$2@273f4e. Reason: java.lang.InterruptedException
java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at
org.apache.activemq.thread.DedicatedTaskRunner.shutdown(DedicatedTask
Runner.java:72)
at
org.apache.activemq.thread.DedicatedTaskRunner.shutdown(DedicatedTask
Runner.java:83)
at org.apache.activemq.broker.region.Topic.stop(Topic.java:469)
at
org.apache.activemq.broker.region.AbstractRegion.stop(AbstractRegion.
java:109)
at
org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:41)
at
org.apache.activemq.broker.region.RegionBroker.doStop(RegionBroker.ja
va:627)
at
org.apache.activemq.broker.jmx.ManagedRegionBroker.doStop(ManagedRegi
onBroker.java:109)
at
org.apache.activemq.broker.region.RegionBroker.stop(RegionBroker.java
:187)
at
org.apache.activemq.broker.TransactionBroker.stop(TransactionBroker.j
ava:117)
at
org.apache.activemq.broker.BrokerFilter.stop(BrokerFilter.java:157)
at
org.apache.activemq.broker.BrokerFilter.stop(BrokerFilter.java:157)
at
org.apache.activemq.broker.BrokerService$2.stop(BrokerService.java:15
41)
at
org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:41)
at
org.apache.activemq.broker.BrokerService.stop(BrokerService.java:491)
at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.stopBroker(JDBC
PersistenceAdapter.java:474)
at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.databaseLockKee
pAlive(JDBCPersistenceAdapter.java:466)
at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter$3.run(JDBCPersi
stenceAdapter.java:260)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:44
1)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java
:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$101(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
runPeriodic(ScheduledThreadPoolExecutor.java:181)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(ScheduledThreadPoolExecutor.java:205)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:907)
at java.lang.Thread.run(Thread.java:619)
INFO BrokerService - ActiveMQ JMS Message Broker
(JayasSuperDu
perBroker1, ID:SE-JSRINIVA-DT1-1549-1213732885890-0:0) stopped
WARN JDBCPersistenceAdapter - Failed to stop broker
rajdavies wrote:
>
>
> On 16 Jun 2008, at 23:12, jaya_srini wrote:
>
>>
>> hi all
>>
>> I saw several posts regarding the async exception (listed below) in
>> logs
>> with ActiveMQ 5.0.0. We are also seeing this exception randomly in
>> the logs,
>> the bad part is it breaks the connection between Broker and the
>> client even
>> tho the broker is up and running and there are no network connection
>> issues
>> between the broker and the client.
>>
>> I got the impression from the other posts regarding this issue that
>> this has
>> been fixed in 5.1 release? Can someone confirm this? This is a
>> production
>> problem for us right now and would really appreciate if someone can
>> provide
>> a timely response. We are setting the
>> wireFormat.maxInactivityDuration=-1 to
>> in the connect url and are using durable subscribers.
>>
>> *WARN 13:50:24.571,ActiveMQ Transport:
>> ,(org.apache.activemq.ActiveMQConnection:1653)> Async exception
>> with no
>> exception listener: java.io.EOFException
>> java.io.EOFException
>> at java.io.DataInputStream.readInt(DataInputStream.java:375)
>> at
>> org
>> .apache
>> .activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
>> at
>> org
>> .apache
>> .activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:
>> 192)
>> at
>> org
>> .apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:
>> 184)
>> at
>> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:
>> 172)
>> at java.lang.Thread.run(Thread.java:619)
>>
>>
>> thanks!
>> jaya
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Async-exception-with-no-exception-listener%3A-java.io.EOFException-tp17874356p17874356.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
> This is fixed in 5.1
>
>
>
>
> cheers,
>
> Rob
>
> http://open.iona.com/products/enterprise-activemq
> http://rajdavies.blogspot.com/
>
>
>
>
>
>
--
View this message in context: http://www.nabble.com/Async-exception-with-no-exception-listener%3A-java.io.EOFException-tp17874356p17936119.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Async exception with no exception listener:
java.io.EOFException
Posted by jaya_srini <jy...@Hotmail.com>.
Thank You!
Is 5.1 backwards compatible with 5.0 configurattion? i.e if we get 5.1, we
shouldn't need to change any of our previous configuration we did with 5.0,
correct? (e.g. connect Url parameters, wireformat parameters etc)
rajdavies wrote:
>
>
> On 16 Jun 2008, at 23:12, jaya_srini wrote:
>
>>
>> hi all
>>
>> I saw several posts regarding the async exception (listed below) in
>> logs
>> with ActiveMQ 5.0.0. We are also seeing this exception randomly in
>> the logs,
>> the bad part is it breaks the connection between Broker and the
>> client even
>> tho the broker is up and running and there are no network connection
>> issues
>> between the broker and the client.
>>
>> I got the impression from the other posts regarding this issue that
>> this has
>> been fixed in 5.1 release? Can someone confirm this? This is a
>> production
>> problem for us right now and would really appreciate if someone can
>> provide
>> a timely response. We are setting the
>> wireFormat.maxInactivityDuration=-1 to
>> in the connect url and are using durable subscribers.
>>
>> *WARN 13:50:24.571,ActiveMQ Transport:
>> ,(org.apache.activemq.ActiveMQConnection:1653)> Async exception
>> with no
>> exception listener: java.io.EOFException
>> java.io.EOFException
>> at java.io.DataInputStream.readInt(DataInputStream.java:375)
>> at
>> org
>> .apache
>> .activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
>> at
>> org
>> .apache
>> .activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:
>> 192)
>> at
>> org
>> .apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:
>> 184)
>> at
>> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:
>> 172)
>> at java.lang.Thread.run(Thread.java:619)
>>
>>
>> thanks!
>> jaya
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Async-exception-with-no-exception-listener%3A-java.io.EOFException-tp17874356p17874356.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
> This is fixed in 5.1
>
>
>
>
> cheers,
>
> Rob
>
> http://open.iona.com/products/enterprise-activemq
> http://rajdavies.blogspot.com/
>
>
>
>
>
>
--
View this message in context: http://www.nabble.com/Async-exception-with-no-exception-listener%3A-java.io.EOFException-tp17874356p17915133.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Async exception with no exception listener: java.io.EOFException
Posted by Rob Davies <ra...@gmail.com>.
On 16 Jun 2008, at 23:12, jaya_srini wrote:
>
> hi all
>
> I saw several posts regarding the async exception (listed below) in
> logs
> with ActiveMQ 5.0.0. We are also seeing this exception randomly in
> the logs,
> the bad part is it breaks the connection between Broker and the
> client even
> tho the broker is up and running and there are no network connection
> issues
> between the broker and the client.
>
> I got the impression from the other posts regarding this issue that
> this has
> been fixed in 5.1 release? Can someone confirm this? This is a
> production
> problem for us right now and would really appreciate if someone can
> provide
> a timely response. We are setting the
> wireFormat.maxInactivityDuration=-1 to
> in the connect url and are using durable subscribers.
>
> *WARN 13:50:24.571,ActiveMQ Transport:
> ,(org.apache.activemq.ActiveMQConnection:1653)> Async exception
> with no
> exception listener: java.io.EOFException
> java.io.EOFException
> at java.io.DataInputStream.readInt(DataInputStream.java:375)
> at
> org
> .apache
> .activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
> at
> org
> .apache
> .activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:
> 192)
> at
> org
> .apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:
> 184)
> at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:
> 172)
> at java.lang.Thread.run(Thread.java:619)
>
>
> thanks!
> jaya
>
> --
> View this message in context: http://www.nabble.com/Async-exception-with-no-exception-listener%3A-java.io.EOFException-tp17874356p17874356.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
This is fixed in 5.1
cheers,
Rob
http://open.iona.com/products/enterprise-activemq
http://rajdavies.blogspot.com/