Github user andytaylor closed the pull request at:
https://github.com/apache/activemq-6/pull/81
---
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
Are you aware that the list of resolved issues includes issues marked
Unresolved? See AMQ-5217 https://issues.apache.org/jira/browse/AMQ-5217
and AMQ-5537 https://issues.apache.org/jira/browse/AMQ-5537 for instance.
On 27 January 2015 at 11:37, Krzysztof Sobkowiak krzys.sobkow...@gmail.com
Hey Gary - what happened to the test failures on AMQ2149LevelDBTest.log? As
you may have noticed - I was still working on that one as I had the
impression from our prior discussion that it was in the path to getting 5.11
released.
Was there a change on that front?
--
View this message in
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-6/pull/80
---
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
Sergiy Barlabanov created AMQ-5542:
--
Summary: KahaDB data files containing acknowledgements are deleted
during cleanup
Key: AMQ-5542
URL: https://issues.apache.org/jira/browse/AMQ-5542
Project:
Apologies Art, I should have given you a heads up. That test failure
(it always works locally) is an old nugget[1] that has been on the
todo list for a long time. I did not think it should hold up the
release. For the past three weeks I have been tracking down
regressions and failures and
[
https://issues.apache.org/jira/browse/AMQ-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14294232#comment-14294232
]
Tim Bain commented on AMQ-5542:
---
Doesn't the logic described here imply that we're almost
[
https://issues.apache.org/jira/browse/AMQ-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergiy Barlabanov updated AMQ-5542:
---
Attachment: AMQ-5542.patch
This is the possible patch.
Just removed the copy of gcCandidateSet.
[
https://issues.apache.org/jira/browse/AMQ-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14294349#comment-14294349
]
Sergiy Barlabanov edited comment on AMQ-5542 at 1/27/15 10:49 PM:
[
https://issues.apache.org/jira/browse/AMQ-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14294349#comment-14294349
]
Sergiy Barlabanov commented on AMQ-5542:
AMQ-2736 actually introduced the problem.
On 01/27/2015 05:53 PM, artnaseef wrote:
That makes sense. Here's what I'll do - if I can get the test to fail on
5.10, then I'll ignore it for the 5.11 release. Let me know if you have
seen this test failing under 5.10 and I'll skip it.
Either way, I'll keep tracking down the issue.
--
+1 (non-binding)
[
https://issues.apache.org/jira/browse/AMQ-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14294463#comment-14294463
]
Sergiy Barlabanov edited comment on AMQ-5542 at 1/28/15 12:19 AM:
-1 (binding).
* sigs ok
* release artifacts look ok
* project does *not* build from source:
There are 5 failures in activemq-stomp, all of the following kind:
StompTest.testSubscribeWithClientAck:739 null
That means that anybody who uses this stomp feature won't be able to
upgrade.
I think
thanks James, I tidied up those two issues.
On 27 January 2015 at 14:11, James Green james.mk.gr...@gmail.com wrote:
Are you aware that the list of resolved issues includes issues marked
Unresolved? See AMQ-5217 https://issues.apache.org/jira/browse/AMQ-5217
and AMQ-5537
+1
On 01/26/2015 04:02 PM, Gary Tully wrote:
Hi folks,
I've just cut a second release candidate for the long-awaited 5.11.0 release.
This release has more than 120 bug fixes and improvements.
Could you review the artifacts and vote? Especially, it would be great if
you could test the unix
Anuj Khandelwal created AMQ-5540:
Summary: KahaDB can't fail over to the slave if the master is
unable to write to disk
Key: AMQ-5540
URL: https://issues.apache.org/jira/browse/AMQ-5540
Project:
[
https://issues.apache.org/jira/browse/AMQ-5537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-5537:
Fix Version/s: (was: 5.11.0)
Network Connector Throughput
+1
On Mon, Jan 26, 2015 at 4:02 PM, Gary Tully gary.tu...@gmail.com wrote:
Hi folks,
I've just cut a second release candidate for the long-awaited 5.11.0 release.
This release has more than 120 bug fixes and improvements.
Could you review the artifacts and vote? Especially, it would be
[
https://issues.apache.org/jira/browse/AMQ-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-5217.
-
Resolution: Fixed
on 2.4.1
Upgrade to Jackson 2
Key: AMQ-5217
That makes sense. Here's what I'll do - if I can get the test to fail on
5.10, then I'll ignore it for the 5.11 release. Let me know if you have
seen this test failing under 5.10 and I'll skip it.
Either way, I'll keep tracking down the issue.
--
View this message in context:
+1 (non-binding)
The {{org.apache.activemq.bugs.AMQ2149LevelDBTest}} test fails in 5.10.0
with at least similar symptoms , so there's no reason to hold up 5.11.0 for
this.
--
View this message in context:
[
https://issues.apache.org/jira/browse/AMQ-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14294463#comment-14294463
]
Sergiy Barlabanov commented on AMQ-5542:
I think, you are right. Otherwise KahaDB
[
https://issues.apache.org/jira/browse/AMQ-5540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14294318#comment-14294318
]
Gary Tully edited comment on AMQ-5540 at 1/27/15 10:34 PM:
---
please
Tim Bain created AMQ-5543:
-
Summary: Broker logs show repeated
java.lang.IllegalSt​ateException: Timer already cancelled. lines
Key: AMQ-5543
URL: https://issues.apache.org/jira/browse/AMQ-5543
Project:
[
https://issues.apache.org/jira/browse/AMQ-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergiy Barlabanov updated AMQ-5542:
---
Attachment: AdjustedAMQ2832Test.patch
This is an adjustment test for AMQ2832Test.java which
[
https://issues.apache.org/jira/browse/AMQ-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14294333#comment-14294333
]
Sergiy Barlabanov commented on AMQ-5542:
The consequence of the fix is that if you
+1
Regards
--
Dejan Bosanac
--
Red Hat, Inc.
dbosa...@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/
On Mon, Jan 26, 2015 at 10:02 PM, Gary Tully gary.tu...@gmail.com wrote:
Hi folks,
I've just cut a second release
+1
kicked its tyres and seems fine
On 27/01/15 10:45, Dejan Bosanac wrote:
+1
Regards
--
Dejan Bosanac
--
Red Hat, Inc.
dbosa...@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/
On Mon, Jan 26, 2015 at 10:02 PM, Gary
GitHub user andytaylor opened a pull request:
https://github.com/apache/activemq-6/pull/81
documentation updates
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andytaylor/activemq-6 master
Alternatively you can review and
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-6/pull/82
---
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
Hi
+1 (non-binding).
Quick tests on Karaf 2.4.1 and 3.0.3-SNAPSHOT ok.
Regards
Krzysztof
On 26.01.2015 22:02, Gary Tully wrote:
Hi folks,
I've just cut a second release candidate for the long-awaited 5.11.0 release.
This release has more than 120 bug fixes and improvements.
Could you
GitHub user mtaylor opened a pull request:
https://github.com/apache/activemq-6/pull/82
Doc redel
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mtaylor/activemq-6 doc_redel
Alternatively you can review and apply these changes
[
https://issues.apache.org/jira/browse/AMQ-5540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anuj Khandelwal updated AMQ-5540:
-
Attachment: ActiveMQ_config.xml
Logs.txt
Attaching the logs and ActiveMQ
Paul Smith created AMQ-5544:
---
Summary: Broker level TotalMessageCount metric can be negative
Key: AMQ-5544
URL: https://issues.apache.org/jira/browse/AMQ-5544
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-5541.
-
Resolution: Fixed
policy entry now eagerly sets redelivered flag on broker messages (non
persistent, only
I found one regression in stomp - fixed via
https://git1-us-west.apache.org/repos/asf?p=activemq.git;a=commit;h=1e5d2127
which shows the config workaround. I think the use case is tenuous at
best so I don't think it should block the release.
On 26 January 2015 at 21:02, Gary Tully
GitHub user andytaylor opened a pull request:
https://github.com/apache/activemq-6/pull/83
upgrade to jetty 8 to be consistent with ActiveMQ 5
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andytaylor/activemq-6 master
+1
On Mon, Jan 26, 2015, 1:03 PM Gary Tully gary.tu...@gmail.com wrote:
Hi folks,
I've just cut a second release candidate for the long-awaited 5.11.0
release.
This release has more than 120 bug fixes and improvements.
Could you review the artifacts and vote? Especially, it would be great
Gary Tully created AMQ-5541:
---
Summary: Support preemptive redelivery flag for non persistent
messages
Key: AMQ-5541
URL: https://issues.apache.org/jira/browse/AMQ-5541
Project: ActiveMQ
Issue
40 matches
Mail list logo
