Re: Artemis HA cluster with replication
>From which script are you talking about? I am configuring and starting the EmbeddedJMS from a simple Main-class. Maybe such a check could be triggered at that point? -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-HA-cluster-with-replication-tp4725734p4725817.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Artemis v2.0 JDK8 dependency
Thanks for the info. Our broker itself is running on Jdk8, so that is not a problem. Its the client I am concerned about. We have a mixture of Jdk7 and jdk8 clients(publishers and consumers). So, we would like to give them an option to use either and upgrade to jdk8 at their convenient time. We do use JAAS module to hook up our custom authentication mechanism. We are also using netty connectors both for cluster and also from client to server. We are using JMS currently and have no plans to switch to AMQP. With these constraints, do you guys recommend to upgrade to 2.0 or it is better to stay in 1.x? -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-v2-0-JDK8-dependency-tp4725798p4725816.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Artemis Rest installation & configuration
In every case you need to build and install the WAR for the REST interface. Historically this has required an application server like Wildfly with a built-in web server. However, I'm fairly certain there are individuals on this list who have deployed the REST interface WAR directly on Artemis using the embedded Jetty server. Justin - Original Message - From: "mtod" To: users@activemq.apache.org Sent: Sunday, May 7, 2017 4:12:19 PM Subject: Artemis Rest installation & configuration I seem to be missing something on the REST setup the doc seems to cover 2 types of install an app server like Wildfly or an embedded install. I have Artemis running as a service on a Windows Server where does that fall? Also it seems that to use Rest I would have to build a war file is that correct there's no default Rest API like 5.x ActiveMQ? Thanks Mike -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-Rest-installation-configuration-tp4725729.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ActiveMQ REST Api with HTTP
Hello, I am using: curl-7.48.0-win32-mingw apache-activemq-5.14.5-bin (locally) I can add messages like this: curl -u admin:admin -d "hello world 1" -H "Content-Type: text/plain" -XPOST "http://localhost:8161/api/message?destination=queue://Test_Kovac&&clientId=KovacIP1"; curl -u admin:admin -d "hello world 1" -H "Content-Type: text/plain" -XPOST "http://localhost:8161/api/message?destination=queue://Test_Kovac&&clientId=KovacIP2"; I can retrieve both messages with: curl -u admin:admin -X GET "http://localhost:8161/api/message?destination=queue://Test_Kovac?type=queue&clientId=KovacIP1"; 1- How come my clientid parameter doesn't filter wich messages I retrieve? "When using this approach, you don't need to keep sessions alive between requests, you just need to use the same clientId every time." - Afterwards, I try using selectors, but they don't seem to work either I insert this: curl -u admin:admin -d "hello world 1" -H "Content-Type: text/plain" -XPOST "http://localhost:8161/api/message?destination=queue://Test_Kovac&&clientId=KovacIP1"; curl -u admin:admin -d "test selector" -H "Content-Type: text/plain" -XPOST "http://localhost:8161/api/message?destination=queue://Test_Kovac&&clientId=KovacIP2&test=2"; curl -u admin:admin -d "hello world 3" -H "Content-Type: text/plain" -XPOST "http://localhost:8161/api/message?destination=queue://Test_Kovac&&clientId=KovacIP3"; When I try to retrieve test=2 with this command curl -u admin:admin -H "selector: test=2" -X GET "http://localhost:8161/api/message?destination=queue://Test_Kovac?type=queue&clientId=KovacIP2"; I have access to all the message. I retreive them all (all 3 of them) 1 by 1. Why is that? How does the selector work? Thanks for your help -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-REST-Api-with-HTTP-tp4725797.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Artemis v2.0 JDK8 dependency
There are a few lambda uses on Artemis. You can probably bypass them on a fork and some consulting gig. Although you could maybe use AMQP client or openwire client? I'm not sure about netty. What's the requirement. I would suggest an older AMQP or openwire client thought. On Mon, May 8, 2017 at 5:24 PM abhijith wrote: > Hi, > > Is there a hard dependency for Artemis v2.0 to be on Jdk8? I am trying to > upgrade a client which is built on jdk7, but enforcer plugin is showing > bunch of non-compatibility issues. > > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce) @ > my-artemis-client > --- > [INFO] Restricted to JDK 1.7 yet > org.apache.activemq:artemis-jms-client:jar:2.0.0:compile contains > org/apache/activemq/artemis/uri/UDPSchema.class targeted to JDK 1.8 > [INFO] Restricted to JDK 1.7 yet > org.apache.activemq:artemis-journal:jar:2.0.0:test contains > > org/apache/activemq/artemis/core/io/AbstractSequentialFile$LocalBufferObserver.class > targeted to JDK 1.8 > [INFO] Restricted to JDK 1.7 yet > org.apache.activemq:artemis-server:jar:2.0.0:test contains > org/apache/activemq/artemis/core/messagecounter/MessageCounter.class > targeted to JDK 1.8 > [INFO] Restricted to JDK 1.7 yet > org.apache.activemq:artemis-selector:jar:2.0.0:compile contains > org/apache/activemq/artemis/selector/strict/TokenMgrError.class targeted to > JDK 1.8 > [INFO] Restricted to JDK 1.7 yet > org.apache.activemq:artemis-dto:jar:2.0.0:test contains > org/apache/activemq/artemis/dto/AppDTO.class targeted to JDK 1.8 > [INFO] Restricted to JDK 1.7 yet > org.apache.activemq:artemis-service-extensions:jar:2.0.0:test contains > org/apache/activemq/artemis/service/extensions/ServiceUtils$1.class > targeted > to JDK 1.8 > [INFO] Restricted to JDK 1.7 yet > org.apache.activemq:artemis-jdbc-store:jar:2.0.0:test contains > org/apache/activemq/artemis/jdbc/store/file/JDBCSequentialFile.class > targeted to JDK 1.8 > [INFO] Restricted to JDK 1.7 yet > org.apache.activemq:artemis-tools:jar:2.0.0:test contains > > org/apache/activemq/artemis/tools/migrate/config/XMLConfigurationMigration.class > targeted to JDK 1.8 > [INFO] Restricted to JDK 1.7 yet > org.apache.activemq:artemis-commons:jar:2.0.0:compile contains > org/apache/activemq/artemis/core/buffers/impl/ChannelBufferWrapper.class > targeted to JDK 1.8 > [INFO] Restricted to JDK 1.7 yet > org.apache.activemq:artemis-cli:jar:2.0.0:test contains > org/apache/activemq/artemis/components/ExternalComponent.class targeted to > JDK 1.8 > [INFO] Restricted to JDK 1.7 yet > org.apache.activemq:artemis-jms-server:jar:2.0.0:test contains > org/apache/activemq/artemis/jms/bridge/DestinationFactory.class targeted to > JDK 1.8 > [INFO] Restricted to JDK 1.7 yet > org.apache.activemq:artemis-native:jar:2.0.0:test contains > org/apache/activemq/artemis/jlibaio/LibaioContext$1.class targeted to JDK > 1.8 > [INFO] Restricted to JDK 1.7 yet > org.apache.activemq:artemis-core-client:jar:2.0.0:compile contains > > org/apache/activemq/artemis/core/settings/impl/AddressFullMessagePolicy.class > targeted to JDK 1.8 > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Artemis-v2-0-JDK8-dependency-tp4725798.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- Clebert Suconic
Artemis v2.0 JDK8 dependency
Hi, Is there a hard dependency for Artemis v2.0 to be on Jdk8? I am trying to upgrade a client which is built on jdk7, but enforcer plugin is showing bunch of non-compatibility issues. [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce) @ my-artemis-client --- [INFO] Restricted to JDK 1.7 yet org.apache.activemq:artemis-jms-client:jar:2.0.0:compile contains org/apache/activemq/artemis/uri/UDPSchema.class targeted to JDK 1.8 [INFO] Restricted to JDK 1.7 yet org.apache.activemq:artemis-journal:jar:2.0.0:test contains org/apache/activemq/artemis/core/io/AbstractSequentialFile$LocalBufferObserver.class targeted to JDK 1.8 [INFO] Restricted to JDK 1.7 yet org.apache.activemq:artemis-server:jar:2.0.0:test contains org/apache/activemq/artemis/core/messagecounter/MessageCounter.class targeted to JDK 1.8 [INFO] Restricted to JDK 1.7 yet org.apache.activemq:artemis-selector:jar:2.0.0:compile contains org/apache/activemq/artemis/selector/strict/TokenMgrError.class targeted to JDK 1.8 [INFO] Restricted to JDK 1.7 yet org.apache.activemq:artemis-dto:jar:2.0.0:test contains org/apache/activemq/artemis/dto/AppDTO.class targeted to JDK 1.8 [INFO] Restricted to JDK 1.7 yet org.apache.activemq:artemis-service-extensions:jar:2.0.0:test contains org/apache/activemq/artemis/service/extensions/ServiceUtils$1.class targeted to JDK 1.8 [INFO] Restricted to JDK 1.7 yet org.apache.activemq:artemis-jdbc-store:jar:2.0.0:test contains org/apache/activemq/artemis/jdbc/store/file/JDBCSequentialFile.class targeted to JDK 1.8 [INFO] Restricted to JDK 1.7 yet org.apache.activemq:artemis-tools:jar:2.0.0:test contains org/apache/activemq/artemis/tools/migrate/config/XMLConfigurationMigration.class targeted to JDK 1.8 [INFO] Restricted to JDK 1.7 yet org.apache.activemq:artemis-commons:jar:2.0.0:compile contains org/apache/activemq/artemis/core/buffers/impl/ChannelBufferWrapper.class targeted to JDK 1.8 [INFO] Restricted to JDK 1.7 yet org.apache.activemq:artemis-cli:jar:2.0.0:test contains org/apache/activemq/artemis/components/ExternalComponent.class targeted to JDK 1.8 [INFO] Restricted to JDK 1.7 yet org.apache.activemq:artemis-jms-server:jar:2.0.0:test contains org/apache/activemq/artemis/jms/bridge/DestinationFactory.class targeted to JDK 1.8 [INFO] Restricted to JDK 1.7 yet org.apache.activemq:artemis-native:jar:2.0.0:test contains org/apache/activemq/artemis/jlibaio/LibaioContext$1.class targeted to JDK 1.8 [INFO] Restricted to JDK 1.7 yet org.apache.activemq:artemis-core-client:jar:2.0.0:compile contains org/apache/activemq/artemis/core/settings/impl/AddressFullMessagePolicy.class targeted to JDK 1.8 -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-v2-0-JDK8-dependency-tp4725798.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Artemis HA cluster with replication
You could also contribute a change to the script to reboot the server in case of JVM crash, that way client reconnects would work and you would only need the network pinger in case of a real box crash. On Mon, May 8, 2017 at 10:32 AM, Clebert Suconic wrote: > you need a network of brokers of at least 3 pairs to have quorum working fine. > > On Mon, May 8, 2017 at 8:47 AM, martk <123mar...@web.de> wrote: >> Hi clebertsuconic, >> >> I have tested the network check by adding (on master with the SLAVEIP and on >> slave with the MASTERIP): >> >> 1 >> 1000 >> MASTERIP/SLAVEIP >> >> Using the described signals to test this does not work (which makes sense, >> because the ping is working). >> >> How many servers would I need for a group? What is needed to configure it? >> Can you provide an example please? >> >> >> >> -- >> View this message in context: >> http://activemq.2283324.n4.nabble.com/Artemis-HA-cluster-with-replication-tp4725734p4725741.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > > > -- > Clebert Suconic -- Clebert Suconic
Re: Artemis HA cluster with replication
you need a network of brokers of at least 3 pairs to have quorum working fine. On Mon, May 8, 2017 at 8:47 AM, martk <123mar...@web.de> wrote: > Hi clebertsuconic, > > I have tested the network check by adding (on master with the SLAVEIP and on > slave with the MASTERIP): > > 1 > 1000 > MASTERIP/SLAVEIP > > Using the described signals to test this does not work (which makes sense, > because the ping is working). > > How many servers would I need for a group? What is needed to configure it? > Can you provide an example please? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Artemis-HA-cluster-with-replication-tp4725734p4725741.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- Clebert Suconic
Re: ActiveMQ with PostgreSQL: Not deleting persistent messages sent to a topic
The odds of that bug being prioritized for work will increase if you can use a debugger to help figure out specifically what is failing in the code. Nothing says that one of the developers won't prioritize it as-is, but your odds would be better if you were able to say "here's the block of code with the wrong logic." But it's really your decision how important it is to you that the bug get fixed as soon as possible. Tim On May 8, 2017 1:27 AM, "khandelwalanuj" wrote: > I think doSetLaskAck is working fine perfectly as I can see that the value > of > last ackd message is getting updated properly. > > I have logged a bug request https://issues.apache.org/ > jira/browse/AMQ-6671 > for the same. > > Thanks, > Anuj > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/ActiveMQ-with-PostgreSQL-Not-deleting- > persistent-messages-sent-to-a-topic-tp4725654p4725733.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
Re: Artemis HA cluster with replication
Hi clebertsuconic, I have tested the network check by adding (on master with the SLAVEIP and on slave with the MASTERIP): 1 1000 MASTERIP/SLAVEIP Using the described signals to test this does not work (which makes sense, because the ping is working). How many servers would I need for a group? What is needed to configure it? Can you provide an example please? -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-HA-cluster-with-replication-tp4725734p4725741.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Artemis HA cluster with replication
U need either a group of servers to establish quorums or u need the network pinger. On Mon, May 8, 2017 at 3:46 AM martk <123mar...@web.de> wrote: > Hello, > > I am using ActiveMQ Artemis 1.5.4 and configured a high available cluster > (master/slave broker) with replication (using static connectors; see main > configuration parts below). > > Under normal conditions (network connection fails or process shutdown/kill) > the switch from master to slave and backwards (desired to do by hand) works > nearly all the time (sometimes the backup server is not in sync although > both were parallel started for quite a time). > > Simulating a busy master server results in two active master broker > (processing messages but with no replication any more). To test/reproduce I > have done the following steps: > > 1. Master and slave proper started (master is live and slave is backup). > 2. Master stopped by sending the SIGSTOP signal to the process. After some > time the slave recognized the problem and gets live. > 4. Sending the SIGCONT signal to the master process causes a running master > and slave. This could then only be resolved with a manual shutdown of both > and probably a lose of messages. > > I would like to ensure only one live broker at the same time and the other > to do the backup (a shared storage is not possible). > Maybe it can be resolved by configuration otherwise I think that is a bug > because both server should always perform a continuous live-check. > > > master-broker.xml > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >xsi:schemaLocation="urn:activemq > /schema/artemis-configuration.xsd"> > > > master > > true > > > > >true > > > > > > tcp://MASTERIP:61616 > name="netty-backup-connector-slave">tcp://SLAVEIP:61616 > > > > tcp://MASTERIP:61616 > > > > > jms > netty-connector > 500 > true > >netty-backup-connector-slave > > > > > > > > > slave-broker.xml > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >xsi:schemaLocation="urn:activemq > /schema/artemis-configuration.xsd"> > > > slave1 > > true > > > > >false > > > > > > name="netty-live-connector">tcp://MASTERIP:61616 > tcp://SLAVEIP:61616 > > > > tcp://SLAVEIP:61616 > > > > > jms > netty-connector > 500 > true > >netty-live-connector > > > > > > > > > > Regards, > Martin > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Artemis-HA-cluster-with-replication-tp4725734.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- Clebert Suconic
Is it possible to keep two certificates in activemq ssl context?
Is it possible to keep two certificates in activemq to communicate with two different clients (i.e old client with old certificate and new client with new certificate). In activemq keystore file I have imported two keys of old and new certificates. In this the new client is communicating fine and the old client is unable to communicate to activemq. The following exception I get while client tries to connect to activemq javax.jms.JMSException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:62) at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1298) at org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1382) at org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:309) at com.sample.ssl.job.handler.MessageQueueLocator.getJmsSession(Unknown Source) at com.sample.ssl.job.handler.MessageQueueLocator.sendMessageToGeneralQueue(Unknown Source) at com.sample.ssl.communication.JobResposeDispatcherInvoker.dispatchStartupMessage(Unknown Source) at com.sample.ssl.job.MessageDispatchJob.dispatchStartupMessage(Unknown Source) at com.sample.ssl.job.MessageDispatchJob.execute(Unknown Source) at org.quartz.core.JobRunShell.run(JobRunShell.java:202) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529) Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1731) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:241) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:235) at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1206) at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:136) at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:593) at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:529) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:925) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1170) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:637) at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:89) at org.apache.activemq.transport.tcp.TcpBufferedOutputStream.flush(TcpBufferedOutputStream.java:115) at java.io.DataOutputStream.flush(DataOutputStream.java:106) at org.apache.activemq.transport.tcp.TcpTransport.oneway(TcpTransport.java:181) at org.apache.activemq.transport.InactivityMonitor.oneway(InactivityMonitor.java:255) at org.apache.activemq.transport.WireFormatNegotiator.sendWireFormat(WireFormatNegotiator.java:168) at org.apache.activemq.transport.WireFormatNegotiator.sendWireFormat(WireFormatNegotiator.java:84) at org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiator.java:74) at org.apache.activemq.transport.failover.FailoverTransport.doReconnect(FailoverTransport.java:844) at org.apache.activemq.transport.failover.FailoverTransport$2.iterate(FailoverTransport.java:135) at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:122) at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:43) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed at sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:289) at sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:263) at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:184) at sun.security.validator.Validator.validate(Validator.java:218) at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:126) at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:209) at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:249) at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1185) ... 21 more Caused by: java.security.cert.CertPathValidatorException: signature check failed at sun.security.provider.certp
Artemis HA cluster with replication
Hello, I am using ActiveMQ Artemis 1.5.4 and configured a high available cluster (master/slave broker) with replication (using static connectors; see main configuration parts below). Under normal conditions (network connection fails or process shutdown/kill) the switch from master to slave and backwards (desired to do by hand) works nearly all the time (sometimes the backup server is not in sync although both were parallel started for quite a time). Simulating a busy master server results in two active master broker (processing messages but with no replication any more). To test/reproduce I have done the following steps: 1. Master and slave proper started (master is live and slave is backup). 2. Master stopped by sending the SIGSTOP signal to the process. After some time the slave recognized the problem and gets live. 4. Sending the SIGCONT signal to the master process causes a running master and slave. This could then only be resolved with a manual shutdown of both and probably a lose of messages. I would like to ensure only one live broker at the same time and the other to do the backup (a shared storage is not possible). Maybe it can be resolved by configuration otherwise I think that is a bug because both server should always perform a continuous live-check. master-broker.xml http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="urn:activemq /schema/artemis-configuration.xsd"> master true true tcp://MASTERIP:61616 tcp://SLAVEIP:61616 tcp://MASTERIP:61616 jms netty-connector 500 true netty-backup-connector-slave slave-broker.xml http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="urn:activemq /schema/artemis-configuration.xsd"> slave1 true false tcp://MASTERIP:61616 tcp://SLAVEIP:61616 tcp://SLAVEIP:61616 jms netty-connector 500 true netty-live-connector Regards, Martin -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-HA-cluster-with-replication-tp4725734.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: ActiveMQ with PostgreSQL: Not deleting persistent messages sent to a topic
I think doSetLaskAck is working fine perfectly as I can see that the value of last ackd message is getting updated properly. I have logged a bug request https://issues.apache.org/jira/browse/AMQ-6671 for the same. Thanks, Anuj -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-with-PostgreSQL-Not-deleting-persistent-messages-sent-to-a-topic-tp4725654p4725733.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
