[
https://issues.apache.org/jira/browse/AMQ-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14482775#comment-14482775
]
Peter Pfort commented on AMQ-5155:
--
It's works now.
Thanks
Heartbeat fails in STOMP over
Christian Schneider created AMQ-5709:
Summary: Logging of Database ... is locked should be done on
level DEBUG
Key: AMQ-5709
URL: https://issues.apache.org/jira/browse/AMQ-5709
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14483063#comment-14483063
]
Gary Tully commented on AMQ-5709:
-
maybe we reduce the frequency - there was a fix a few
[
https://issues.apache.org/jira/browse/AMQ-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Torsten Mielke updated AMQ-5692:
Attachment: AMQ-5692.pl
Inactivity monitor does not time out on stuck socket writes
[
https://issues.apache.org/jira/browse/AMQ-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14483067#comment-14483067
]
Torsten Mielke commented on AMQ-5692:
-
Attached reproducer in AMQ-5692.pl.
To reproduce
[
https://issues.apache.org/jira/browse/AMQ-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14483068#comment-14483068
]
Christian Schneider commented on AMQ-5709:
--
+1 to log the first try at higher
[
https://issues.apache.org/jira/browse/AMQ-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14483110#comment-14483110
]
Jean-Baptiste Onofré commented on AMQ-5709:
---
Yes, I think the first log message
[
https://issues.apache.org/jira/browse/AMQ-5707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5707.
---
Resolution: Fixed
Fix Version/s: 5.12.0
Added support for reacting to the ConsumerControl
make JIRA notifications into a JIRA list? then you subscribe into that
if you like.
I think github notifications should still be on the dev list though.
On Tue, Apr 7, 2015 at 10:43 AM, artnaseef a...@artnaseef.com wrote:
Using Nabble, as I do, to keep up with the dev mailing list, this is what
[
https://issues.apache.org/jira/browse/AMQ-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic reassigned AMQ-5709:
Assignee: clebert suconic
Logging of Database ... is locked should be done on level DEBUG
Dejan Bosanac created AMQ-5710:
--
Summary: ActiveMQConnection cleanup should not close the
connection on the broker
Key: AMQ-5710
URL: https://issues.apache.org/jira/browse/AMQ-5710
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-5710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac resolved AMQ-5710.
Resolution: Fixed
Fixed with http://git-wip-us.apache.org/repos/asf/activemq/commit/c705523c
On Apr 7, 2015, at 11:02 AM, Clebert Suconic clebert.suco...@gmail.com
wrote:
make JIRA notifications into a JIRA list? then you subscribe into that
if you like.
Many of the other projects (CXF, Camel, etc…) do have a separate “issues” list
for the JIRA things. That might make sense.
[
https://issues.apache.org/jira/browse/AMQ-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14483412#comment-14483412
]
Timothy Bish commented on AMQ-5711:
---
So the NPE is not great here but what you are trying
[
https://issues.apache.org/jira/browse/AMQ-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher L. Shannon updated AMQ-5712:
Summary: Broker can deadlock when using queues while producers wait on disk
space
Agreed. +1
On Tuesday, April 7, 2015, Clebert Suconic clebert.suco...@gmail.com
wrote:
paste the JIRA? I will vote for it.
I would keep github on dev for now.. there are a few discussions that
would happen through github (embedded comments.. etc) that I think
it's worth to mirror to the
Anything that requires assistance from the Infra team is accomplished by
creating a JIRA issue. Just create a new issue in JIRA (
https://issues.apache.org/jira/secure/Dashboard.jspa) and select the
Infrastructure project.
Bruce
On Tue, Apr 7, 2015 at 12:36 PM, artnaseef a...@artnaseef.com
It just seemed like a simple thing to clean up. You can refuse it because
it's clear that I don't understand the configuration yet.
Bruce
On Tue, Apr 7, 2015 at 9:27 AM, Clebert Suconic clebert.suco...@gmail.com
wrote:
@Bruce:
What's the best way to handle this:
I have seen your PR:
+1
That works. It looks like the volume of github notifications is much lower
- and appear to be mostly pull requests, so moving out the jira entries
would be a big win.
--
View this message in context:
Christopher L. Shannon created AMQ-5712:
---
Summary: Broker can deadlock for queues while producers wait on
disk space
Key: AMQ-5712
URL: https://issues.apache.org/jira/browse/AMQ-5712
Project:
It sounds like the Jira list is the way to go.
How can I go about getting the list created and messages redirected? I
think iss...@activemq.apache.org is the way to go.
Art
--
View this message in context:
I already submitted a request.
Bruce
On Tue, Apr 7, 2015 at 12:18 PM, artnaseef a...@artnaseef.com wrote:
It sounds like the Jira list is the way to go.
How can I go about getting the list created and messages redirected? I
think iss...@activemq.apache.org is the way to go.
Art
--
https://issues.apache.org/jira/browse/INFRA-9394
Vote the JIRA, I guess that will bother infra guys to do it sooner ;)
On Tue, Apr 7, 2015 at 2:43 PM, James Carman ja...@carmanconsulting.com wrote:
Agreed. +1
On Tuesday, April 7, 2015, Clebert Suconic clebert.suco...@gmail.com
wrote:
+1
Bruce
On Tue, Apr 7, 2015 at 12:39 PM, Clebert Suconic clebert.suco...@gmail.com
wrote:
paste the JIRA? I will vote for it.
I would keep github on dev for now.. there are a few discussions that
would happen through github (embedded comments.. etc) that I think
it's worth to mirror to
Nabble is not controlled by the ASF at all.
Bruce
On Tue, Apr 7, 2015 at 12:49 PM, artnaseef a...@artnaseef.com wrote:
So the Infra team manages Jira and mailing lists?
What about nabble - will it also be included, or is there more work to do
there?
--
View this message in context:
[
https://issues.apache.org/jira/browse/AMQ-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher L. Shannon updated AMQ-5712:
Description:
I am experiencing a deadlock when using a Queue with non-persistent
paste the JIRA? I will vote for it.
I would keep github on dev for now.. there are a few discussions that
would happen through github (embedded comments.. etc) that I think
it's worth to mirror to the dev... we can later move out if they start
to bother.
On Tue, Apr 7, 2015 at 2:35 PM, Bruce
Hey Bruce - I would like to learn the process here. Can you help me?
Was the request made simply by creating a Jira entry?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/DISCUSS-dev-mailing-list-is-cluttered-tp4694420p4694448.html
Sent from the ActiveMQ - Dev mailing
Good point, Clebert.
Bruce
On Tue, Apr 7, 2015 at 12:45 PM, Clebert Suconic clebert.suco...@gmail.com
wrote:
https://issues.apache.org/jira/browse/INFRA-9394
Vote the JIRA, I guess that will bother infra guys to do it sooner ;)
On Tue, Apr 7, 2015 at 2:43 PM, James Carman
Andy Taylor is sick today and he was the one who placed it there... I
will wait him back before deciding what to do ok?
I think it's all ok.. just would need to check what the docs says. but
i will wait for Andy.
On Tue, Apr 7, 2015 at 1:48 PM, Bruce Snyder bruce.sny...@gmail.com wrote:
It
+1
Bruce
On Tue, Apr 7, 2015 at 9:02 AM, Clebert Suconic clebert.suco...@gmail.com
wrote:
make JIRA notifications into a JIRA list? then you subscribe into that
if you like.
I think github notifications should still be on the dev list though.
On Tue, Apr 7, 2015 at 10:43 AM, artnaseef
I don't think they work that way, but it couldn't hurt. :)
On Tuesday, April 7, 2015, Bruce Snyder bruce.sny...@gmail.com wrote:
Good point, Clebert.
Bruce
On Tue, Apr 7, 2015 at 12:45 PM, Clebert Suconic
clebert.suco...@gmail.com javascript:;
wrote:
Actually the mailing lists are different
https://infra.apache.org/officers/mlreq
On Tuesday, April 7, 2015, Bruce Snyder bruce.sny...@gmail.com wrote:
Anything that requires assistance from the Infra team is accomplished by
creating a JIRA issue. Just create a new issue in JIRA (
So the Infra team manages Jira and mailing lists?
What about nabble - will it also be included, or is there more work to do
there?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/DISCUSS-dev-mailing-list-is-cluttered-tp4694420p4694453.html
Sent from the ActiveMQ - Dev
Unless anyone objects, I don't think we need an official VOTE. Thus
far, it appears we have consensus. Anyone? Anyone? Bueller?
On Tue, Apr 7, 2015 at 4:21 PM, Hiram Chirino hi...@hiramchirino.com wrote:
Do we need an official vote thread for these kinds of changes?
Perhaps this discussion
How about this.. Lets request the change 72 hours after this thread
was started. So 3 days - 5 hours :) That way, we lets folks in
different time zones get a chance to object if they want. After that
we can call it lazy consensus and be done with it.
On Tue, Apr 7, 2015 at 4:30 PM, Bruce Snyder
I don't think we need a vote, but I won't stand in the way of one.
Bruce
On Tue, Apr 7, 2015 at 2:26 PM, James Carman ja...@carmanconsulting.com
wrote:
Unless anyone objects, I don't think we need an official VOTE. Thus
far, it appears we have consensus. Anyone? Anyone? Bueller?
On Tue,
The purpose of the PMC chair is to represent the project to the board.
I supposed it would be a good idea to vote on this change on the dev@ list.
Bruce
On Tue, Apr 7, 2015 at 1:14 PM, James Carman ja...@carmanconsulting.com
wrote:
I think we need to have Hiram request this since he is the
I think we need to have Hiram request this since he is the chair of the PMC.
On Tuesday, April 7, 2015, James Carman ja...@carmanconsulting.com wrote:
Actually the mailing lists are different
https://infra.apache.org/officers/mlreq
On Tuesday, April 7, 2015, Bruce Snyder
I'm OK either way. This is something that can be undone without too much
hassle if a later objection arises, but not without a little impact (that is
messages in the interim being in a different place).
--
View this message in context:
Do we need an official vote thread for these kinds of changes?
Perhaps this discussion thread is good enough?
On Tue, Apr 7, 2015 at 3:14 PM, James Carman ja...@carmanconsulting.com wrote:
I think we need to have Hiram request this since he is the chair of the PMC.
On Tuesday, April 7, 2015,
Sounds good. There's no reason to rush this by any stretch of the
imagination. Lazy consensus is just fine for this sort of thing, I'd
think.
On Tue, Apr 7, 2015 at 4:36 PM, Hiram Chirino hi...@hiramchirino.com wrote:
How about this.. Lets request the change 72 hours after this thread
was
I'm OK with moving JIRA notices to a separate list.
On Tue, Apr 7, 2015, 1:22 PM Hiram Chirino hi...@hiramchirino.com wrote:
Do we need an official vote thread for these kinds of changes?
Perhaps this discussion thread is good enough?
On Tue, Apr 7, 2015 at 3:14 PM, James Carman
[
https://issues.apache.org/jira/browse/ACTIVEMQ6-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14484050#comment-14484050
]
Justin Bertram commented on ACTIVEMQ6-19:
-
How about we replace the
[
https://issues.apache.org/jira/browse/ACTIVEMQ6-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram reassigned ACTIVEMQ6-19:
---
Assignee: Justin Bertram
Disable Server Side Load Balancing on message routing
GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq/pull/82
AMQ-5709 Reworking Logging on Locker
https://issues.apache.org/jira/browse/AMQ-5709
This is about changing how the Log is done in case of not being able to
lock (log only once)
+1 for lazy consensus.
On Tue, Apr 7, 2015, 1:44 PM James Carman ja...@carmanconsulting.com
wrote:
Sounds good. There's no reason to rush this by any stretch of the
imagination. Lazy consensus is just fine for this sort of thing, I'd
think.
On Tue, Apr 7, 2015 at 4:36 PM, Hiram Chirino
[
https://issues.apache.org/jira/browse/AMQ-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14484095#comment-14484095
]
ASF GitHub Bot commented on AMQ-5709:
-
GitHub user clebertsuconic opened a pull request:
I took this JIRA to fix here:
https://issues.apache.org/jira/browse/AMQ-5709
https://github.com/apache/activemq/pull/82
and I discovered a race into LockFile.java
Basically Lock will return false if you run the test I wrote in loop.
It's non related to my change.. but I will add the test
[
https://issues.apache.org/jira/browse/AMQ-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic resolved AMQ-5709.
--
Resolution: Fixed
Logging of Database ... is locked should be done on level DEBUG
[
https://issues.apache.org/jira/browse/AMQ-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14484114#comment-14484114
]
ASF GitHub Bot commented on AMQ-5709:
-
Github user asfgit closed the pull request at:
I think the in vm case is only used in some tests, so it is not
critical but would be a nice addition to have it correct.
On 7 April 2015 at 22:33, Clebert Suconic clebert.suco...@gmail.com wrote:
I took this JIRA to fix here:
https://issues.apache.org/jira/browse/AMQ-5709
[
https://issues.apache.org/jira/browse/ACTIVEMQ6-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14484050#comment-14484050
]
Justin Bertram edited comment on ACTIVEMQ6-19 at 4/7/15 10:15 PM:
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/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
I can take a look on fixing it tomorrow.
Take a look at my last commit later please as I have added a test for it.
On Tue, Apr 7, 2015 at 5:39 PM, Gary Tully gary.tu...@gmail.com wrote:
I think the in vm case is only used in some tests, so it is not
critical but would be a nice addition to
[
https://issues.apache.org/jira/browse/AMQ-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14484349#comment-14484349
]
Piotr Klimczak commented on AMQ-4693:
-
Pushed one more commit to PR as I have realised
[
https://issues.apache.org/jira/browse/ACTIVEMQ6-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14484050#comment-14484050
]
Justin Bertram edited comment on ACTIVEMQ6-19 at 4/8/15 2:41 AM:
57 matches
Mail list logo
