, there
are some other small changes.
Best Regards
dolphin_cheng
Andy Wu wrote:
>
> Did that happen regardless of how you started up activemq? Can you provide
> any more details about the changes you made?
>
> Thanks
> Andy
>
>
>
> dolphin_cheng wrote:
>>
opped
>>> 2008-07-10 20:06:11,173 [MQ ShutdownHook] INFO TransportConnector
>>> - Connector ssl Stopped
>>> 2008-07-10 20:06:13,173 [MQ ShutdownHook] INFO TransportConnector
>>> - Connector stomp Stopped
>>> 2008-07-10 20:06:13,797 [MQ Shutdown
try 5.1 instead ?
>
> On 11 Jun 2008, at 12:35, dolphin_cheng wrote:
>
>>
>> Yes, there is nothing in the logs from Activemq to indicate why it
>> failed.
>> In the logs from our project there is only exception "Could not
>> co
t;
> On 11 Jun 2008, at 08:02, dolphin_cheng wrote:
>
>>
>> We use activemq 5.1.0 and deploy it in a linux system. Several
>> days ago, I
>> asked a question that EOFException can lead to broker shut down. But
>> I found
>> that even there is no EOF
We use activemq 5.1.0 and deploy it in a linux system. Several days ago, I
asked a question that EOFException can lead to broker shut down. But I found
that even there is no EOFException the broker can shut down too. We are
waiting for the solution vexedly, please help us ^_^
Thanks very mu
We use activemq 5.1.0 and deploy it in a linux system. But the broker is dead
every one hour. It is not steady especially. I found the EOFException in the
client as follow:
javax.jms.JMSException: java.io.EOFException
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSuppo
