geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <>
Subject [jira] Commented: (GERONIMO-3783) MessageDrivenBean delivery problem
Date Wed, 30 Jan 2008 16:40:33 GMT


Jarek Gawor commented on GERONIMO-3783:

I've been debugging this issue a little and I'm getting lost in the activemq code since I'm
not familiar with it. 

What I see is that sometimes the messages get dispatched right away and sometimes they get
queued. Once there are messages in the queue , the new incoming messages will be queued (which
makes sense). However, the messages in the queue are never dispatched until the mdb is restarted.
There is a method to process the queued messages but it appears not to be called. That's where
I'm getting lost. I'm not sure when or what should be calling this method. Btw, the decision
to queue or dispatch right away happens in PrefetchSubscription.add(MessageReference) function.

Increasing the prefetchSize value (or how it is known as 'maxMessagesPerSessions' in the activation
spec) helps but does not completely remove the problem. 

> MessageDrivenBean delivery problem
> ----------------------------------
>                 Key: GERONIMO-3783
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: ActiveMQ
>    Affects Versions: 2.1
>         Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot
>            Reporter: Tomasz Mazan
>            Priority: Critical
>         Attachments:
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then
stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message