Could you raise a JIRA for this - its sounding like the cache eviction
for durable topics is not kicking in and things are blocking on the
amount of RAM in the <usageManager/>
On 7/25/06, Christopher Mihaly <[EMAIL PROTECTED]> wrote:
There are no non-durable consumers. It is a pretty simple test, I created
a durable subscriber that subscribed for messages on the topic. Then I shut
down that consumer and wrote a publisher that wrote persistent messages, up
to 100,000 of them. It will have after about 1800 messages every time. If
I then run my druable consumer, it will read the messages off the queue and
I can send another few messages before it hangs.
If I leave the durable subscriber inactive for a while, it will go OFF-LINE
and sometimes I am unable to get it to back on-lne ever. But that is a
different message thread.
Chris
James.Strachan wrote:
>
> Do you have any slow consumers (non-durable consumers) who are not keeping
> up?
>
> On 7/24/06, Christopher Mihaly <[EMAIL PROTECTED]> wrote:
>>
>>
>> James.Strachan wrote:
>> >
>> > Are you sending the messages with persistent message delivery mode?
>> > private int deliveryMode = javax.jms.DeliveryMode.PERSISTENT;
>> > private int deliveryPriority = javax.jms.Message.DEFAULT_PRIORITY;
>> > publisher.send(msg, deliveryMode, deliveryPriority,
>> > Message.DEFAULT_TIME_TO_LIVE);
>> > Also what version are you using?
>> >
>> > Version Version 4.0.1
>> >
>> > On 7/24/06, Christopher Mihaly <[EMAIL PROTECTED]> wrote:
>> >>
>> >> On the test case, I created a topic publisher and create 100000
>> >> messages
>> >> using asyncsend. This works great. Then I make a durable
>> subscription
>> >> and
>> >> that client exits leaving his durable subsription. Then I send the
>> >> publisher and around 2000 messages it will hang. The only solution
>> to
>> >> this is to run my client that subscribed to the subscription and read
>> the
>> >> thousands of messages. Then I can send another couple thousand
>> >> messages,
>> >> etc. It is completely repeatable. This happens if I am using
>> >> journaling
>> >> or not, or out of the box, derby or MS SQLServer as the persistenace
>> DB.
>> >> I believe this is what is happening on our production server. We
>> have
>> >> clients that are run weekly, or at other unspecified times that will
>> hold
>> >> durable subscriptions to the topics. I have not found any way around
>> >> this
>> >> other than killing off subscriptions (sometimes not possible since you
>> >> cannot destroy a subsription that is off-line, not sure why they are
>> >> off-line, but I guess over time they become off-line). So the only
>> >> solutoins is to destroy the topic and recreate, but this destroys a
>> lot
>> >> of
>> >> data for us and is getting unusable :_(
>> >>
>> >> Chris
>> >>
>> >>
>> >> Chris
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/activemq-clients-all-hang-tf1950608.html#a5461880
>> >> Sent from the ActiveMQ - User forum at Nabble.com.
>> >>
>> >>
>> >
>> >
>> > --
>> >
>> > James
>> > -------
>> > http://radio.weblogs.com/0112098/
>> >
>> >
>> --
>> View this message in context:
>> http://www.nabble.com/activemq-clients-all-hang-tf1950608.html#a5469193
>> Sent from the ActiveMQ - User forum at Nabble.com.
>>
>>
>
>
> --
>
> James
> -------
> http://radio.weblogs.com/0112098/
>
>
--
View this message in context:
http://www.nabble.com/activemq-clients-all-hang-tf1950608.html#a5480407
Sent from the ActiveMQ - User forum at Nabble.com.
--
James
-------
http://radio.weblogs.com/0112098/
