On 09/01/2008, qwidjibo <[EMAIL PROTECTED]> wrote:
>
>
> Hi All.
>
> I'd like to have many (potentially hundreds or more) message listeners in
> the same VM listening to different queues.
>
> The problem is that I'd like a number of those to be listening at different
> priorities. Looking at the JM
For AMQ5.0.0, I configured the AMQPersistenceAdapter like this:
However when running a Slave broker with this config, I get the following
exception on Slave broker (see below).
Apparently the locking fails as it should, but should'nt the Slave Broker
wait in a loop to retry
I tried the amq store as well, with this configuration:
but on repeating the test, I see immediate (in about a second or two) errors
in the AMQ log (see below).
My sending client goes to completion. But the receiver does not receive any
messages after the error occurs.
Is my configuration a
You can create a queue browser and view the messages without acknowleding
them.
I believe there is a sample of creating a browser with the source for the
project.
-- The grass may be greener, but I'm looking for a maintenance free lawn.
Peter V Kasson
"teo.danciu" <[EMAIL PROTECTED]>
01/0
On 09/01/2008, teo.danciu <[EMAIL PROTECTED]> wrote:
>
> Hi, is there any way in which I can see the messages from a queue at any
> moment? (I'm having trouble with an application and I just can't follow what
> happens with the queue).
Yes...
http://activemq.apache.org/how-can-i-monitor-activemq.h
Hi, is there any way in which I can see the messages from a queue at any
moment? (I'm having trouble with an application and I just can't follow what
happens with the queue).
Thanks
--
View this message in context:
http://www.nabble.com/View-messages-from-a-queue-tp14720928s2354p14720928.htm
that's certainly an option. however, i'm sure that my company will have some
reluctance to rush to production on a *.0 release. this is a rather
critical application with human safety implications so decisions to adopt
new versions are conservative.
rajdavies wrote:
>
> you don't want to use
On 09/01/2008, Mario Siegenthaler <[EMAIL PROTECTED]> wrote:
> We're running an ActiveMQ-based messaging infrastructure with multiple
> applications communicating over it. Everything is running fine, but we
> want to implement an 'alert'-system in case something goes wrong. I'm
> not talking about
you don't want to use activemq 5.0 ?
On Jan 8, 2008, at 6:34 PM, gfrank wrote:
Is there a schedule on this?
I'm interested because there are some critical fixes since 4.1.1
related to
master/slave and JDBC message store. My company is reluctant to go to
production with a locally compiled bi
please use the default store for activemq 5.0 - amqstore. It
supersedes the kaha store originally using kaha. The difference is
that we've integrated the journal with kaha - and this is the main
store we test on.
cheers,
Rob
Rob Davies
'Go further faster with Apache Camel!'
http://rajdav
We're running an ActiveMQ-based messaging infrastructure with multiple
applications communicating over it. Everything is running fine, but we
want to implement an 'alert'-system in case something goes wrong. I'm
not talking about a broker failure here (that is already monitored),
but of application
awesome! thanks Trevor!
On Jan 8, 2008, at 8:55 PM, tpounds wrote:
I've created a JIRA issue and a patch at the following link for the
networkTTL problem. This problem actually affects more than just the
networkTTL parameter as mentioned in the ticket. See that for more
info.
see: https:
Setting prefetch to 1 on the connection in either ways does not seem to
work; It seems like the server reads every message into memory anyway, and
the server fails. (I tried this with the example queue consumer / producer,
setting the message to 600k and produce 500 messages, and then try to
cons
13 matches
Mail list logo