Re: ActiveMQ JMS Bridge to Websphere MQ

On Sep 24, 2007, at 2:29 PM, thaibox1 wrote: Does anyone require anything more from me to help diagnose this issue? Thanks... Well, this is just a stab in the dark here, but one thing that looks a bit funny to me is that your ActiveMQ server is named ALERTQ, yet the error message you are

Virtual Topic not working as expected - defect, or misunderstanding?

The following test produces unexpected results: 1) Start a broker with a statically defined destination topic called VirtualTopic.FOO 2) Start a consumer listening to Consumer.A.VirtualTopic.FOO 3) Start a sender and send N messages to VirtualTopic.FOO 4) Consumer correctly receives N messages. 5

Compression

I am using AMQ 5.0 SNAPSHOT I am testing compression with Text messages and have set jms.useCompression=true in my producer's brokerURL. tcp://localhost:61616?jms.useCompression=true ...and ((ActiveMQConnection)conn).isUseCompression() always returns 'true' However, when I turn on debug on

Re: ActiveMQ JMS Bridge to Websphere MQ

Does anyone require anything more from me to help diagnose this issue? Thanks... thaibox1 wrote: > > I'm using MQ series 5.2 (I know it's old, but it's supposedly JMS > compliant). We're looking to move off Websphere MQ and I'm evaluating > ActiveMQ, but we're still going to need to hook it

Failed to send to dead letter queue?

Hello all I'm trying to use third party software (GridGain) with ActiveMQ 5.0-SNAPSHOT (built from trunk a few minutes ago). Each time GridGain sends a "discovery" message to a topic, the broker prints the following message: WARN RegionBroker - Failed to send ActiveMQObje

Daemon process manager

We're planning to use ActiveMQ as an asynchronous messaging layer between daemon processes written in various languages (connecting to ActiveMQ via STOMP). We need a convenient way to launch, shutdown, or restart the daemons and supervise them (restart them if they die). We also want to start mul

Re: VM Transport problem when closing connections

Since you're connecting to an embedded broker, there is no need to use the 'failover' transport. Are you reusing Connection objects? zouzounos wrote: > > Hi, > I'm using activemq4.1.1 under tomcat 6. I am using the next entry in the > Context.xml: > type="org.apache.activemq.ActiveMQConnect

Re: VM Transport problem when closing connections

Hi, Are you using Spring? Can you use an org.apache.activemq.xbean.BrokerFactoryBean? This will create and start the broker and just leave it there in the VM. You can create a connection and then close it as you want but it will not shutdown the broker. (Broker stays alive until VM dies or until

ActiveMQ 4.0.2 errors with firewall between client and broker

Hi, we have tested ActiveMQ 4.0.2 for a long time on a network without firewall between clients and broker. Switching to DMZ with firewalls we stumbled across problems with activemq connections. It appears that whenever firewall closes connection, activemq doesn't, which eventually leads to OutOfM

VM Transport problem when closing connections

Hi, I'm using activemq4.1.1 under tomcat 6. I am using the next entry in the Context.xml: As the d=ocumentation says, the broker is created upon creation of a connection The problem that i face is that after releasing the connection using Connection.close() (and if no other connection is still