Re: Issues with Network of Brokers and Message Selectors

Elliot, This looks very similar to an issue fixed a couple of months ago. Check out: http://fusesource.com/issues/browse/MB-438 or alternatively for AMQ: https://issues.apache.org/activemq/browse/AMQ-2104 HTH, -Giovani On Wed, Apr 29, 2009 at 1:21 PM, Elliot Barlas wrote: > > I have been experi

Problem discovering broken with using non-jmdns client

Cutting to the chase, I need to be able to discover brokers by non-java means. Here are the details: I have activeMQ set up to use rendezvous using the following configuration: discoveryUri="rendezvous://test"/> The DiscoveryAgent starts up fine and can be discovered using the

Re: VMTransportServer already bound

After peeking a while in the sources of ActiveMQ I discovered the trick by myself: actually it's not ActiveMQ the problem, but the java.net.URI class, which in a string like this: vm://A_NODE_NAME?create=false&waitForStart=1 considers "A_NODE_NAME" a malformed host name and sets its corre

Issues with Network of Brokers and Message Selectors

I have been experimenting with the behavior of a network of two AMQ brokers and message selecting consumers. As described in the AMQ documentation (http://activemq.apache.org/networks-of-brokers.html), consuming with message selectors in a broker network environment can lead to messages being tra

Configuration of maximum number of Producers

Hi, I'm looking for a policyEntry attribute which allows to limit the number of Producers per Topic/Queue. Same for the maximim size of a single message. I'm not sure if the PolicyEntry.maxProducerToAudit which is referenced by AbstractPendingMessageCursor.java is the right thing. I tried it with

VMTransportServer already bound

I am trying to embed an ActiveMQ broker inside an application that is exposing services via JMS. The intent is to create a cluster of brokers so that: - each instance of the application has its own broker via VM transport; - each instance exposes a TCP transport to clients; - each instance is a no

Re: Segmentation fault while sending bytes messages

On Mon, 2009-04-27 at 09:44 -0700, manua wrote: > Hi Tim, > > In continuation to my previous mail, I tried with increasing the array size > at the producer end, but still getting the same error. > > Also, my producer is running till end, its the consumer which fails. The > same consumer never fai

Re: Libraries to include while compiling my activemq-cpp code

On Wed, 2009-04-29 at 04:47 -0700, nmittal wrote: > > > Timothy Bish wrote: > > > > On Tue, 2009-04-28 at 08:35 -0700, nmittal wrote: > >> > >> > >> Timothy Bish wrote: > >> > > >> > > >> > It still appears if your environment is working against you. You need > >> > to spend some time figur

Re: Libraries to include while compiling my activemq-cpp code

Timothy Bish wrote: > > On Tue, 2009-04-28 at 08:35 -0700, nmittal wrote: >> >> >> Timothy Bish wrote: >> > >> > >> > It still appears if your environment is working against you. You need >> > to spend some time figuring out what is installed and where. >> > >> >> /usr/bin/ld: skipping in

Re: Reconnect of the durable consumers after ActiveMQ restart/fail

I guess i'll try using two different URIs producers One with maxReconnectAttempts=2 - this will not block my producer consumers one with default value of maxRecconecetAttempts - which is -1 cuz i want my consumers to keep trying reconnect forever - since they don't block anyone. Thank you for yo

Re: Reconnect of the durable consumers after ActiveMQ restart/fail

Hi, I have a similar config. I think the problem is because you have maxReconnectAttempts parameter set to 2. When the connection reaches max attempts it does not try to connect again, which is logicall. If you want to revive your consumers you will have to reinstall them. At least is what I

Re: Reconnect of the durable consumers after ActiveMQ restart/fail

So , am I doing something wrong and nobody has this problem or it might be that nobody noticed it yet :) agatone wrote: > > Hi, > > I have this setup where I set few durable consumers (setMessageListener) > and they succesfully register on ActiveMQ. But as soon as the ActiveMQ > shutdowns (by

Re: Journal files. Memory management and cursors

the fileQueueCursor should work well for you but the error with the journal looks like an issue that requires a jira entry. It should be better able to deal with wrap around. If you have time to produce a simple test case that demonstrates this usage pattern and attach it to a new jira, it would be

Re: Journal files. Memory management and cursors

Hi all, I have done some more test and now seems to me that the problem has nothing to do with journal files but with journal files in cursor storage. My previous thoughts were wrong as messages are committed into the database every 5 minutes or as soon as the cursor memory reaches 70%

Re: Queue message order

Hi Roger, I seethanks for answering. Best regards Andreas On Apr 29, 2009, at 8:31 AM, Roger Hoover wrote: Hi Andreas, That's an insightful question and there is a good answer, albeit complicated. The test is trying to validate the exception handling logic in our STOMP client. To pre