ActiveMQ connections hangs sometimes when calling start on a connection

Any ideas why every now and then, when my code creates a connection and calls start on that connection, the call never returns. Here is a dump of the thread that is hanging... State: WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@365f10e6 Total blocked: 1,312 T

Session.SESSION_TRANSACTED in example code wrong??

I'm looking at the Vendor.java sample that comes with ActiveMQ. It does... connection.createSession(true, Session.SESSION_TRANSACTED); Reading the docs... http://download.oracle.com/javaee/1.4/api/javax/jms/Connection.html#createSession%28boolean,%20int%29 that isn't a valid value for create ses

Re: Selectors and QueueBrowser

Gary Tully wrote: > > You can experience a hung queue scenario if there are more > than maxPageSize messags in a queue that do not match a selector. > Gulp! While I have only 4 messages in my current test, potential I could have 10,000s of messages and my selector will be used to pick out a

Re: Selectors and QueueBrowser

//activemq.apache.org/maven/5.3-SNAPSHOT/activemq-core/testapidocs/org/apache/activemq/JmsQueueBrowserTest.html > [3] http://activemq.apache.org/per-destination-policies.html > > 2009/1/16 IBeaumont : >> >> ActiveMQ 5.2 >> >> Has anyone used a QueueBrowser with selec

Selectors and QueueBrowser

ActiveMQ 5.2 Has anyone used a QueueBrowser with selectors? I know my message properties are set correctly as they are displayed in the tooltip in the ActiveMQ web administrator when I browse the queue. However they don't return any messages when I try to query the items on the queue from code.

Re: Problem with Selector

Sorry about opening up an old thread, by I've got all the same fustrations as Jecsiac with this issue. How can I write a deterministic system to return a message if it exists on a queue, or null if it doesn't exist. How long should I wait, a second, a minute, an hour? What if I have a million m

Re: Q Consumers stop receiving messages

ideal solution as I'd need to change a lot of other code. I'm trying to avoid any changes. bsnyder wrote: > > On Tue, Jan 13, 2009 at 12:35 PM, IBeaumont > wrote: >> >> I'm sending a mixture of persistent and non persistent messages. >> >> I have s

Re: Q Consumers stop receiving messages

depende on > redelivered(). tThat is a known issue, prefetched messages that are > not consumed are deemed redelivered when they are dispatched to the > next consumer. > ActiveMQ redelivered means delivered to a amq consumer, not delivered > to the end user. see: > https://issues.a

Re: Q Consumers stop receiving messages

rs are blocking > when trying to "stick messages" back on a queue? > > Out of interest, why are you using prefetch==0? > > 2009/1/13 IBeaumont : >> >> I've got a fairly complex app, that takes msgs, processing them and >> sticks >> them on the s

Re: Q Consumers stop receiving messages

James.Strachan wrote: > > Which version? > ActiveMQ 5.2 I've also found that restarting the broker doesn't seem to make any difference. The consumes are still stuck on the same call, which makes me think the problem is with the consumers. -- View this message in context: http://www.nabble

Q Consumers stop receiving messages

I've got a fairly complex app, that takes msgs, processing them and sticks them on the same or different queues. The queues are pre-loaded with persistent messages before the application starts (5). Once it starts processing things work fine for a while and then the consumers stop receiving

Re: Client threads hang if ActiveMQ dies

me another problem). I found this setting though "soTimeout" - which can be set for the socket timeout and defaults to 0. So I changed this to 1 (10 secs) and everything now behaves a lot better. bsnyder wrote: > > On Thu, Jan 8, 2009 at 8:51 AM, IBeaumont wrote: &

Client threads hang if ActiveMQ dies

I'm running ActiveMQ on another machine and connecting via TCP. If it dies (I press CTRL-C, or may get an out of memory error) while I'm processing messages then the consume gets stuck waiting for a message and never returns (I'm calling receiveNoWait). This is the stack trace where it is stuck

OutOfMemoryError - with large number of msgs in a transaction

I'm trying to post a few thousand messages in one tranactions. It seems that my heap space needs to be big enough to hold all messages from the one transaction in memory in one time to successfully commit. Is this correct? I would expect it to start spooling the messages to the message store as

Blocking on waitForSpace, configuring a timeout??

I send a large amount of messages in one transation that the queues aren't configured big enough to handle. ActiveMQ sits and waits in "MemoryUsage.waitForSpace" forever and the whole system appears hung (monitoring through jconsole). The space needed will never become available and I need the s