Re: Kahadb - Getting Worried Message

Congrats on getting ActiveMQ into production! That warning, although it's not clear from the message, indicates that the store limit is too high for the amount of space available on the disk and won't prevent running out of disk space -- at least, if I'm reading the code correctly.

Re: [VOTE] Apache ActiveMQ 5.9.1 release

No, there's much more, I have to finish updating that. As I said in the vote mail, I'll follow up with another email once that's done. Hadrian On Tuesday 01 April 2014 20:18:54 ryan segura wrote: > Just to confirm -- the only bug fixes are those in the release notes? It > does not appear to be

Re: [VOTE] Apache ActiveMQ 5.9.1 release

Just to confirm -- the only bug fixes are those in the release notes? It does not appear to be many -- View this message in context: http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-9-1-release-tp4679806p4679833.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: Contributing a configuration on the connectivity page

There is no process per se. If you create an account on the activemq wiki and submit an icla to the ASF you would become officially a contributor and could edit it yourself. The alternative would be to provide the content (on the list or in a patch) and then one of the community member will upda

Re: ActiveMQ 5.10 release date?

Ryan, I built the 5.9.1 candidate yesterday, it's currently under vote. Community involvement is always highly appreciated. Please feel free to test the release candidate in your environment (see the vote thread for location of the staged distro). Thanks, Hadrian On Tuesday 01 April 2014 01:

ActiveMq Encypted Passwords

Hello, I'm having a problem getting the property replacement to work when setting up the encrypted passwords to access my data source. I've been following the instructions here; http://activemq.apache.org/encrypted-passwords.html Maybe my understanding of this is not correct, but I was expecting

Kahadb - Getting Worried Message

Hi everybody, Recently We implemented in production a ActiveMQServer. (It has 5 days working),everything was perfect but today I saw in the hawtio-JMX Web Console the following message(property health/current status): "Getting Worried {org.apache.activemq.FreeDiskSpaceLeft: WARNING Store limit is

[jira] [Commented] (AMQNET-454) Add Apache Qpid provider to NMS

[ https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956929#comment-13956929 ] Timothy Bish commented on AMQNET-454: - All new patch applied without issue. > Add Ap

[jira] [Updated] (AMQNET-454) Add Apache Qpid provider to NMS

[ https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke updated AMQNET-454: --- Attachment: Apache.NMS.AMQP-23e-addFilesToTestProject.patch Apache.NMS.AMQP-23d-addTra

[jira] [Comment Edited] (AMQ-4920) AmqpErrorException occurs with multiple concurrent amqp topic consumers

[ https://issues.apache.org/jira/browse/AMQ-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956818#comment-13956818 ] Gurinder edited comment on AMQ-4920 at 4/1/14 6:02 PM: --- So essentially

[jira] [Commented] (AMQ-4920) AmqpErrorException occurs with multiple concurrent amqp topic consumers

[ https://issues.apache.org/jira/browse/AMQ-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956818#comment-13956818 ] Gurinder commented on AMQ-4920: --- So essentially multiple topic consumers even running from dif

Re: [VOTE] Apache ActiveMQ 5.9.1 release

I really appreciate this minor release. Last minor releases were caused by legal issues two years ago. +1 (non binding) Checked console and admin script. Cheers, Łukasz Dywicki -- l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-house.org Wiadomość napisan

Re: [VOTE] Apache ActiveMQ 5.9.1 release

Tested binary and console basic functionality. +1 - Non binding. On Apr 1, 2014, at 10:14 AM, Hadrian Zbarcea wrote: > Hi all, > > I've cut a release candidate for the 5.9.1 patch release. > I have to update JIRA today to determine the exact number of issues resolved > and follow up with anoth

[jira] [Updated] (AMQ-4767) Extend ActiveMQ Camel component to support INDIVIDUAL_MESSAGE ack mode

[ https://issues.apache.org/jira/browse/AMQ-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated AMQ-4767: - Fix Version/s: (was: 5.10.0) 5.11.0 > Extend ActiveMQ Camel component to support IND

[jira] [Commented] (AMQ-3725) Kahadb error during SAN failover delayed write - Allow kahaDB to recover in a similar manner as the JDBC store using the IOExceptionHandler

[ https://issues.apache.org/jira/browse/AMQ-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956663#comment-13956663 ] Claus Ibsen commented on AMQ-3725: -- [~dejanb] should we assume this is fixed and close the

[jira] [Updated] (AMQ-3725) Kahadb error during SAN failover delayed write - Allow kahaDB to recover in a similar manner as the JDBC store using the IOExceptionHandler

[ https://issues.apache.org/jira/browse/AMQ-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated AMQ-3725: - Assignee: Dejan Bosanac > Kahadb error during SAN failover delayed write - Allow kahaDB to recover in a >

[jira] [Commented] (AMQ-3725) Kahadb error during SAN failover delayed write - Allow kahaDB to recover in a similar manner as the JDBC store using the IOExceptionHandler

[ https://issues.apache.org/jira/browse/AMQ-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956662#comment-13956662 ] Claus Ibsen commented on AMQ-3725: -- Did anyone test the SNAPSHOT with a fix > Kahadb error

[jira] [Commented] (AMQ-5077) Improve performance of ConcurrentStoreAndDispatch

[ https://issues.apache.org/jira/browse/AMQ-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956570#comment-13956570 ] Richard Wagg commented on AMQ-5077: --- Hi, I'm happy that those 2 changes would help the pro

[VOTE] Apache ActiveMQ 5.9.1 release

Hi all, I've cut a release candidate for the 5.9.1 patch release. I have to update JIRA today to determine the exact number of issues resolved and follow up with another email. This patch release is focused on fixes related to leveldb, a security update for the camel dependency and moving back

[jira] [Commented] (AMQ-5077) Improve performance of ConcurrentStoreAndDispatch

[ https://issues.apache.org/jira/browse/AMQ-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956461#comment-13956461 ] Gary Tully commented on AMQ-5077: - ahh sorry, you are correct, the CompositeDestinationFilte

[jira] [Commented] (AMQ-5109) "Soft deadlock" in TransportConnection causes degraded performance in certain situations

[ https://issues.apache.org/jira/browse/AMQ-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956435#comment-13956435 ] Gary Tully commented on AMQ-5109: - this may provide a test case - seems to be the same issue

Re: Contributing a configuration on the connectivity page

Anyone ? 2014-03-25 15:28 GMT+01:00 William Drai : > Hi, > > What is the process to contribute a configuration example on this > page > . > GraniteDS is a project similar to BlazeDS referenced > here which >

[jira] [Created] (AMQCPP-537) CLONE - verify the admin login functionality using login credentials

ram created AMQCPP-537: -- Summary: CLONE - verify the admin login functionality using login credentials Key: AMQCPP-537 URL: https://issues.apache.org/jira/browse/AMQCPP-537 Project: ActiveMQ C++ Client

[jira] [Updated] (AMQCPP-536) verify the admin login functionality using login credentials

[ https://issues.apache.org/jira/browse/AMQCPP-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ram updated AMQCPP-536: --- Regression: Regression > verify the admin login functionality using login credentials > -

[jira] [Updated] (AMQCPP-536) verify the admin login functionality using login credentials

[ https://issues.apache.org/jira/browse/AMQCPP-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ram updated AMQCPP-536: --- Summary: verify the admin login functionality using login credentials (was: verify the admin login functionality) >

[jira] [Created] (AMQCPP-536) verify the admin login functionality

ram created AMQCPP-536: -- Summary: verify the admin login functionality Key: AMQCPP-536 URL: https://issues.apache.org/jira/browse/AMQCPP-536 Project: ActiveMQ C++ Client Issue Type: Bug Compon

Re: [jira] [Commented] (AMQ-4955) TCP Connections and related thread leak.

I think it should cause the connection to die. The subs currently don't deal with a dispatch failure wrt stats and redelivery so the only safe thing to do is termination. On 1 Apr 2014 06:28, "Arthur Naseef (JIRA)" wrote: > > [ > https://issues.apache.org/jira/browse/AMQ-4955?page=com.atlassi

Re: git commit: Update spring.schemas for the 5.9.1 release

It seems odd to me that a point release would require a new schema. What change demands this? Is it backwards compatible with an existing xsd? On 31 Mar 2014 23:56, wrote: > Repository: activemq > Updated Branches: > refs/heads/trunk ed11b067c -> 997bbb7a0 > > > Update spring.schemas for the 5.

[jira] [Resolved] (AMQ-2354) Default the ServerUrl to vm://brokerName?create=false when an embedded broker is specified with brokerXmlConfig

[ https://issues.apache.org/jira/browse/AMQ-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved AMQ-2354. -- Resolution: Fixed Thanks for the patch. Well we made it before 5 years :) > Default the ServerUrl to vm: