Re: Why don't Commit() and Receive() throw exceptions ? (NMS)

Hi Sebastian, The URI settings are not identical between the JMS provider and NMS. Even the different JMS providers (ActiveMQ, TIBCO, MSMQ) have specific URI parameters. Currently, the documentation is a bit behind on which URI parameters are available for the separate provider implementations.

Re: Why don't Commit() and Receive() throw exceptions ? (NMS)

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

Re: Why don't Commit() and Receive() throw exceptions ? (NMS)

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 to 0 would effectively disable pre

Re: Why don't Commit() and Receive() throw exceptions ? (NMS)

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

Why don't Commit() and Receive() throw exceptions ? (NMS)

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