Build failed in Jenkins: ActiveMQ » ActiveMQ :: Unit Tests #1455

See Changes: [tabish121] https://issues.apache.org/jira/browse/AMQ-5213 [tabish121] Convert to JUnit 4 test and add a timeout, also remove the tcp transport --

Build failed in Jenkins: ActiveMQ #1455

See Changes: [tabish121] https://issues.apache.org/jira/browse/AMQ-5213 [tabish121] https://issues.apache.org/jira/browse/AMQ-5214 [tabish121] Convert to JUnit 4 test and add a timeout, also remove the tcp transport ---

[jira] [Created] (AMQ-5215) org.apache.activemq.thread.PooledTaskRunner.wakeup() doesn't handle errors

Tapan Jaggi created AMQ-5215: Summary: org.apache.activemq.thread.PooledTaskRunner.wakeup() doesn't handle errors Key: AMQ-5215 URL: https://issues.apache.org/jira/browse/AMQ-5215 Project: ActiveMQ

[jira] [Commented] (AMQ-5202) Default cursor exceeds allocated memory on broker restart

[ https://issues.apache.org/jira/browse/AMQ-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019575#comment-14019575 ] Ben O'Day commented on AMQ-5202: we were able to deal with this issue by setting a per queue

[jira] [Commented] (AMQ-5188) AMQ broker throws OutOfMemoryError even when global flow-control memoryUsage limit is imposed

[ https://issues.apache.org/jira/browse/AMQ-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019570#comment-14019570 ] Ben O'Day commented on AMQ-5188: we had a similar issue and were able to mitigate it by sett

[jira] [Updated] (AMQ-5211) ActiveMQDestination.createDestination() should prevent empty destination name

[ https://issues.apache.org/jira/browse/AMQ-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben O'Day updated AMQ-5211: --- Attachment: AMQ-5211.patch > ActiveMQDestination.createDestination() should prevent empty destination name > --

[jira] [Comment Edited] (AMQ-5211) ActiveMQDestination.createDestination() should prevent empty destination name

[ https://issues.apache.org/jira/browse/AMQ-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019562#comment-14019562 ] Ben O'Day edited comment on AMQ-5211 at 6/6/14 4:32 AM: patch to add

[jira] [Updated] (AMQ-5211) ActiveMQDestination.createDestination() should prevent empty destination name

[ https://issues.apache.org/jira/browse/AMQ-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben O'Day updated AMQ-5211: --- Attachment: (was: AMQ-5211.patch) > ActiveMQDestination.createDestination() should prevent empty destinatio

[jira] [Updated] (AMQ-5211) ActiveMQDestination.createDestination() should prevent empty destination name

[ https://issues.apache.org/jira/browse/AMQ-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben O'Day updated AMQ-5211: --- Attachment: AMQ-5211.patch patch to add validation with simple unit tests for empty queue/topic names... > Act

[jira] [Updated] (AMQ-5211) ActiveMQDestination.createDestination() should prevent empty destination name

[ https://issues.apache.org/jira/browse/AMQ-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben O'Day updated AMQ-5211: --- Attachment: (was: AMQ-5211.patch) > ActiveMQDestination.createDestination() should prevent empty destinatio

Re: [VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

AMQ-5167 works now -- Karaf with Felix. With Equinox (AMQ-4794) does not work and adding the missing import doesn't help too, On 05.06.2014 23:54, artnaseef wrote: > Did I misread the earlier statement that "it works", or did something change? > > > > -- > View this message in context: > htt

Re: [VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

Did I misread the earlier statement that "it works", or did something change? -- View this message in context: http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-10-0-Release-Candidate-2-tp4681721p4681747.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

The problem still exists (tested with Karaf 2.3.4, Camel 2.13.1 and ActiveMQ 5.10.0) On 05.06.2014 23:00, artnaseef wrote: > Great - any concerns with changing the resolution on > https://issues.apache.org/jira/browse/AMQ-4794 to "FIXED"? > > > > -- > View this message in context: > http://acti

[jira] [Commented] (AMQ-5211) ActiveMQDestination.createDestination() should prevent empty destination name

[ https://issues.apache.org/jira/browse/AMQ-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019278#comment-14019278 ] Ben O'Day commented on AMQ-5211: agreed Tim, I'll add a unit test to the patch... > ActiveM

Re: [VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

Great - any concerns with changing the resolution on https://issues.apache.org/jira/browse/AMQ-4794 to "FIXED"? -- View this message in context: http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-10-0-Release-Candidate-2-tp4681721p4681742.html Sent from the ActiveMQ - Dev mailing list

Re: RAM or Core for AMQ

can you elaborate on what sort of test your are running - message size, persistent or non persistent, destination type, num producer/consumer pairs, protocol etc. AMQ is not great at using multiple cores so mostly gets cpu bound on 2/3 cores. So RAM/CPU is the answer up to a point On 31 May 2014

[jira] [Commented] (AMQ-5211) ActiveMQDestination.createDestination() should prevent empty destination name

[ https://issues.apache.org/jira/browse/AMQ-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019250#comment-14019250 ] Timothy Bish commented on AMQ-5211: --- This seems sensible enough. Empty destination names

[jira] [Resolved] (AMQ-5214) Security errors for sync commands are only logged at debug levels

[ https://issues.apache.org/jira/browse/AMQ-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5214. --- Resolution: Fixed Fixed on trunk. > Security errors for sync commands are only logged at debug levels

[jira] [Created] (AMQ-5214) Security errors for sync commands are only logged at debug levels

Timothy Bish created AMQ-5214: - Summary: Security errors for sync commands are only logged at debug levels Key: AMQ-5214 URL: https://issues.apache.org/jira/browse/AMQ-5214 Project: ActiveMQ Iss

Re: [VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

The web console installs now with no problem on Karaf. Best regards Krzysztof On 05.06.2014 16:08, Dejan Bosanac wrote: > Hi folks, > > I've just cut a second release candidate for the 5.10.0 release. This > release has > 232 bug fixes and improvements. > > Could you review the artifacts and vote

[jira] [Resolved] (AMQ-5213) Allow for changing logger levels via JMX

[ https://issues.apache.org/jira/browse/AMQ-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5213. --- Resolution: Fixed Feature added on trunk. > Allow for changing logger levels via JMX > --

[jira] [Created] (AMQ-5213) Allow for changing logger levels via JMX

Timothy Bish created AMQ-5213: - Summary: Allow for changing logger levels via JMX Key: AMQ-5213 URL: https://issues.apache.org/jira/browse/AMQ-5213 Project: ActiveMQ Issue Type: New Feature

Build failed in Jenkins: ActiveMQ Protocol Buffer #15

See -- [...truncated 828 lines...] 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-9/doxia-sink-api-1.0-alpha-9.pom 1K downloaded Downl

Re: [VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

Can someone familiar with AMQ-4269 put a quick comment there as to why it was marked "invalid"? Was it a case of the original post didn't expose a bug, but rather just known "undesirable, but correct" operation? https://issues.apache.org/jira/browse/AMQ-4269 AMQ-4794 is marked "won't fix -- due

[jira] [Commented] (AMQ-5167) ActiveMQ web-cosole fails to start in Karaf - missing import

[ https://issues.apache.org/jira/browse/AMQ-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018842#comment-14018842 ] ASF GitHub Bot commented on AMQ-5167: - Github user sobkowiak closed the pull request at:

[GitHub] activemq pull request: AMQ-5167 ActiveMQ web-cosole fails to start...

Github user sobkowiak closed the pull request at: https://github.com/apache/activemq/pull/27 --- 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

[jira] [Commented] (AMQ-5030) Upgrade Camel to latest 2.12.x patch

[ https://issues.apache.org/jira/browse/AMQ-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018830#comment-14018830 ] Paul Gale commented on AMQ-5030: Is there any reason why Camel cannot be upgraded to 2.13.1

[VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

Hi folks, I've just cut a second release candidate for the 5.10.0 release. This release has 232 bug fixes and improvements. Could you review the artifacts and vote? The list of resolved issues is here: https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMQ%20AND%20fixVersion%20%3D%205.10

[jira] [Updated] (AMQ-5125) Broker and clients hang

[ https://issues.apache.org/jira/browse/AMQ-5125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Klubal updated AMQ-5125: -- Attachment: broker-threads-blocked.tdump Same issue happening to us not every time but quite often on ver

[jira] [Created] (AMQ-5212) Deadlock with duplicate detection and dlq processing in kahadb

Gary Tully created AMQ-5212: --- Summary: Deadlock with duplicate detection and dlq processing in kahadb Key: AMQ-5212 URL: https://issues.apache.org/jira/browse/AMQ-5212 Project: ActiveMQ Issue Type

[jira] [Commented] (AMQ-5167) ActiveMQ web-cosole fails to start in Karaf - missing import

[ https://issues.apache.org/jira/browse/AMQ-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018633#comment-14018633 ] Dejan Bosanac commented on AMQ-5167: I don't have any plans to do it. If someone wants t

[jira] [Commented] (AMQ-5167) ActiveMQ web-cosole fails to start in Karaf - missing import

[ https://issues.apache.org/jira/browse/AMQ-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018627#comment-14018627 ] Krzysztof Sobkowiak commented on AMQ-5167: -- Will you not release the 5.9.x line any

[jira] [Resolved] (AMQ-5167) ActiveMQ web-cosole fails to start in Karaf - missing import

[ https://issues.apache.org/jira/browse/AMQ-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-5167. Resolution: Fixed Fix Version/s: 5.10.0 Patch applied to trunk. Thanks! > ActiveMQ web-cosole

[jira] [Updated] (AMQ-5193) Java Files Started Appearing in activemq-all jar starting in 5.9.0

[ https://issues.apache.org/jira/browse/AMQ-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac updated AMQ-5193: --- Fix Version/s: (was: 5.11.0) 5.10.0 > Java Files Started Appearing in activemq-a

[jira] [Updated] (AMQ-5209) Add additional properties to advisory for consumed, delivered and discarded

[ https://issues.apache.org/jira/browse/AMQ-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac updated AMQ-5209: --- Fix Version/s: (was: 5.11.0) 5.10.0 > Add additional properties to advisory for

Re: [VOTE] Apache ActiveMQ 5.10.0

Hi Paul, it’s a mistake in the release notes, it got all the issues that has fix version 5.10. Regards -- Dejan Bosanac -- Red Hat, Inc. FuseSource is now part of Red Hat dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/

Re: [VOTE] Apache ActiveMQ 5.10.0

Thanks guys, cancelling this vote and will build the new RC. Regards -- Dejan Bosanac -- Red Hat, Inc. FuseSource is now part of Red Hat dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/ On Wed, Jun 4, 2014 at 9: