That is because XML has some 'special characters' that need encoding; see
http://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references
On 21 December 2011 12:37, liny wrote:
> Hi, Gary:
>
> Thanks for reply.
> I changed to
>
> Yes, I must use "&" to replace "&", can't just use "&
Hi, Gary:
Thanks for reply.
I changed to
Yes, I must use "&" to replace "&", can't just use "&" in your broker
URL.
That's very strange!
--
View this message in context:
http://activemq.2283324.n4.nabble.com/failover-invalid-connect-parameters-tp3923668p4221517.html
Sent from the ActiveMQ - Us
have a look through some of the usage in the tests. I gave google code
search a whirl to pull them out, the result is reasonable:
http://www.google.com/codesearch#search/&q=%22failover%22%20lang:%5Ejava$%20license:%5Eapache$%20activemq&type=cs
On 21 December 2011 09:58, liny wrote:
> Hi,
>
> I do
Hi,
I don't understand why below two broker URLs don't work:
I still get
Any help is appreciated
--
View this message in context:
http://activemq.2283324.n4.nabble.com/failover-invalid-connect-parameters-tp3923668p4221073.html
Sent from the ActiveMQ - User mailing list archive at Nabble
I think you can also replace tcp.keepAlive=true with transport.keepAlive.
--Claudio
>
>From: qt4x11
>To: users@activemq.apache.org
>Sent: Friday, October 21, 2011 12:42 PM
>Subject: Re: failover invalid connect parameters
>
>Worked lik
Worked like a charm! Thank you!
On Thu, Oct 20, 2011 at 5:54 PM, Timothy Bish wrote:
> On Thu, 2011-10-20 at 17:34 -0500, qt4x11 wrote:
> > We are trying to instantiate a new ActiveMQConnectionFactory in our code
> > using the brokerURL
> >
> > failover:(ssl://107.22.0.25:61616,ssl://174.129.78
On Thu, 2011-10-20 at 17:34 -0500, qt4x11 wrote:
> We are trying to instantiate a new ActiveMQConnectionFactory in our code
> using the brokerURL
>
> failover:(ssl://107.22.0.25:61616,ssl://174.129.78.76:61616
> )?tcp.keepAlive=true
>
Try this:
failover:(ssl://107.22.0.25:61616?keepAlive=true,s
