On Fri, Jul 17, 2009 at 5:53 PM, tide08 wrote:
>
> I have activemq configured to run with spring in embedded mode. I also have
> also added journaling and oracle persistence but activemq still keeps on
> looking for derby somehow?
>
> dataDirectory="${scheduling.jms.datadirectory}">
>
>
On 20 Jul 2009, at 18:00, Eric Gearhart wrote:
Wow that subject line was a mouthful!
OK back to the question... we are trying to setup a highly available
ActiveMQ implementation. Reading over what I've read on ActiveMQ's
website, I think I can accomplish this best using a shared filesystem
app
Setting the element's 'deleteAllMessagesOnStartup' attribute to true
will force the broker to delete all queues and messages on startup.
http://activemq.apache.org/schema/core"; brokerName="broker0"
deleteAllMessagesOnStartup="true">
Joe
http://www.ttmsolutions.com
nmt999 wrote:
>
> Active
ActiveMQ when started creates all the old queues that was used for testing
purpose. How can I prevent it from creating those queues? The queues are
created from the java application.
nmt
--
View this message in context:
http://www.nabble.com/prevting-unnecessary-queues-from-being-created-tp2457
Wow that subject line was a mouthful!
OK back to the question... we are trying to setup a highly available
ActiveMQ implementation. Reading over what I've read on ActiveMQ's
website, I think I can accomplish this best using a shared filesystem
approach.
We have a pair of Windows SQL servers that
I have checked again and all of my configuration seems to be fine.
Does anyone have any suggestions? Please help.
Thanks!
tide08 wrote:
>
> I have activemq configured to run with spring in embedded mode. I also
> have also added journaling and oracle persistence but activemq still keeps
> on
Thanks Gary. It totally makes sense. However, I am exactly using pooled
connection factory for producer and message listener container with a
regular connection factory for consumer. I am sorry that I didn't state
clearly in my previous thread. What might cause pending messages unable to
consume u
Thanks. Will try.
More detail about the client is that when we send a queue request, we do
- create a Session
- create a TemporaryQueue
I wonder if these two will be broadcasting something to the other clients
and cause the backlog. Shouldn't be, but...
rajdavies wrote:
>
> Does this behavi
consuming messages from a connection pool can be problematic due to
prefetch[1]. Unconsumed prefetched messages are only returned when the
connection is closed, but with a pooled connection the connection
close is deferred (for reuse) till the pool closes. This leaves
prefetched messages unconsumed