Do you have some simple test case that we could use to reproduce the problem ? You can also take a look at the statistics that are available via jmx to check if you can see a component that would cause the problem. For example, if a component does not poll its delivery queue (or does not implement the MessageExchangeListener), the queue may be fulled and the component will not be able to process more messages.
Cheers, Guillaume Nodet On 4/24/06, Gerdes, Mike <[EMAIL PROTECTED]> wrote: > > btw this happens only when I use a topic and not a queue and only when I send > the messages in a high frequency. > > -----Ursprüngliche Nachricht----- > Von: Gerdes, Mike > Gesendet: Freitag, 21. April 2006 16:11 > An: [email protected] > Betreff: memory problem > > > > > hi, > > I am not sure if I have run into a problem or if it is just an error on my > side. So here is what I have encountered: > > I have an application that sends as fast as possible JMS messages of 1kb into > the JMS-binding exsample, the rate is about 1000 messages per second. When I > reach about 8000 messages servicemix and I guess also activemq shuts down. > the debug says that the memory is full at 100%. > > DEBUG - UsageManager.fireEvent(207) | Memory usage change. from: 99, to: 100 > > From these 8000 messages are only about 100 processed by servicemix, the rest > are in the queue. > With AMQ and no processing from SM everything works perfectly. So I guess it > is some kind of a problem on SM side. > > Is there still hope for me? > > cya > > mike > > > This mail has originated outside your organization, either from an external > partner or the Global Internet. Keep this in mind if you answer this message. > > > > This mail has originated outside your organization, > either from an external partner or the Global Internet. > Keep this in mind if you answer this message. > > This mail has originated outside your organization, either from an external > partner or the Global Internet. Keep this in mind if you answer this message. >
