suggested
that it was a socket timeout issue, however I was not able to configure the
connection with the documentation I could find
- my issued has been resolved (for now) by using
transport.requesttimeout=1
Michael
--
View this message in context:
http://www.nabble.com/NMS-library
tions are not relayed back to
> > the caller.
> > --
> > View this message in context:
> >
> http://www.nabble.com/NMS-library-hangs-when-connection-to-ActiveMQ-is-broken-tp16452218s2354p16452218.html
> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >
> >
>
Well, they say that the sourcs code itself is the ultimate
documentation. :). But in this regard, there is not a single location
that lists all possible URI parameters for the .NET client in a single
location. I think the Java client is documented, and we try to stay
compatible, but I know there a
Jim Gomes wrote:
I am currently taking a look at this. Part of the solution is to set
a timeout for your transport using a URI parameter like so:
activemq:tcp://amqsrv:61616?transport.requesttimeout=1
Thanks Jim. BTW, is there any place (possibly in the source code) where
all possible U
to
> the caller.
> --
> View this message in context:
> http://www.nabble.com/NMS-library-hangs-when-connection-to-ActiveMQ-is-broken-tp16452218s2354p16452218.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
The NMS API calls to send and receive messages synchronously hang when the
connection to ActiveMQ gets broken, the expections are not relayed back to
the caller.
--
View this message in context:
http://www.nabble.com/NMS-library-hangs-when-connection-to-ActiveMQ-is-broken
