Perhaps memory being shared between the JVM and C++ is not properly allocated
for use in the JVM?
Anyway, this sound likely to be a JNI-related issue; you may want to look
for a forum with more JNI knowledge (stack overflow?).
--
View this message in context:
http://activemq.2283324.n4.nabble.
I scrubbed out the queue names because it was just a long list of all my
queues
INFO | Recovery replayed 18364 operations from the journal in 0.699 seconds.
ERROR | java.lang.RuntimeException: Failed to start per destination
persistence adapter for destination: queue://,
options:[KahaDBPersistence
Art,
Looking at ActiveMQConnection, In the close method, I see
>
> ServiceSupport.dispose(this.transport);
>
Yes, now I can see it into the finally block, so the connection handle the
passed transaction close() call.
> This in turn calls
>
> service.stop();
>
> Which ult
I hava done some test while using the new feature Replicated LevelDB.
I'm running a 3 node ActiveMQ quorum_mem and 3 node Zookeeper.
In a PtoP situation,using a pooled connectionFactory to send Messages with
one queue.
I observed 3000 msgs/sec which is similar with using levelDB or KahaDb in
norma
