[jira] [Updated] (AMQ-4734) Upgrade Jolokia to 1.1.3
[ https://issues.apache.org/jira/browse/AMQ-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated AMQ-4734: - Component/s: Broker Affects Version/s: 5.8.0 Fix Version/s: 5.9.0 Issue Type: Task (was: Improvement) > Upgrade Jolokia to 1.1.3 > > > Key: AMQ-4734 > URL: https://issues.apache.org/jira/browse/AMQ-4734 > Project: ActiveMQ > Issue Type: Task > Components: Broker >Affects Versions: 5.8.0 >Reporter: Lionel Cons >Assignee: Claus Ibsen > Fix For: 5.9.0 > > > ActiveMQ currently uses Jolokia 1.0.6 while the latest version is 1.1.3. > It would be good to upgraded Jolokia before the 5.9.0 release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (AMQ-4734) Upgrade Jolokia to 1.1.3
[ https://issues.apache.org/jira/browse/AMQ-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned AMQ-4734: Assignee: Claus Ibsen > Upgrade Jolokia to 1.1.3 > > > Key: AMQ-4734 > URL: https://issues.apache.org/jira/browse/AMQ-4734 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Lionel Cons >Assignee: Claus Ibsen > > ActiveMQ currently uses Jolokia 1.0.6 while the latest version is 1.1.3. > It would be good to upgraded Jolokia before the 5.9.0 release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-4733) Upgrade to Jasypt 1.9.1
[ https://issues.apache.org/jira/browse/AMQ-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved AMQ-4733. -- Resolution: Fixed Thanks for the patch. > Upgrade to Jasypt 1.9.1 > --- > > Key: AMQ-4733 > URL: https://issues.apache.org/jira/browse/AMQ-4733 > Project: ActiveMQ > Issue Type: Task > Components: Broker >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 5.9.0 > > Attachments: AMQ-4733.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-4735) LinkageError in latest 5.9 snapshot
[ https://issues.apache.org/jira/browse/AMQ-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lionel Cons updated AMQ-4735: - Attachment: activemq.log > LinkageError in latest 5.9 snapshot > --- > > Key: AMQ-4735 > URL: https://issues.apache.org/jira/browse/AMQ-4735 > Project: ActiveMQ > Issue Type: Bug > Environment: activemq-5.9-20130919.101342-100 >Reporter: Lionel Cons > Attachments: activemq.log > > > When upgrading a test broker to the latest 5.9 snapshot I get: > java.lang.LinkageError: loader constraint violation: when resolving method > "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" > the class loader (instance of org/eclipse/jetty/webapp/WebAppClassLoader) of > the current class, org/slf4j/LoggerFactory, and the class loader (instance of > java/net/URLClassLoader) for resolved class, > org/slf4j/impl/StaticLoggerBinder, have different Class objects for the type > org/slf4j/ILoggerFactory used in the signature -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4735) LinkageError in latest 5.9 snapshot
Lionel Cons created AMQ-4735: Summary: LinkageError in latest 5.9 snapshot Key: AMQ-4735 URL: https://issues.apache.org/jira/browse/AMQ-4735 Project: ActiveMQ Issue Type: Bug Environment: activemq-5.9-20130919.101342-100 Reporter: Lionel Cons When upgrading a test broker to the latest 5.9 snapshot I get: java.lang.LinkageError: loader constraint violation: when resolving method "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" the class loader (instance of org/eclipse/jetty/webapp/WebAppClassLoader) of the current class, org/slf4j/LoggerFactory, and the class loader (instance of java/net/URLClassLoader) for resolved class, org/slf4j/impl/StaticLoggerBinder, have different Class objects for the type org/slf4j/ILoggerFactory used in the signature -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4734) Upgrade Jolokia to 1.1.3
Lionel Cons created AMQ-4734: Summary: Upgrade Jolokia to 1.1.3 Key: AMQ-4734 URL: https://issues.apache.org/jira/browse/AMQ-4734 Project: ActiveMQ Issue Type: Improvement Reporter: Lionel Cons ActiveMQ currently uses Jolokia 1.0.6 while the latest version is 1.1.3. It would be good to upgraded Jolokia before the 5.9.0 release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Use ActiveMQ to receive messages from extern data center
Please DO NOT cross post. This is the dev list.. you already asked this on the user's mailing list. On Mon, Sep 23, 2013 at 2:21 PM, Nicolas wrote: > Hello, > We plan to use ActiveMQ to receive JMS messages coming from the data center > of a partner , so external to our data center. > How to manage it ? > Firewall ? DMZ ? > The both data centers (partner DC and our DC) are private and accesible > only > via VPN until now. > > Tks a lot > Nicolas > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Use-ActiveMQ-to-receive-messages-from-extern-data-center-tp4671752.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
Use ActiveMQ to receive messages from extern data center
Hello, We plan to use ActiveMQ to receive JMS messages coming from the data center of a partner , so external to our data center. How to manage it ? Firewall ? DMZ ? The both data centers (partner DC and our DC) are private and accesible only via VPN until now. Tks a lot Nicolas -- View this message in context: http://activemq.2283324.n4.nabble.com/Use-ActiveMQ-to-receive-messages-from-extern-data-center-tp4671752.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] [Updated] (AMQ-4733) Upgrade to Jasypt 1.9.1
[ https://issues.apache.org/jira/browse/AMQ-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-4733: -- Attachment: AMQ-4733.patch > Upgrade to Jasypt 1.9.1 > --- > > Key: AMQ-4733 > URL: https://issues.apache.org/jira/browse/AMQ-4733 > Project: ActiveMQ > Issue Type: Task > Components: Broker >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 5.9.0 > > Attachments: AMQ-4733.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4733) Upgrade to Jasypt 1.9.1
Jean-Baptiste Onofré created AMQ-4733: - Summary: Upgrade to Jasypt 1.9.1 Key: AMQ-4733 URL: https://issues.apache.org/jira/browse/AMQ-4733 Project: ActiveMQ Issue Type: Task Components: Broker Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 5.9.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQNET-443) Better logging for XATransaction
[ https://issues.apache.org/jira/browse/AMQNET-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remo Gloor updated AMQNET-443: -- Affects Version/s: 1.6.0 > Better logging for XATransaction > > > Key: AMQNET-443 > URL: https://issues.apache.org/jira/browse/AMQNET-443 > Project: ActiveMQ .Net > Issue Type: Improvement >Affects Versions: 1.6.0 >Reporter: Remo Gloor >Assignee: Jim Gomes >Priority: Minor > Attachments: BetterLoggingForXATransaction.patch > > > The current log output is not really helpful because you don't see what for > which transaction the log entry is written: > DEBUG: Transaction Rollback Done TX id: XATransactionId[ FormatId = 0, > GlobalTransactionId = System.Byte[] > The patch will change this to: > DEBUG: Transaction Rollback Done TX id: XATransactionId[ FormatId = 0, > GlobalTransactionId = DF0D6FAA45EAA44885A322CD299493AD, BranchQualifier = > c23f8230-9892-49c7-a3ed-6e6bd5ffd05c ] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQNET-443) Better logging for XATransaction
[ https://issues.apache.org/jira/browse/AMQNET-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remo Gloor updated AMQNET-443: -- Attachment: BetterLoggingForXATransaction.patch > Better logging for XATransaction > > > Key: AMQNET-443 > URL: https://issues.apache.org/jira/browse/AMQNET-443 > Project: ActiveMQ .Net > Issue Type: Improvement >Reporter: Remo Gloor >Assignee: Jim Gomes >Priority: Minor > Attachments: BetterLoggingForXATransaction.patch > > > The current log output is not really helpful because you don't see what for > which transaction the log entry is written: > DEBUG: Transaction Rollback Done TX id: XATransactionId[ FormatId = 0, > GlobalTransactionId = System.Byte[] > The patch will change this to: > DEBUG: Transaction Rollback Done TX id: XATransactionId[ FormatId = 0, > GlobalTransactionId = DF0D6FAA45EAA44885A322CD299493AD, BranchQualifier = > c23f8230-9892-49c7-a3ed-6e6bd5ffd05c ] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQNET-443) Better logging for XATransaction
Remo Gloor created AMQNET-443: - Summary: Better logging for XATransaction Key: AMQNET-443 URL: https://issues.apache.org/jira/browse/AMQNET-443 Project: ActiveMQ .Net Issue Type: Improvement Reporter: Remo Gloor Assignee: Jim Gomes Priority: Minor The current log output is not really helpful because you don't see what for which transaction the log entry is written: DEBUG: Transaction Rollback Done TX id: XATransactionId[ FormatId = 0, GlobalTransactionId = System.Byte[] The patch will change this to: DEBUG: Transaction Rollback Done TX id: XATransactionId[ FormatId = 0, GlobalTransactionId = DF0D6FAA45EAA44885A322CD299493AD, BranchQualifier = c23f8230-9892-49c7-a3ed-6e6bd5ffd05c ] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4732) maven : add IssueManagement declaration
lord created AMQ-4732: - Summary: maven : add IssueManagement declaration Key: AMQ-4732 URL: https://issues.apache.org/jira/browse/AMQ-4732 Project: ActiveMQ Issue Type: Task Reporter: lord Priority: Trivial It would be nice to get the IssueManagement declared in pom.xml like this : Jira https://issues.apache.org/jira/browse/AMQ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-4533) Messages stuck in queue with redelivered=true
[ https://issues.apache.org/jira/browse/AMQ-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wieslaw Dudek updated AMQ-4533: --- Attachment: LOGS_FAILED_5.9.0.redhat-610-SNAPSHOT.zip > Messages stuck in queue with redelivered=true > - > > Key: AMQ-4533 > URL: https://issues.apache.org/jira/browse/AMQ-4533 > Project: ActiveMQ > Issue Type: Bug > Components: JMS client >Affects Versions: 5.7.0 > Environment: Fuse Message Broker 5.7.0 >Reporter: Jason Shepherd >Assignee: Timothy Bish > Fix For: 5.9.0 > > Attachments: AMQ4533_logs.ZIP, AMQ4533Test.java, AMQ4533-test.patch, > AMQ4533-Test.patch, AMQ4533-Test.patch, AMQ4533-Test.patch, > AMQ4533-Test.patch, AMQ4533-Test.patch, AMQ4533TestPatch.txt, > AMQ4533TestPatch.txt, AMQ4533TestPatch.txt, AMQFreezeFailingTest.zip, > AMQFreeze_logs.zip, AMQFreezeTest-5.8.0.fuse-72-SNAPSHOT-log.zip, > AMQFreezeTest-5.9.0.redhat-610084-log.zip, AMQFreezeTest.patch, > AMQFreezeTest.zip, AMQFreezeTest.zip, kahaPendingMessages.zip, > LOGS_FAILED_5.9.0.redhat-610-SNAPSHOT.zip > > > We're getting message stuck in queues with the > redelivery flag set to true. > We used the following test model: put every 1 second 50 messages > sequentially, and after that, the rest of 1000 msgs quickly to INPUT_QUEUE > and > while starting 25 listeners cosuming from INPUT_QUEUE, which takes about 30 > seconds to move the message to RECEIPT_QUEUE, 10 other listeners on > RECEIPT_QUEUE consume and counts them. > We tried making one of the consumer slow by setting the > processing time to 10 seconds (sleep) and putting a heavy load in > 500 threads every 1 ms to some other queues the same time. > Our test case is attached, you might need to install some dependencies > to the local maven repository manually: > mvn install:install-file -DgroupId=org.apache.activemq > -DartifactId=activemq-core -Dversion=5.7.0-fuse-71-047 -Dpackaging=jar > -Dfile=activemq-core-5.7.0.fuse-71-047.jar > mvn install:install-file -DgroupId=org.apache.kahadb > -DartifactId=kahadb -Dversion=5.7.0-fuse-71-047 -Dpackaging=jar > -Dfile=kahadb-5.7.0.fuse-71-047.jar > mvn install:install-file > -DgroupId=org.apache.geronimo.management.specs > -DartifactId=geronimo-j2ee-management_1.1_spec -Dversion=1.0.1 > -Dpackaging=jar -Dfile=geronimo-j2ee-management_1.1_spec-1.0.1.jar > mvn install:install-file -DgroupId=org.apache.activemq.pool > -DartifactId=activemq-pool -Dversion=5.7.0-fuse-71-047 -Dpackaging=jar > -Dfile=activemq-pool-5.7.0.fuse-71-047.jar > To run the test, simply use the Maven test target: > mvn clean test > If the problem occurs the you'll get a message like this in the test > results, (target/surefire-reports): > java.lang.AssertionError: Still messages in InputQueue expected:<0> > but was:<365> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4533) Messages stuck in queue with redelivered=true
[ https://issues.apache.org/jira/browse/AMQ-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774441#comment-13774441 ] Wieslaw Dudek commented on AMQ-4533: I used the last test case from: https://fusesource.com/issues/browse/ENTMQ-409 and tested it on my laptop. Results: Tests run: 20 Failed: 8 I attached logs from the failed tests: LOGS_FAILED_5.9.0.redhat-610-SNAPSHOT.zip I have also checked it on very slow Solaris system where I was not able to get the test case passed even once/see attached logs/. After changing only the options to have abortConnection="true" ignoreIdleConsumers="false" I managed to pass the test case on the Solaris environment and got better results on the laptop with Windows OS: Tests run: 20 Failed 2 So I was able to get the test case failed even with abortConnection="true" ignoreIdleConsumers="false" but it behaved much better with these options. For testing I used the oryginal TC and 5.9.0.redhat-610-SNAPSHOT from: http://repo.fusesource.com/nexus/content/repositories/snapshots/ As for activemq-all we had only those: 5.9-fuse-SNAPSHOT/ Thu Jun 27 11:57:53 UTC 2013 5.9.0.redhat-610-SNAPSHOT/ Sat Sep 21 00:34:04 UTC 2013 > Messages stuck in queue with redelivered=true > - > > Key: AMQ-4533 > URL: https://issues.apache.org/jira/browse/AMQ-4533 > Project: ActiveMQ > Issue Type: Bug > Components: JMS client >Affects Versions: 5.7.0 > Environment: Fuse Message Broker 5.7.0 >Reporter: Jason Shepherd >Assignee: Timothy Bish > Fix For: 5.9.0 > > Attachments: AMQ4533_logs.ZIP, AMQ4533Test.java, AMQ4533-test.patch, > AMQ4533-Test.patch, AMQ4533-Test.patch, AMQ4533-Test.patch, > AMQ4533-Test.patch, AMQ4533-Test.patch, AMQ4533TestPatch.txt, > AMQ4533TestPatch.txt, AMQ4533TestPatch.txt, AMQFreezeFailingTest.zip, > AMQFreeze_logs.zip, AMQFreezeTest-5.8.0.fuse-72-SNAPSHOT-log.zip, > AMQFreezeTest-5.9.0.redhat-610084-log.zip, AMQFreezeTest.patch, > AMQFreezeTest.zip, AMQFreezeTest.zip, kahaPendingMessages.zip > > > We're getting message stuck in queues with the > redelivery flag set to true. > We used the following test model: put every 1 second 50 messages > sequentially, and after that, the rest of 1000 msgs quickly to INPUT_QUEUE > and > while starting 25 listeners cosuming from INPUT_QUEUE, which takes about 30 > seconds to move the message to RECEIPT_QUEUE, 10 other listeners on > RECEIPT_QUEUE consume and counts them. > We tried making one of the consumer slow by setting the > processing time to 10 seconds (sleep) and putting a heavy load in > 500 threads every 1 ms to some other queues the same time. > Our test case is attached, you might need to install some dependencies > to the local maven repository manually: > mvn install:install-file -DgroupId=org.apache.activemq > -DartifactId=activemq-core -Dversion=5.7.0-fuse-71-047 -Dpackaging=jar > -Dfile=activemq-core-5.7.0.fuse-71-047.jar > mvn install:install-file -DgroupId=org.apache.kahadb > -DartifactId=kahadb -Dversion=5.7.0-fuse-71-047 -Dpackaging=jar > -Dfile=kahadb-5.7.0.fuse-71-047.jar > mvn install:install-file > -DgroupId=org.apache.geronimo.management.specs > -DartifactId=geronimo-j2ee-management_1.1_spec -Dversion=1.0.1 > -Dpackaging=jar -Dfile=geronimo-j2ee-management_1.1_spec-1.0.1.jar > mvn install:install-file -DgroupId=org.apache.activemq.pool > -DartifactId=activemq-pool -Dversion=5.7.0-fuse-71-047 -Dpackaging=jar > -Dfile=activemq-pool-5.7.0.fuse-71-047.jar > To run the test, simply use the Maven test target: > mvn clean test > If the problem occurs the you'll get a message like this in the test > results, (target/surefire-reports): > java.lang.AssertionError: Still messages in InputQueue expected:<0> > but was:<365> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-4347) Rename lockKeepAlivePeriod and lockAcquireSleepInterval for more intuition
[ https://issues.apache.org/jira/browse/AMQ-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-4347. - Resolution: Won't Fix peeked at this, and I am not sure it is worth introducing new variables to the lease locker. If the 'lock' term is replaced with a 'lease' term I think they make some sense. granted the names reflect more the implementation rather than the intent which is not ideal but the implementation is shared with all lockers so there is some consistency. > Rename lockKeepAlivePeriod and lockAcquireSleepInterval for more intuition > -- > > Key: AMQ-4347 > URL: https://issues.apache.org/jira/browse/AMQ-4347 > Project: ActiveMQ > Issue Type: Improvement > Components: Message Store >Affects Versions: 5.7.0, 5.8.0 >Reporter: SuoNayi >Assignee: Gary Tully >Priority: Minor > Fix For: 5.9.0 > > > For lease database locker the lockKeepAlivePeriod property is the peroid to > renew the lease and lockAcquireSleepInterval is the amount for lease > extension.Renaming them to leaseRenewPeroid and leaseDuration respectively > brings more intuition and readability. > Besides, leaseDuration should be greater than leaseRenewPeroid to avoid > unnecessary master/slave switching. > The users should be aware of unproper configuration via warning log. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4701) NIO transport performance for ActiveMQ
[ https://issues.apache.org/jira/browse/AMQ-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774390#comment-13774390 ] Anuj Khandelwal commented on AMQ-4701: -- I have provided my configuration and test results. Can someone from ActiveMQ developers team help me with this. As Timothy said it reduces clients for large number of clients, So can you please specify what should be this large value. I have tried with 20 clients. After how many clients nio starts reducing threads ? Thanks, Anuj > NIO transport performance for ActiveMQ > -- > > Key: AMQ-4701 > URL: https://issues.apache.org/jira/browse/AMQ-4701 > Project: ActiveMQ > Issue Type: Test > Components: Performance Test, Transport >Affects Versions: 5.8.0 >Reporter: Anuj Khandelwal > > Hi, > I am using 5.8.0 version of ActiveMQ. I am trying to use NIO to improve > performance and scalability of my ActiveMQ broker but it is not working well. > I was expecting that it should reduce number of threads but I have not > observed any changes in number of threads. It is even reducing the > throughput. > I have made changes in broker's configuration file as specified > http://activemq.apache.org/configuring-transports.html > Can somebody help me here. > Thanks, > Anuj -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (AMQ-4701) NIO transport performance for ActiveMQ
[ https://issues.apache.org/jira/browse/AMQ-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anuj Khandelwal reopened AMQ-4701: -- > NIO transport performance for ActiveMQ > -- > > Key: AMQ-4701 > URL: https://issues.apache.org/jira/browse/AMQ-4701 > Project: ActiveMQ > Issue Type: Test > Components: Performance Test, Transport >Affects Versions: 5.8.0 >Reporter: Anuj Khandelwal > > Hi, > I am using 5.8.0 version of ActiveMQ. I am trying to use NIO to improve > performance and scalability of my ActiveMQ broker but it is not working well. > I was expecting that it should reduce number of threads but I have not > observed any changes in number of threads. It is even reducing the > throughput. > I have made changes in broker's configuration file as specified > http://activemq.apache.org/configuring-transports.html > Can somebody help me here. > Thanks, > Anuj -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: how to override policyEntry for a given set of queues?
Yes that should work. Regards, Torsten Mielke tmie...@redhat.com tmielke.blogspot.com On Sep 20, 2013, at 2:28 PM, damu wrote: > Hi, > > I want to define a default policyEntry fro all queues and override the > behavior for a given set of queues using wild card. Will it work if I repeat > the policy entry definition like below? > > memoryLimit="1mb"> > > > producerFlowControl="true" memoryLimit="1mb"> > > > > > > Thanks for any help on this > > Damu > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/how-to-override-policyEntry-for-a-given-set-of-queues-tp4671692.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
