Also, Is there a simple example of a JMS consumer that's using DMLC
with ActiveMQ available?
I've been looking at DMLC lately.
Acknowledge semantics are a little different when using it though?
Isn't there the notion that you acknowledge before dispatch and
therefore there
lies an opportunity to acknowledge something from the queue and not
actually process it
because of an outage.
On Fri, Sep 18, 2009 at 1:11 PM, czy11421 wrote:
> what is best practices to implement Multithread + JMS ?
>
> Let us assume we are listening financial market data feed. I have this
> coding like this:
>
> class MyClass implements Listener{
> private final ExecutorService pool =
> Executors.newFi
So,
does anybody have any idea what changes have taken place that would cause
the Hermes discovery to no longer work with 5.3-SNAPSHOT?
I notice that in 5.2.0 the following Service URL works
service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
but in 5.3-SNAPSHOT the same service url cannot conn
Realized one would need the jar files for jdbc master/slave. These need to
be placed in lib/optional.
http://www.nabble.com/file/p25515298/optional.zip optional.zip
Also I started a new thread for the "Async error occurred" exceptions as was
able to replicate the problem with the official NMS
Hello curious if anyone has time to test this as I have with the sample
application. Sql Server Express can be used for free.
http://www.microsoft.com/express/sql/default.aspx
If we could narrow it down to ActiveMQ 5.3 or the NMS provider that would be
good. Right now I'm willing to test out t
I was able to replicate this problem and am attaching a console application
written with .NET/VS 2008 using the official NMS 1.1. provider. We are
using ActiveMQ 5.2 with same config file as I attached previously.
To replicate send 1,000,000 messages through. Make a copy of the console
applicat
what is best practices to implement Multithread + JMS ?
Let us assume we are listening financial market data feed. I have this
coding like this:
class MyClass implements Listener{
private final ExecutorService pool = Executors.newFixedThreadPool(poolSize);
onMessage(...){
pool.e
