On 2/23/07, GaryG <[EMAIL PROTECTED]> wrote:
When you say "client" are you talking about the client connection should
automatically send keep-alive pings, or is this something our code has to do
manually?
Sorry I mean that the internals of the ActiveMQ JMS Client should do
the keep-alive stuff
if a JMS connection isn't doing much
>
--
View this message in context:
http://www.nabble.com/Non-Persistent-Topic-not-getting-messages-tf3264593s2354.html#a9122086
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
On 2/21/07, GaryG <[EMAIL PROTECTED]> wrote:
I have not looked at the JMX stats. For whatever reason, I haven't been able
to connect remotely to the broker.
Aside from that...Why would a broker kill clients due to inactivity?
Some OSes/platforms don't detect a socket death for hours or days;
to your situation. Anyway, you may want to look into the
> usageManager settings in the broker configuration to set the limit
> higher. A 20MiB default seems weird. I didn't think that there was a
> default.
>
> --
> Christopher G. Stach II
>
>
>
--
View this
GaryG wrote:
> AMQ Broker is down again. Same situation. However, running "jstack" on the
> PID doesn't work, it hangs connecting to the process.
>
> So, I opened up the JMX console, and am providing you some of stats that
> looked interesting.
>
> My main questions regarding this output are:
>
AMQ was started with 512MB.
The memory % used says 100%.
But this doesn't match the Summary Memory stats. What is this limit?
--
View this message in context:
http://www.nabble.com/Non-Persistent-Topic-not-getting-messages-tf3264593s2354.html#a9093767
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
_Gary
Christopher G. Stach II wrote:
>
>
> We currently have some issues where queues stop delivering. Can you
> generate a stack dump when it's hung?
>
> --
> Christopher G. Stach II
>
>
>
--
View this message in context:
http://www.nabble.com/Non-P
GaryG wrote:
> I've got the JMX running. Again the architecture ran fine for about 3 hours,
> then all my topics seemed to stop receiving messages.
>
> So, here's the situation:
>
> 1) the producers ARE sending messages and there are no exception from AMQ
> API when they're sent.
> 2) AMQ Brok
>>> The only difference I can see is that this particular topic is getting
>>> ObjectMessage(s), while I've switched the others to "MapMessage(s)".
>>>
>>> Is there an issue with sending across a large number of ObjectMessage(s)
>>> ??
>>&
gt; ObjectMessage(s), while I've switched the others to "MapMessage(s)".
>>
>> Is there an issue with sending across a large number of ObjectMessage(s)
>> ??
>> It seems that whenever I've used that, after a while messages stop coming
>> through. This has h
d the others to "MapMessage(s)".
Is there an issue with sending across a large number of ObjectMessage(s) ??
It seems that whenever I've used that, after a while messages stop coming
through. This has happened a number of times now.
Thanks,
Gary
--
View this message in conte
f times now.
Thanks,
Gary
--
View this message in context:
http://www.nabble.com/Non-Persistent-Topic-not-getting-messages-tf3264593s2354.html#a9074729
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
12 matches
Mail list logo