(final JMSException e) {
> > > >> e.printStackTrace();
> > > >> }
> > > >> }
> > > >> }
> > > >
> > > > This is an inefficient way of using JMS BTW...
> > > >
>
ent way of using JMS BTW...
> > >
> > > http://activemq.apache.org/how-do-i-use-jms-efficiently.html
> > >
> > > you should try pool producers if you can.
> > >
> > >
> > >> >"You night wanna enable failover...&qu
jms-efficiently.html
> >
> > you should try pool producers if you can.
> >
> >
> >> >"You night wanna enable failover...":
> >> We have only been assigned one port for the broker (specified obviously
> >> as
> >> part of the brok
er causes the client to reconnect to the broker if the socket dies.
>
>
>> my
>> understanding of failover is that you need more than one URI and AMQ
>> switches to another one if one broker goes down:
>
> Not true - it works fine with a single broker URI
>
> --
> James
> ---
> http://macstrac.blogspot.com/
>
> Open Source SOA
> http://open.iona.com
>
>
--
View this message in context:
http://www.nabble.com/Unable-to-create-MessageProducer-tf4782623s2354.html#a13709793
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
On 12/11/2007, TOPPER_HARLEY <[EMAIL PROTECTED]> wrote:
> >"It could just be the socket has been dropped.":
> Is socket dropping a common occurence or simply related to the quality of
> the network one is running on (my TCP level knowledge isn't great).
Its normally a glitch in the network - or th
cessor time to ping it if there is load?
>>
>> My XML defines one transport connector of the form
>> tcp://localhost:61616?wireFormat.maxInactivityDuration=0
>>
>> What can I do to workaround this issue? Can I catch the exception and try
>> to
>> restart the
omehow, although that feels like a bad solution? If I
> switched to a "vm:" style URI would it make it easier to keep transport
> alive?
>
> Any help is much appreciated as this has us stumped...
>
> /Tom
>
> --
> View this message in context:
> http:/
m
--
View this message in context:
http://www.nabble.com/Unable-to-create-MessageProducer-tf4782623s2354.html#a13682284
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
