Re: [VOTE] Release Apache ActiveMQ 5.10.1 (3rd attempt)

[Jean-Baptiste Onofré]

+1 (non binding)

Regards
JB


 Original message 
From: Claus Ibsen  
Date:16/01/2015  08:02  (GMT+01:00) 
To: dev@activemq.apache.org 
Cc:  
Subject: Re: [VOTE] Release Apache ActiveMQ 5.10.1 (3rd attempt) 

Hi

I gave the RC a test spin with latest Camel source code.
And the spring XSD schema 5.10.1 is included.

+1




On Thu, Jan 15, 2015 at 6:10 PM, artnaseef  wrote:
> The release candidate for the activemq 5.10.1 release is now built and ready
> for a vote.
> This release comes with 34 fixes and 1 administrative jira entry.
>
> Please see the list of jira entries here:
> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%205.10.1%20AND%20project%20%3D%20AMQ
>
>
> You can get binary distributions here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1013/org/apache/activemq/apache-activemq/5.10.1/
>
>
> Source archives are here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1013/org/apache/activemq/activemq-parent/5.10.1/
>
>
> Maven2 repository is here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1013/
>
> Source tag:
> https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=8938d14d434447193b02ba635606aa0fb7a80353
>
>
> NOTE: I used Hadrian's prior thread as a template (thank you Hadrian).
>
>
>
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/VOTE-Release-Apache-ActiveMQ-5-10-1-3rd-attempt-tp4689959.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/

Re: [VOTE] Release Apache ActiveMQ 5.10.1 (3rd attempt)

[Claus Ibsen]

Hi

I gave the RC a test spin with latest Camel source code.
And the spring XSD schema 5.10.1 is included.

+1




On Thu, Jan 15, 2015 at 6:10 PM, artnaseef  wrote:
> The release candidate for the activemq 5.10.1 release is now built and ready
> for a vote.
> This release comes with 34 fixes and 1 administrative jira entry.
>
> Please see the list of jira entries here:
> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%205.10.1%20AND%20project%20%3D%20AMQ
>
>
> You can get binary distributions here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1013/org/apache/activemq/apache-activemq/5.10.1/
>
>
> Source archives are here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1013/org/apache/activemq/activemq-parent/5.10.1/
>
>
> Maven2 repository is here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1013/
>
> Source tag:
> https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=8938d14d434447193b02ba635606aa0fb7a80353
>
>
> NOTE: I used Hadrian's prior thread as a template (thank you Hadrian).
>
>
>
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/VOTE-Release-Apache-ActiveMQ-5-10-1-3rd-attempt-tp4689959.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/

[jira] [Created] (ACTIVEMQ6-70) Implement resource limits

[Michael Cressman (JIRA)]

Michael Cressman created ACTIVEMQ6-70:
-

 Summary: Implement resource limits
 Key: ACTIVEMQ6-70
 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-70
 Project: Apache ActiveMQ 6
  Issue Type: New Feature
Reporter: Michael Cressman


Implement various resource limits within the system:
- overall number of connections
- connections per user
- connections per IP address
- queues per user
- (possibly: number of sessions, number of subscriptions per user)

The "per user" limits can be a default maximum for everyone plus specific 
limits for particular users.

Other things:
- limit the max queue size a user can create
- limit the names a user may call a queue that he creates

To see how MRG-M handles this, see the documentation on Authorization using ACL 
and quotas:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_MRG/3/html-single/Messaging_Installation_and_Configuration_Guide/index.html#sect-Authorization



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: AMQ2149LevelDBTest failures

[artnaseef]

Hmm, maybe this logic is faulty for Topics:



For Topics, the messages being delivered elsewhere is beside the point,
right?  I'm basing this conclusion in large part on the comment stating that
"messages have been dispatched else where".



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/AMQ2149LevelDBTest-failures-tp4690010p4690011.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

AMQ2149LevelDBTest failures

[artnaseef]

Attempting to track down failures in AMQ2149LevelDBTest, I noticed the
following (from here:
https://builds.apache.org/job/ActiveMQ-Java7/org.apache.activemq$activemq-unit-tests/574/testReport/org.apache.activemq.bugs/AMQ2149LevelDBTest/testTopicTransactionalOrderWithRestart/).

Anyone recognize what's going on here?  That is, why is the
ActiveMQMessageConsumer forcing a roll back?  I suspect this is the cause of
the test failures as the test is making sure no messages are lost and that
they are delivered in order.





--
View this message in context: 
http://activemq.2283324.n4.nabble.com/AMQ2149LevelDBTest-failures-tp4690010.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Build failed in Jenkins: ActiveMQ-Trunk-Deploy #1196

[Apache Jenkins Server]

See 

Changes:

[dkulp] Get more tests passing with Jetty9

--
[...truncated 8641 lines...]
Archived 1 artifacts
Archive block size is 32768
Received 0 blocks and 13847 bytes
Compression is 0.0%
Took 0.33 sec
[JENKINS] Archiving 

 to 
org.apache.activemq.tooling/activemq-memtest-maven-plugin/5.11-SNAPSHOT/activemq-memtest-maven-plugin-5.11-SNAPSHOT.pom
Sending artifact delta relative to ActiveMQ-Trunk-Deploy » ActiveMQ :: Memory 
Usage Test Plugin #1194
Archived 1 artifacts
Archive block size is 32768
Received 0 blocks and 2841 bytes
Compression is 0.0%
Took 0.22 sec
[JENKINS] Archiving 

 to 
org.apache.activemq.tooling/activemq-perf-maven-plugin/5.11-SNAPSHOT/activemq-perf-maven-plugin-5.11-SNAPSHOT.pom
Sending artifact delta relative to ActiveMQ-Trunk-Deploy » ActiveMQ :: 
Performance Test Plugin #1194
Archived 1 artifacts
Archive block size is 32768
Received 0 blocks and 3117 bytes
Compression is 0.0%
Took 0.27 sec
[JENKINS] Archiving 
 
to 
org.apache.activemq/activemq-amqp/5.11-SNAPSHOT/activemq-amqp-5.11-SNAPSHOT.pom
Sending artifact delta relative to ActiveMQ-Trunk-Deploy » ActiveMQ :: AMQP 
#1194
Archived 1 artifacts
Archive block size is 32768
Received 0 blocks and 8049 bytes
Compression is 0.0%
Took 0.23 sec
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-itests-spring31/5.11-SNAPSHOT/activemq-itests-spring31-5.11-SNAPSHOT.pom
Sending artifact delta relative to ActiveMQ-Trunk-Deploy » ActiveMQ :: 
Integration Test :: Spring 3.1 #1194
Archived 1 artifacts
Archive block size is 32768
Received 0 blocks and 3005 bytes
Compression is 0.0%
Took 0.23 sec
[JENKINS] Archiving 
 to 
org.apache.activemq/apache-activemq/5.11-SNAPSHOT/apache-activemq-5.11-SNAPSHOT.pom
Sending artifact delta relative to ActiveMQ-Trunk-Deploy » ActiveMQ :: Assembly 
#1194
Archived 1 artifacts
Archive block size is 32768
Received 0 blocks and 18443 bytes
Compression is 0.0%
Took 1.9 sec
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-jms-pool/5.11-SNAPSHOT/activemq-jms-pool-5.11-SNAPSHOT.pom
Sending artifact delta relative to ActiveMQ-Trunk-Deploy » ActiveMQ :: Generic 
JMS Pool #1194
Archived 1 artifacts
Archive block size is 32768
Received 0 blocks and 3814 bytes
Compression is 0.0%
Took 0.23 sec
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-log4j-appender/5.11-SNAPSHOT/activemq-log4j-appender-5.11-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-log4j-appender/5.11-20150116.032639-206/activemq-log4j-appender-5.11-20150116.032639-206.jar
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-log4j-appender/5.11-20150116.032639-206/activemq-log4j-appender-5.11-20150116.032639-206-sources.jar
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-log4j-appender/5.11-20150116.032639-206/activemq-log4j-appender-5.11-20150116.032639-206-javadoc.jar
Sending artifact delta relative to ActiveMQ-Trunk-Deploy » ActiveMQ :: Log4j 
Appender #1194
Archived 4 artifacts
Archive block size is 32768
Received 0 blocks and 93469 bytes
Compression is 0.0%
Took 0.42 sec
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-runtime-config/5.11-SNAPSHOT/activemq-runtime-config-5.11-SNAPSHOT.pom
Sending artifact delta relative to ActiveMQ-Trunk-Deploy » ActiveMQ :: Runtime 
Configuration #1194
Archived 1 artifacts
Archive block size is 32768
Received 0 blocks and 6523 bytes
Compression is 0.0%
Took 0.86 sec
[JENKINS] Archiving 
 
to 
org.apache.activemq/activemq-pool/5.11-SNAPSHOT/activemq-pool-5.11-SNAPSHOT.pom
Sending artifact delta relative to ActiveMQ-Trunk-Deploy » ActiveMQ :: Pool 
#1194
Archived 1 artifacts
Archive block size is 32768
Received 0 blocks and 3783 bytes
Compression is 0.0%
Took 0.24 sec
[JENKINS] Arc

Build failed in Jenkins: ActiveMQ-Trunk-Deploy » ActiveMQ :: KahaDB Store #1196

[Apache Jenkins Server]

See 


--
[...truncated 391 lines...]
Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

[jira] [Created] (AMQ-5522) Limit the number of messages in individual queues instead of, or in addition to, limiting memory and store usage

[Arthur Naseef (JIRA)]

Arthur Naseef created AMQ-5522:
--

 Summary: Limit the number of messages in individual queues instead 
of, or in addition to, limiting memory and store usage
 Key: AMQ-5522
 URL: https://issues.apache.org/jira/browse/AMQ-5522
 Project: ActiveMQ
  Issue Type: New Feature
Reporter: Arthur Naseef
Priority: Minor


Sometimes it is easier to administer and communicate broker limits using a 
maximum number of messages per queue rather than using memory and store percent 
usage.

Being able to set the limit, in numbers of messages, would meet this need.  It 
could be in place of, or (preferably) in addition to the existing memory and 
store usage limits.  The effect would be the same - triggering producer flow 
control.

See this discussion: 
http://activemq.2283324.n4.nabble.com/How-to-limit-queue-depth-by-msgs-td4689633.html




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMQ-5521) Average message size attribute on destination mbean should not have decimals

[Tim Bain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim Bain updated AMQ-5521:
--
  Description: 
Under AMQ-4831, we introduced rounding on the AverageMessageSize attribute of 
BrokerViewMBean, but the same change wasn't applied to the same attribute on 
DestinationViewMBean so the two are inconsistent.  If the change was worth 
making, it should be made both places.



  was:
This doesn't look very nice when looking from a jmx console such as hawtio.

See screenshot, and notice the many decimals the average message size attribute 
has.



Fix Version/s: (was: 5.10.0)

> Average message size attribute on destination mbean should not have decimals
> 
>
> Key: AMQ-5521
> URL: https://issues.apache.org/jira/browse/AMQ-5521
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: Broker, JMX
>Affects Versions: 5.9.0
>Reporter: Tim Bain
>Assignee: Claus Ibsen
>Priority: Minor
>
> Under AMQ-4831, we introduced rounding on the AverageMessageSize attribute of 
> BrokerViewMBean, but the same change wasn't applied to the same attribute on 
> DestinationViewMBean so the two are inconsistent.  If the change was worth 
> making, it should be made both places.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMQ-5521) Average message size attribute on destination mbean should not have decimals

[Tim Bain (JIRA)]

Tim Bain created AMQ-5521:
-

 Summary: Average message size attribute on destination mbean 
should not have decimals
 Key: AMQ-5521
 URL: https://issues.apache.org/jira/browse/AMQ-5521
 Project: ActiveMQ
  Issue Type: Improvement
  Components: Broker, JMX
Affects Versions: 5.9.0
Reporter: Tim Bain
Assignee: Claus Ibsen
Priority: Minor
 Fix For: 5.10.0


This doesn't look very nice when looking from a jmx console such as hawtio.

See screenshot, and notice the many decimals the average message size attribute 
has.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Build failed in Jenkins: ActiveMQ-Trunk-Deploy #1195

[Apache Jenkins Server]

See 

--
Started by timer
Building remotely on ubuntu-4 (docker Ubuntu ubuntu4 ubuntu) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/activemq.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/activemq.git
 > git --version # timeout=10
FATAL: Failed to fetch from https://git-wip-us.apache.org/repos/asf/activemq.git
hudson.plugins.git.GitException: Failed to fetch from 
https://git-wip-us.apache.org/repos/asf/activemq.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:647)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:889)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:914)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1252)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:615)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:524)
at hudson.model.Run.execute(Run.java:1706)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:232)
Caused by: hudson.plugins.git.GitException: Failed to connect to 
https://git-wip-us.apache.org/repos/asf/activemq.git (exception: 
org.apache.http.conn.HttpHostConnectException: Connect to 
git-wip-us.apache.org:443 [git-wip-us.apache.org/140.211.11.23] failed: 
Connection refused)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkCredentials(CliGitAPIImpl.java:2253)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1169)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:85)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:280)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

Release signers. [WAS] Release Apache ActiveMQ 5.10.1 (3rd attempt)

[Hiram Chirino]

Changed subject to avoid hijacking the vote thread.

I think it's fine if Arthur signs the release since his key is in the KEYS file:
https://github.com/apache/activemq/blob/activemq-5.10.1/KEYS

The PMC has final control if the release is accepted or not after all.
I don't want to discourage any committers from attempting to do RCs
and signing them.  Cutting RC's is laborious and as a result it's
something this project does not do nearly enough.

Regards,
Hiram

On Thu, Jan 15, 2015 at 12:23 PM, James Carman
 wrote:
> -0, I would prefer to see the releases signed by a PMC member.
>
> On Thu, Jan 15, 2015 at 12:10 PM, artnaseef  wrote:
>> The release candidate for the activemq 5.10.1 release is now built and ready
>> for a vote.
>> This release comes with 34 fixes and 1 administrative jira entry.
>>
>> Please see the list of jira entries here:
>> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%205.10.1%20AND%20project%20%3D%20AMQ
>>
>>
>> You can get binary distributions here:
>> https://repository.apache.org/content/repositories/orgapacheactivemq-1013/org/apache/activemq/apache-activemq/5.10.1/
>>
>>
>> Source archives are here:
>> https://repository.apache.org/content/repositories/orgapacheactivemq-1013/org/apache/activemq/activemq-parent/5.10.1/
>>
>>
>> Maven2 repository is here:
>> https://repository.apache.org/content/repositories/orgapacheactivemq-1013/
>>
>> Source tag:
>> https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=8938d14d434447193b02ba635606aa0fb7a80353
>>
>>
>> NOTE: I used Hadrian's prior thread as a template (thank you Hadrian).
>>
>>
>>
>> --
>> View this message in context: 
>> http://activemq.2283324.n4.nabble.com/VOTE-Release-Apache-ActiveMQ-5-10-1-3rd-attempt-tp4689959.html
>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.



-- 
Hiram Chirino
Engineering | Red Hat, Inc.
hchir...@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino

[jira] [Resolved] (AMQ-5517) Support for Jetty 9

[Daniel Kulp (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Kulp resolved AMQ-5517.
--
Resolution: Done


All the tests except the activemq-web-demo now pass when run with Jetty9.   The 
web-demo uses Jetty 8 specific classes for the request/response and will 
require a significant amount of work to port to Jetty9.

> Support for Jetty 9
> ---
>
> Key: AMQ-5517
> URL: https://issues.apache.org/jira/browse/AMQ-5517
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Transport
>Reporter: Daniel Kulp
>Assignee: Daniel Kulp
> Fix For: 5.11.0
>
>
> With jetty 8 and jetty 7 going EOL and no longer receiving security updates, 
> we need to support running with Jetty 9 as an option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache ActiveMQ 5.10.1 (3rd attempt)

[James Carman]

-0, I would prefer to see the releases signed by a PMC member.

On Thu, Jan 15, 2015 at 12:10 PM, artnaseef  wrote:
> The release candidate for the activemq 5.10.1 release is now built and ready
> for a vote.
> This release comes with 34 fixes and 1 administrative jira entry.
>
> Please see the list of jira entries here:
> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%205.10.1%20AND%20project%20%3D%20AMQ
>
>
> You can get binary distributions here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1013/org/apache/activemq/apache-activemq/5.10.1/
>
>
> Source archives are here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1013/org/apache/activemq/activemq-parent/5.10.1/
>
>
> Maven2 repository is here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1013/
>
> Source tag:
> https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=8938d14d434447193b02ba635606aa0fb7a80353
>
>
> NOTE: I used Hadrian's prior thread as a template (thank you Hadrian).
>
>
>
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/VOTE-Release-Apache-ActiveMQ-5-10-1-3rd-attempt-tp4689959.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

[jira] [Commented] (ACTIVEMQ6-67) clean up configuration files

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ACTIVEMQ6-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278964#comment-14278964
 ] 

ASF GitHub Bot commented on ACTIVEMQ6-67:
-

Github user asfgit closed the pull request at:

https://github.com/apache/activemq-6/pull/63


> clean up configuration files
> 
>
> Key: ACTIVEMQ6-67
> URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-67
> Project: Apache ActiveMQ 6
>  Issue Type: Task
>Reporter: Andy Taylor
>Assignee: Andy Taylor
> Fix For: 6.0.0
>
>
> The configuration files and parsers need consolidating to be cleaner, that is 
> the main and configuration file should be combined and the securty bootstrap 
> needs fixing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] activemq-6 pull request: ACTIVEMQ6-67 - cleaned up configuration

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/activemq-6/pull/63


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[VOTE] Release Apache ActiveMQ 5.10.1 (3rd attempt)

[artnaseef]

The release candidate for the activemq 5.10.1 release is now built and ready
for a vote.
This release comes with 34 fixes and 1 administrative jira entry.

Please see the list of jira entries here:
https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%205.10.1%20AND%20project%20%3D%20AMQ
  


You can get binary distributions here: 
https://repository.apache.org/content/repositories/orgapacheactivemq-1013/org/apache/activemq/apache-activemq/5.10.1/
  


Source archives are here: 
https://repository.apache.org/content/repositories/orgapacheactivemq-1013/org/apache/activemq/activemq-parent/5.10.1/
  


Maven2 repository is here: 
https://repository.apache.org/content/repositories/orgapacheactivemq-1013/

Source tag: 
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=8938d14d434447193b02ba635606aa0fb7a80353


NOTE: I used Hadrian's prior thread as a template (thank you Hadrian).



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/VOTE-Release-Apache-ActiveMQ-5-10-1-3rd-attempt-tp4689959.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

[jira] [Resolved] (AMQ-5514) Create Release 5.10.1

[Arthur Naseef (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arthur Naseef resolved AMQ-5514.

   Resolution: Done
Fix Version/s: 5.10.1

Work to prepare the 5.10.1 release is complete.

> Create Release 5.10.1
> -
>
> Key: AMQ-5514
> URL: https://issues.apache.org/jira/browse/AMQ-5514
> Project: ActiveMQ
>  Issue Type: Bug
>Reporter: Arthur Naseef
>Assignee: Arthur Naseef
>Priority: Trivial
> Fix For: 5.10.1
>
>
> Minor updates for the 5.10.1 release are included here.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (AMQ-5514) Create Release 5.10.1

[Arthur Naseef (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arthur Naseef reassigned AMQ-5514:
--

Assignee: Arthur Naseef

> Create Release 5.10.1
> -
>
> Key: AMQ-5514
> URL: https://issues.apache.org/jira/browse/AMQ-5514
> Project: ActiveMQ
>  Issue Type: Bug
>Reporter: Arthur Naseef
>Assignee: Arthur Naseef
>Priority: Trivial
>
> Minor updates for the 5.10.1 release are included here.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[RESULT][VOTE] Release Apache.NMS.ActiveMQ 1.7.0

[Timothy Bish]

Results of the NMS.ActiveMQ 1.7.0 vote:

Vote passes with 6 +1 and no other votes.

The following votes were received:

Jim Gomes
Gary Tully
Claus Ibsen
Art Naseef
Timothy Bish
Hiram Chirino

I'll start pushing out the release bundles and update the Wiki.

Regards

--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/

[jira] [Commented] (AMQ-3692) ActiveMQ OSGi bundle should be stopped when broker stops itself

[metatech (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278518#comment-14278518
 ] 

metatech commented on AMQ-3692:
---

Here is a workaround that allows to use the Blueprint XBean syntax, with 
"blueprint.aries.xml-validation:=false".
I did not find how to enhance the validator to allow it yet.
{code}
http://www.osgi.org/xmlns/blueprint/v1.0.0";
   
xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0";
   
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0";
   xmlns:amq="http://activemq.apache.org/schema/core";
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
   xsi:schemaLocation="
http://www.osgi.org/xmlns/blueprint/v1.0.0 
http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
http://activemq.apache.org/schema/core 
http://activemq.apache.org/schema/core/activemq-core-5.5.0.xsd";
>

Bundle-SymbolicName: activemq-broker.xml; 
blueprint.aries.xml-validation:=false





http://www.osgi.org/xmlns/blueprint/v1.0.0";>






{code}

Without it, the error is the following in ServiceMix 4.5.3 : 

{code}
Unable to start blueprint container for bundle activemq-broker.xml
org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to 
validate xml
at org.apache.aries.blueprint.container.Parser.validate(Parser.java:288)
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:281)
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:230)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching 
wildcard is strict, but no declaration can be found for element 'bean'.
{code}



> ActiveMQ OSGi bundle should be stopped when broker stops itself
> ---
>
> Key: AMQ-3692
> URL: https://issues.apache.org/jira/browse/AMQ-3692
> Project: ActiveMQ
>  Issue Type: New Feature
>  Components: Broker
>Affects Versions: 5.4.2
> Environment: ServiceMix 4.3
>Reporter: metatech
>Assignee: Hiram Chirino
> Fix For: 5.9.0
>
> Attachments: BrokerBundleWatcher.patch, BrokerBundleWatcher_v2.patch, 
> BrokerBundleWatcher_v3.patch, BrokerService.patch, activemq-broker.xml
>
>
> In case of error, the ActiveMQ broker can stop itself.
> In an OSGi/Blueprint environment, the bundle is however still in 
> Active/Created state, which misleads an external monitoring software into 
> thinking that the broker is running fine.
> This patch stops the bundle when the broker stops itself.
> This patch can also auto-restart the bundle, which will restart the broker.
> This is critical in an Master/Slave configuration : when the connection to 
> the database is lost, the broker cannot maintain the DB exclusive lock, and 
> it stops itself.  The bundle should be stopped and started again, so that it 
> enters again the "Creating" state, in which it waits to obtain the DB lock 
> again.
> The class "BrokerBundleWatcher" needs to be registered with the 
> "shutdownHooks" property of the ActiveMQ "BrokerService".  However, there is 
> a limitation with the XBean syntax in a Blueprint XML, which does not allow 
> to define inner beans.  The workaround is to define the "activemq-broker.xml" 
> in full native Blueprint syntax (no XBean).
> The patch also provides a modified version of the BrokerService, that injects 
> its own reference into the ShutdownHook's which implement the 
> "BrokerServiceAware" interface.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (AMQ-5249) "cursor got duplicate" error after upgrade

[Sergiy Barlabanov (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278500#comment-14278500
 ] 

Sergiy Barlabanov edited comment on AMQ-5249 at 1/15/15 9:51 AM:
-

In our case after getting quite a lot of "cursor got duplicate" in a DQL, we 
start to observe "Problem retrieving message for browse" error with 
NullPointerException for that DLQ when trying to browse the queue. Restart 
helps.

2015-01-14 20:26:00,659 | ERROR | Problem retrieving message for browse | 
org.apache.activemq.broker.region.Queue | ActiveMQ Broker[dcdng] Scheduler
java.lang.NullPointerException


was (Author: barlabanov):
In our case after getting "cursor got duplicate" in a DQL, we start to observe 
"Problem retrieving message for browse" error with NullPointerException for 
that DLQ when trying to browse the queue. Restart helps.

2015-01-14 20:26:00,659 | ERROR | Problem retrieving message for browse | 
org.apache.activemq.broker.region.Queue | ActiveMQ Broker[dcdng] Scheduler
java.lang.NullPointerException

> "cursor got duplicate" error after upgrade
> --
>
> Key: AMQ-5249
> URL: https://issues.apache.org/jira/browse/AMQ-5249
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.1, 5.10.0
>Reporter: Rural Hunter
>
> I was using 5.9.0 and meet one problem so I tried to upgrade activemq. I 
> tried both 5.9.1 and 5.10.0 and encouterred a same problem. I saw messages 
> filled DLQ very quickly. I checked the clients both producer and consumer but 
> there was no error. I checked activemq log and found the log is full of these 
> warnings:
> 2014-06-27 23:22:09,337 | WARN  | 
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com.cyyun.webmon.spider.update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
>  - cursor got duplicate: ID:211.com-52399-1400732399425-1:1:235992:1:1, 4 | 
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ 
> Broker[localhost] Scheduler
> 2014-06-27 23:22:09,337 | WARN  | 
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com..update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
>  - cursor got duplicate: ID:nbzjjf22805-34129-1403880308671-1:1:28:1:1, 4 | 
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ 
> Broker[localhost] Scheduler
> 2014-06-27 23:22:09,338 | WARN  | 
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com.x.update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
>  - cursor got duplicate: ID:jxncxnj2-48598-1403856107346-1:1:6007:1:1, 4 | 
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ 
> Broker[localhost] Scheduler
> 2014-06-27 23:22:09,338 | WARN  | 
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com..update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
>  - cursor got duplicate: ID:jxnc17-60227-1400730816361-1:1:149072:1:1, 4 | 
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ 
> Broker[localhost] Scheduler
> 2014-06-27 23:22:09,339 | WARN  | 
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com..update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
>  - cursor got duplicate: ID:cyyun-46954-1403800808565-1:1:9765:1:1, 4 | 
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ 
> Broker[localhost] Scheduler
> 2014-06-27 23:22:09,339 | WARN  | 
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com..update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
>  - cursor got duplicate: ID:ubuntu-55495-1403497638437-1:1:53086:1:1, 4 | 
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ 
> Broker[localhost] Scheduler
> 2014-06-27 23:22:09,340 | WARN  | 
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com..update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
>  - cursor got duplicate: ID:cyyun-39030-1403880008363-1:1:70:1:1, 4 | 
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ 
> Broker[localhost] Scheduler
> The problem mostly happens right after activemq starts and sometimes happened 
> after activemq worked normally for a while.
> For now I have to roll back to 5.9.0 and the problem doesn't occure.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-5249) "cursor got duplicate" error after upgrade

[Sergiy Barlabanov (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278500#comment-14278500
 ] 

Sergiy Barlabanov commented on AMQ-5249:


In our case after getting "cursor got duplicate" in a DQL, we start to observe 
"Problem retrieving message for browse" error with NullPointerException for 
that DLQ when trying to browse the queue. Restart helps.

2015-01-14 20:26:00,659 | ERROR | Problem retrieving message for browse | 
org.apache.activemq.broker.region.Queue | ActiveMQ Broker[dcdng] Scheduler
java.lang.NullPointerException

> "cursor got duplicate" error after upgrade
> --
>
> Key: AMQ-5249
> URL: https://issues.apache.org/jira/browse/AMQ-5249
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.1, 5.10.0
>Reporter: Rural Hunter
>
> I was using 5.9.0 and meet one problem so I tried to upgrade activemq. I 
> tried both 5.9.1 and 5.10.0 and encouterred a same problem. I saw messages 
> filled DLQ very quickly. I checked the clients both producer and consumer but 
> there was no error. I checked activemq log and found the log is full of these 
> warnings:
> 2014-06-27 23:22:09,337 | WARN  | 
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com.cyyun.webmon.spider.update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
>  - cursor got duplicate: ID:211.com-52399-1400732399425-1:1:235992:1:1, 4 | 
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ 
> Broker[localhost] Scheduler
> 2014-06-27 23:22:09,337 | WARN  | 
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com..update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
>  - cursor got duplicate: ID:nbzjjf22805-34129-1403880308671-1:1:28:1:1, 4 | 
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ 
> Broker[localhost] Scheduler
> 2014-06-27 23:22:09,338 | WARN  | 
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com.x.update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
>  - cursor got duplicate: ID:jxncxnj2-48598-1403856107346-1:1:6007:1:1, 4 | 
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ 
> Broker[localhost] Scheduler
> 2014-06-27 23:22:09,338 | WARN  | 
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com..update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
>  - cursor got duplicate: ID:jxnc17-60227-1400730816361-1:1:149072:1:1, 4 | 
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ 
> Broker[localhost] Scheduler
> 2014-06-27 23:22:09,339 | WARN  | 
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com..update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
>  - cursor got duplicate: ID:cyyun-46954-1403800808565-1:1:9765:1:1, 4 | 
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ 
> Broker[localhost] Scheduler
> 2014-06-27 23:22:09,339 | WARN  | 
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com..update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
>  - cursor got duplicate: ID:ubuntu-55495-1403497638437-1:1:53086:1:1, 4 | 
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ 
> Broker[localhost] Scheduler
> 2014-06-27 23:22:09,340 | WARN  | 
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@19117501:com..update,batchResetNeeded=false,storeHasMessages=true,size=211,cacheEnabled=true,maxBatchSize:200,hasSpace:true
>  - cursor got duplicate: ID:cyyun-39030-1403880008363-1:1:70:1:1, 4 | 
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ 
> Broker[localhost] Scheduler
> The problem mostly happens right after activemq starts and sometimes happened 
> after activemq worked normally for a while.
> For now I have to roll back to 5.9.0 and the problem doesn't occure.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ACTIVEMQ6-67) clean up configuration files

[Andy Taylor (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ACTIVEMQ6-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Taylor resolved ACTIVEMQ6-67.
--
Resolution: Fixed

> clean up configuration files
> 
>
> Key: ACTIVEMQ6-67
> URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-67
> Project: Apache ActiveMQ 6
>  Issue Type: Task
>Reporter: Andy Taylor
>Assignee: Andy Taylor
> Fix For: 6.0.0
>
>
> The configuration files and parsers need consolidating to be cleaner, that is 
> the main and configuration file should be combined and the securty bootstrap 
> needs fixing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)