semog wrote:
>
> Hi Sebastian,
>
> You can set the prefetch size on the connection URI as follows:
>
> activemq:tcp://servername:61616?session.prefetchSize=5
>
> As you noted, the prefetch size is set to 1000 as a default, but it can be
> changed on a per-connection basis. Setting the value
I found out that what i called a local store is in ActiveMQ called
prefetching. This prefetching is controlled via the variable prefetchSize
(which in NMS is set in the session.cs to a fixed value of 1000). Do I have
influence on this value in some way ? It would even better if, there would
be a
Hello,
i recognized that neither the ISession.Commit()- nor the
IMessageConsumer.Receive()-method throw any exceptions when called although
there is no connection established. I debugged a little into the
ActiveMQ.NMS namespaces and they actually realize that the connection is
broken (TcpTranspor
Hiram Chirino wrote:
>
> A connection will hold on to messages that's trying to deliver to it's
> client until the broker detects that the connection has failed.
>
> In the last case is you main thread blocked somewhere?
>
>
Nope, the programm shuts down correctly, probably because at the re
Hello,
First of all my setup:
NMS: Yesterdays HEAD SVN revision
Broker: external broker running on ActiveMQ 4.1.1
.Net Framework: 2.0
IDE: MS Visual Studio 2008 with C# as programming language
I recognize very strange behaviour when it comes to a connection failure. To
show this I wrote a littl
