ssl client connectivity and the keystore with needClientAuth on the broker

Hi there, I'm having great difficulty in get SSL connectivity working with client certificate verification (needClientAuth = true on the broker's ssl transport). I think that I have my certificates all set up correctly. I see the broker asking the client for its certificate via Wireshark. I not

Re: Failover in 5.2.0

The Failover transport layers reconnect logic on top of any of the other transports. On NIO, that is typically a broker side option, so the broker will use tcp using NIO on its transportConnector or listener. A client will still use the the regular tcp stack. 2009/3/13 Ryan Moquin > That would b

Re: Failover in 5.2.0

That would be fine.. I just want to reestablish the connection if it gets dropped (it seems like there are constant network hiccups that cause my connection to get lost). I don't want to lose the connection from innactivity either though. Will it still block if I use the NIO transport? Or can I n

Re: Failover in 5.2.0

If you are in the same VM, then use the vm:scheme as this will be a lot faster as there is no marshaling overhead. I guess it is worth investigating what is causing your connections to get dropped. Is it inactivity timeout or netwo

Re: Failover in 5.2.0

Ahh ok.. that explains a lot... Too bad I didn't ask this question a lot sooner since I've been very confused over the last week on why updates seemed to stop unexpectedly when they never used to. On the same note, should I use failover even for interVM connections? Such as my servicemix serv

Re: Failover in 5.2.0

you still need to use the failover: scheme in 5.2 when you provide a url and want failover. The change only effects users who do not provide a brokerUrl to the ActiveMQConnectionFactory. That is the only case where the defaultUrl is used. 2009/3/13 Ryan Moquin > I've been using ActivbeMQ 5.2 for

Failover in 5.2.0

I've been using ActivbeMQ 5.2 for a while now and am having a problem where my topic subscribers seem to lose their connections to the ActiveMQ broker after around 1,000 messages (it seems like they consistently lose their connection at just over 1,000 messages). My publishers (SOA services in Ser

Re: ActiveMQMessageConsumer not releasing packages

yes. I have also tried CLIENT_ACKNOWLEDGE and called message.acknowledge in the onMessage() method and observed the same results. On Fri, Mar 13, 2009 at 7:03 AM, Gary Tully wrote: > is the consumer using auto acknowledge? > > 2009/3/12 Mark Webb > >> I have been debugging a memory issue I am

Re: ActiveMQMessageConsumer not releasing packages

is the consumer using auto acknowledge? 2009/3/12 Mark Webb > I have been debugging a memory issue I am having with a client that > uses ActiveMQ 5.2 libraries. This program has sends and receives > messages on 2 topics, and also has implemented the Request/Response > algorithm found in > > > h

How post message to a queue which is an a remote broker

I use jndi.properties to describe jndi queue and physical queue. When I describe a local queue I have no problem. But I search in the documentation of jndi.properties how describe the physical queue of an another broker. I try this configuration but it doesn't work My local broker has the name

Wire format negotiation timeout: peer did not send his wire format

Hi, We are using ActiveMQ 5.1 (with Spring JMSTemplate) and have faced this problem for the first time and are unable to find the reason for this issue. Let me relate the scenario first. We have two applications running which interact with each other to send and receive messages. The first