Re: Why webconsole starts a message broker?

Hi, take a look at this link http://activemq.apache.org/web-console.html#WebConsole-StartingtheWebConsoleinaseperateVM%2FinaWebContainer it describes how to do it. Regards -- Dejan Bosanac Senior Software Engineer | FuseSource Corp. dej...@fusesource.com | fusesource.com skype: dejan.bosanac |

Re: custom plugin

I found there was an related issue back in 2010 about schema validation: https://issues.apache.org/jira/browse/AMQ-2939 The comment by Gary Tully can relieve the problem: ./bin/activemq xbean:conf/activemq.xml?validate=false Is there a better way to solve it ? Thanks. Luoh Ren-Shan -- View

Re: custom plugin

Hi, I'm following the instructions in http://activemq.apache.org/interceptors.html to write a very minimal plugin. My plugin class can be successfully loaded by However, if I tell the broker to load it as a plugin http://activemq.apache.org/schema/core"; brokerName="localhost" dataDirecto

Why webconsole starts a message broker?

Hi, I have a JBooss 5.1 with an integrated ActiveMQ. When I deployed the ActiveMQ webconsole I noticed that the webconsole starts another message broker. Is it possible to tell the webconsole to use the original message broker? I'd like to monitor the messages in the original broker so I do not n

Re: Can activeMQ be configured to state only one consumer per queue?

see: http://activemq.apache.org/exclusive-consumer.html On 17 April 2012 13:07, archa wrote: > Can activeMQ be configured to state only one consumer per queue? > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Can-activeMQ-be-configured-to-state-only-one-consumer-per

Re: Producer blocks when trying to send async JMS messages to failed broker

Or for this case (where messages with age > 2 secs can be discarded), couldn't you have a variant... ignore the network connector status, and allow messages to be expired after 2000 milliseconds via setTimetoLive on the producer. - Michael Hayes B.Sc. (NUI), M.Sc. (DCU), SCSA SCNA -- View

Re: Producer blocks when trying to send async JMS messages to failed broker

yes, if the failure to connect/reconnect bubbles up to the application, it will need to initiate a new connection. fire and forget in jms terms is still mediated by the broker, and finding a broker is currently a synchronous operation. A jms connection that ignores the fact that it does not have a

Re: Producer blocks when trying to send async JMS messages to failed broker

Thanks Gary. I am still not completely sure I get it. I am using failover because I *do* want my client to reconnect when the broker comes back up. However, when it's down I don't want to queue messages or block anything - they can be thrown away. My messages really are 'fire and forget'. These

Re: Producer blocks when trying to send async JMS messages to failed broker

configure the failover maxReconnectAttempts and the failure to connect will bubble up to the application where you can ignore it. The assumption of failover is that you want to 'transparently' maintain the connection and block pending reconnect failover:(...)? maxReconnectAttempts=1 http://active

Re: Can we connect multiple connection for the same destination ?

I /think /that if you draw the picture for what you have described, you will see that you are trying to share a JMS Connection *CX *between your producing process (JMS client) *SSX *and a different consuming process *SRX *(a different JMS Client). Process SS1 cannot have the the same JMS Connectio

Re: Activemq IPV6 Client Connection (Java and C++)

can you post the failover uri from the java case and the exception? On 16 April 2012 16:33, Oscar Pernas wrote: > Hi all, > > Im trying to use ActiveMQ with IPV6 but Im running into some problems. I'm > in debian linux, and seems that ActiveMQ(5.5.1) is up and listening IPV6. > >    tcp6   0   0