Re: [VOTE] HornetQ Code Donation should use a codename
+1
-dain
On Apr 9, 2015, at 6:06 AM, Hiram Chirino hi...@hiramchirino.com wrote:
Lots of confusion has occurred since we did not use a code name for
the code donation from the start. Everyone refers to it as HornetQ
which adds to the Trademark confusions. Also the current state of the
code is not ready to become ActiveMQ 6. We can figure out what the
code name should be later with community and trademarks input.
Please choose an option:
[ ] +1 : Rename the hornetq code grant source code from ActiveMQ 6 to
an ActiveMQ ${codename}
[ ] -1 : No don't rename
[ ] 0 : No preference
Vote is open for 72 hours.
--
Hiram Chirino
Engineering | Red Hat, Inc.
hchir...@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino
[VOTE] HornetQ Code Donation should use a codename
Lots of confusion has occurred since we did not use a code name for
the code donation from the start. Everyone refers to it as HornetQ
which adds to the Trademark confusions. Also the current state of the
code is not ready to become ActiveMQ 6. We can figure out what the
code name should be later with community and trademarks input.
Please choose an option:
[ ] +1 : Rename the hornetq code grant source code from ActiveMQ 6 to
an ActiveMQ ${codename}
[ ] -1 : No don't rename
[ ] 0 : No preference
Vote is open for 72 hours.
--
Hiram Chirino
Engineering | Red Hat, Inc.
hchir...@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino
[jira] [Commented] (AMQ-5155) Heartbeat fails in STOMP over WebSockets
[ https://issues.apache.org/jira/browse/AMQ-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14487704#comment-14487704 ] Chad Kelly commented on AMQ-5155: - You are correct, using /topic/test works as expected. I performed various tests and no issues to report. Thank you very much for solving this bug. This is the one feature I needed in order to use ActiveMQ. I appreciate everyone's contribution in resolving this problem and look forward to the release of 5.12. Heartbeat fails in STOMP over WebSockets Key: AMQ-5155 URL: https://issues.apache.org/jira/browse/AMQ-5155 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.9.1, 5.10.0 Reporter: Arjan van den Berg Assignee: Timothy Bish Priority: Minor Fix For: 5.12.0 Attachments: AMQ-5155-jetty8.diff, AMQ-5155-jetty9.diff From AMQ-4740: I receive the following error after establishing a connection and heartbeat through stomp.js. This seems to occur after the 'PING' is sent. -- stomp.js output CONNECTED heart-beat:1,1 session:ID:localhost.localdomain-45596-1396530920609-2:2 server:ActiveMQ/5.10-SNAPSHOT version:1.1 send PING every 1ms check PONG every 1ms PONG PING did not receive server activity for the last 20005ms Whoops! Lost connection to ws://172.16.99.73:61614/stomp - activemq console --- WARN | Transport Connection to: StompSocket_19548821 failed: java.io.IOException Exception in thread ActiveMQ InactivityMonitor Worker java.lang.NullPointerException at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314) at org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:215) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) WARN | Transport Connection to: StompSocket_19548821 failed: java.io.IOException Exception in thread ActiveMQ InactivityMonitor Worker java.lang.NullPointerException at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314) at org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:215) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) For me it looks as if the StompInactivityMonitor is delivering its events to the wrong Transport, i.e. it needs a narrow() when setting it up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-5155) Heartbeat fails in STOMP over WebSockets
[ https://issues.apache.org/jira/browse/AMQ-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14487669#comment-14487669 ] Chad Kelly commented on AMQ-5155: - Even though the above bug was fixed, a related bug now occurs. This may deserve a new ticket? Can someone confirm the following: 1) Download a recent 5.12 SNOPSHOT that works and contains the patch above. I used https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/5.12-SNAPSHOT/apache-activemq-5.12-20150407.48-96-bin.tar.gz 2) bin/activemq console xbean:examples/conf/activemq-demo.xml 3) open two browsers (firefox/chrome) to http://localhost:8161/demo/websocket/index.html 4) In a single browser window, type 1, 2, 3, ... 9 with a return/enter after each number 5) Half of the chat ends up in one browser, and half in the other. This bug causes the receiving browser to only get 1/2 the chats. Could this bug relate to the new added code that uses /n? Can someone confirm this? Heartbeat fails in STOMP over WebSockets Key: AMQ-5155 URL: https://issues.apache.org/jira/browse/AMQ-5155 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.9.1, 5.10.0 Reporter: Arjan van den Berg Assignee: Timothy Bish Priority: Minor Fix For: 5.12.0 Attachments: AMQ-5155-jetty8.diff, AMQ-5155-jetty9.diff From AMQ-4740: I receive the following error after establishing a connection and heartbeat through stomp.js. This seems to occur after the 'PING' is sent. -- stomp.js output CONNECTED heart-beat:1,1 session:ID:localhost.localdomain-45596-1396530920609-2:2 server:ActiveMQ/5.10-SNAPSHOT version:1.1 send PING every 1ms check PONG every 1ms PONG PING did not receive server activity for the last 20005ms Whoops! Lost connection to ws://172.16.99.73:61614/stomp - activemq console --- WARN | Transport Connection to: StompSocket_19548821 failed: java.io.IOException Exception in thread ActiveMQ InactivityMonitor Worker java.lang.NullPointerException at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314) at org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:215) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) WARN | Transport Connection to: StompSocket_19548821 failed: java.io.IOException Exception in thread ActiveMQ InactivityMonitor Worker java.lang.NullPointerException at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314) at org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:215) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) For me it looks as if the StompInactivityMonitor is delivering its events to the wrong Transport, i.e. it needs a narrow() when setting it up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] HornetQ Code Donation should use a codename
+1
david jencks
On Apr 9, 2015, at 9:06 AM, Hiram Chirino hi...@hiramchirino.com wrote:
Lots of confusion has occurred since we did not use a code name for
the code donation from the start. Everyone refers to it as HornetQ
which adds to the Trademark confusions. Also the current state of the
code is not ready to become ActiveMQ 6. We can figure out what the
code name should be later with community and trademarks input.
Please choose an option:
[ ] +1 : Rename the hornetq code grant source code from ActiveMQ 6 to
an ActiveMQ ${codename}
[ ] -1 : No don't rename
[ ] 0 : No preference
Vote is open for 72 hours.
--
Hiram Chirino
Engineering | Red Hat, Inc.
hchir...@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino
Re: [DISCUSS] Fix Sorting of Board Reports
Thanks for the explanation. That helps. So, I guess we could discuss the merits of keeping the Board Reports on our wiki, as it does seem somewhat redundant. As long as they exist on the wiki, it would be helpful to have a better indexing system. Perhaps Hiram can offer background as to the purpose and intent of the Board Reports being published on the wiki? Best, Jim On Thu, Apr 9, 2015 at 10:27 AM, Daniel Kulp dk...@apache.org wrote: On Apr 9, 2015, at 1:02 PM, Jim Gomes jgo...@apache.org wrote: Thanks for the link, Dan. I didn't know those were there. I think the main difference here is that link is to the Board Minutes, whereas the ActiveMQ wiki has the Board Report. They seem to be identical, but will they always be? Possibly not, but it would NORMALLY be because the board has decided something should be private (like names of people being voted on or something) in which case it should likely not have been in our public version as well. Doesn't happen too often. Also, they would remove any wiki formatting type things that wouldn't look right in the text form they use. And even if they are identical, do we still need to have the redundancy for trace-ability? For instance, if the Board, for whatever reason, claims they didn't receive the report, we have documentation on the wiki showing the Report was produced. I don't really think the board would care if one was produced or not. It's the chair's job to make sure the board gets the report. If they don't get it, they ask the chair to report again next month. If the chair consistently has issues, they'd likely replace the chair.Another thing to keep in mind: it's the Chairs job to create the report that reflects the state of the community. The chair MAY include the wider community in creating that report, but that's not a requirement. Thus, saying the community produced one, the chair didn't submit it really wouldn't matter at all. Dan That's me just trying to understand the reason for the Board Report page's existence. -Jim On Thu, Apr 9, 2015 at 9:53 AM, Daniel Kulp dk...@apache.org wrote: No objection, but why don't we just delete the page and point at the official records: https://whimsy.apache.org/board/minutes/ActiveMQ.html Dan On Apr 9, 2015, at 12:35 PM, Jim Gomes jgo...@apache.org wrote: I recently went out to look at previous Board Reports ( http://activemq.apache.org/apache-activemq-board-reports.html) and found the current sorting method difficult to deal with. Unless we are required to use the page naming format, I would like to change it to the following format: Apache ActiveMQ Board Report - 2009.01 January Apache ActiveMQ Board Report - 2009.04 April Apache ActiveMQ Board Report - 2009.07 July . . . I would then set it to sort in reverse order so the most recent report is automatically at the top, and they descend in chronological order. The current sorting puts the most recent board report (2015/02) in the middle of the pack, making it difficult to find. Good luck trying to find the report directly prior to that. I will make the changes, unless anyone has other suggestions. Best, Jim -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
Re: [DISCUSS] Fix Sorting of Board Reports
Your proposal sounds good to me. On Thu, Apr 9, 2015 at 2:44 PM, Jim Gomes e.se...@gmail.com wrote: Thanks, Tim. That is a clear and compelling reason to keep them there. With that clarified, does anyone have any comments on the renaming of the pages to improve the indexing? Best, Jim On Thu, Apr 9, 2015 at 11:16 AM, Timothy Bish tabish...@gmail.com wrote: On 04/09/2015 02:13 PM, Jim Gomes wrote: Thanks for the explanation. That helps. So, I guess we could discuss the merits of keeping the Board Reports on our wiki, as it does seem somewhat redundant. As long as they exist on the wiki, it would be helpful to have a better indexing system. Perhaps Hiram can offer background as to the purpose and intent of the Board Reports being published on the wiki? Best, Jim On Thu, Apr 9, 2015 at 10:27 AM, Daniel Kulp dk...@apache.org wrote: On Apr 9, 2015, at 1:02 PM, Jim Gomes jgo...@apache.org wrote: Thanks for the link, Dan. I didn't know those were there. I think the main difference here is that link is to the Board Minutes, whereas the ActiveMQ wiki has the Board Report. They seem to be identical, but will they always be? Possibly not, but it would NORMALLY be because the board has decided something should be private (like names of people being voted on or something) in which case it should likely not have been in our public version as well. Doesn't happen too often. Also, they would remove any wiki formatting type things that wouldn't look right in the text form they use. And even if they are identical, do we still need to have the redundancy for trace-ability? For instance, if the Board, for whatever reason, claims they didn't receive the report, we have documentation on the wiki showing the Report was produced. I don't really think the board would care if one was produced or not. It's the chair's job to make sure the board gets the report. If they don't get it, they ask the chair to report again next month. If the chair consistently has issues, they'd likely replace the chair.Another thing to keep in mind: it's the Chairs job to create the report that reflects the state of the community. The chair MAY include the wider community in creating that report, but that's not a requirement. Thus, saying the community produced one, the chair didn't submit it really wouldn't matter at all. Dan That's me just trying to understand the reason for the Board Report page's existence. -Jim On Thu, Apr 9, 2015 at 9:53 AM, Daniel Kulp dk...@apache.org wrote: No objection, but why don't we just delete the page and point at the official records: https://whimsy.apache.org/board/minutes/ActiveMQ.html Dan On Apr 9, 2015, at 12:35 PM, Jim Gomes jgo...@apache.org wrote: I recently went out to look at previous Board Reports ( http://activemq.apache.org/apache-activemq-board-reports.html) and found the current sorting method difficult to deal with. Unless we are required to use the page naming format, I would like to change it to the following format: Apache ActiveMQ Board Report - 2009.01 January Apache ActiveMQ Board Report - 2009.04 April Apache ActiveMQ Board Report - 2009.07 July . . . I would then set it to sort in reverse order so the most recent report is automatically at the top, and they descend in chronological order. The current sorting puts the most recent board report (2015/02) in the middle of the pack, making it difficult to find. Good luck trying to find the report directly prior to that. I will make the changes, unless anyone has other suggestions. Best, Jim -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com I believe that he does this as a place to create and edit them and allow for other members to contribute if they so desire before he submits them. I've edited a couple in the past prior to submission to add CMS or NMS release notes. -- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.redhat.com twitter: @tabish121 blog: http://timbish.blogspot.com/ -- Hiram Chirino Engineering | Red Hat, Inc. hchir...@redhat.com | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino
Re: [DISCUSS} HornetQ ActiveMQ's next generation
+1 (Please pardon my reference to Buddhism here) In buddhist practice, we remind ourselves of many things every time we practice. One of those is stated this way, forgive me for divisive actions, and, I promise to avoid divisive actions. We all do it, whether with intent or not, but in the long run, it only leads to anger, frustration, ... Suffering. All the heated arguments here that attack all the value of all the great work of the past done by the folks on this project is truly sad. I only hope that there are enough folks either not listening, or believing that this is just one large vent so this conversation doesn't drive folks away from ActiveMQ. A culture of respect and honest interest in technical concerns, impacts on users and others across the community, and a focus on moving things forward -- that's a vision I dream of when I think of being a core member of the ActiveMQ community. I long for more discussions like ones I have had with Hadrian - in which we actually talk about ideas and work together to make a solution better than either one of us would have made alone. It's awesome. I highly recommend everyone to try it. Please move past the fighting. Every foolish thing any one of us has ever said can be forgiven. Every one here is valuable, and can bring that value to ActiveMQ - it's our actions and the impact they have on ActiveMQ - both the product and the community - that are our measure. Let's strive for the ideal - working together (not without disagreement) - bringing out valid concerns and providing valid responses, considering impacts and deciding which to accept, and how to minimize where possible. Then work toward resolution through decision-making and acceptance that no path forward will be perfect, and all paths forward that are worth taking require effort - true effort. With this said, I'm going back to focusing on other parts of my life at the moment as this entire discussion has drained so much of my energy for a week or two, and those parts have been neglected. Please PM me if my input is valuable and desired, or my absence is somehow blocking, before I return more prominently (probably after ApacheCon), when it will be time to get the next patch release of ActiveMQ built (I will do all the grunt work, although help is appreciated - thanks to Hadrian again for his past help in creating releases)! -- View this message in context: http://activemq.2283324.n4.nabble.com/DISCUSS-HornetQ-ActiveMQ-s-next-generation-tp4693781p4694603.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[GitHub] activemq-6 pull request: Add Auto JMS queue creation for OpenWire
GitHub user mtaylor opened a pull request: https://github.com/apache/activemq-6/pull/202 Add Auto JMS queue creation for OpenWire You can merge this pull request into a Git repository by running: $ git pull https://github.com/mtaylor/activemq-6 autoQueueCreationOpenWire Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/202.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #202 commit 548735f8b63ee07399ebd84b858f0fa808c4102d Author: Martyn Taylor mtay...@redhat.com Date: 2015-04-08T12:27:55Z Add Auto JMS queue creation for OpenWire --- 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. ---
Re: [DISCUSS] Fix Sorting of Board Reports
Thanks, Tim. That is a clear and compelling reason to keep them there. With that clarified, does anyone have any comments on the renaming of the pages to improve the indexing? Best, Jim On Thu, Apr 9, 2015 at 11:16 AM, Timothy Bish tabish...@gmail.com wrote: On 04/09/2015 02:13 PM, Jim Gomes wrote: Thanks for the explanation. That helps. So, I guess we could discuss the merits of keeping the Board Reports on our wiki, as it does seem somewhat redundant. As long as they exist on the wiki, it would be helpful to have a better indexing system. Perhaps Hiram can offer background as to the purpose and intent of the Board Reports being published on the wiki? Best, Jim On Thu, Apr 9, 2015 at 10:27 AM, Daniel Kulp dk...@apache.org wrote: On Apr 9, 2015, at 1:02 PM, Jim Gomes jgo...@apache.org wrote: Thanks for the link, Dan. I didn't know those were there. I think the main difference here is that link is to the Board Minutes, whereas the ActiveMQ wiki has the Board Report. They seem to be identical, but will they always be? Possibly not, but it would NORMALLY be because the board has decided something should be private (like names of people being voted on or something) in which case it should likely not have been in our public version as well. Doesn't happen too often. Also, they would remove any wiki formatting type things that wouldn't look right in the text form they use. And even if they are identical, do we still need to have the redundancy for trace-ability? For instance, if the Board, for whatever reason, claims they didn't receive the report, we have documentation on the wiki showing the Report was produced. I don't really think the board would care if one was produced or not. It's the chair's job to make sure the board gets the report. If they don't get it, they ask the chair to report again next month. If the chair consistently has issues, they'd likely replace the chair.Another thing to keep in mind: it's the Chairs job to create the report that reflects the state of the community. The chair MAY include the wider community in creating that report, but that's not a requirement. Thus, saying the community produced one, the chair didn't submit it really wouldn't matter at all. Dan That's me just trying to understand the reason for the Board Report page's existence. -Jim On Thu, Apr 9, 2015 at 9:53 AM, Daniel Kulp dk...@apache.org wrote: No objection, but why don't we just delete the page and point at the official records: https://whimsy.apache.org/board/minutes/ActiveMQ.html Dan On Apr 9, 2015, at 12:35 PM, Jim Gomes jgo...@apache.org wrote: I recently went out to look at previous Board Reports ( http://activemq.apache.org/apache-activemq-board-reports.html) and found the current sorting method difficult to deal with. Unless we are required to use the page naming format, I would like to change it to the following format: Apache ActiveMQ Board Report - 2009.01 January Apache ActiveMQ Board Report - 2009.04 April Apache ActiveMQ Board Report - 2009.07 July . . . I would then set it to sort in reverse order so the most recent report is automatically at the top, and they descend in chronological order. The current sorting puts the most recent board report (2015/02) in the middle of the pack, making it difficult to find. Good luck trying to find the report directly prior to that. I will make the changes, unless anyone has other suggestions. Best, Jim -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com I believe that he does this as a place to create and edit them and allow for other members to contribute if they so desire before he submits them. I've edited a couple in the past prior to submission to add CMS or NMS release notes. -- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.redhat.com twitter: @tabish121 blog: http://timbish.blogspot.com/
[jira] [Updated] (AMQ-5716) TopicSubscription gets into endless loop when memory limit reached
[
https://issues.apache.org/jira/browse/AMQ-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michal Kubricht updated AMQ-5716:
-
Affects Version/s: 5.10.2
5.11.1
TopicSubscription gets into endless loop when memory limit reached
--
Key: AMQ-5716
URL: https://issues.apache.org/jira/browse/AMQ-5716
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.7.0, 5.10.2, 5.11.1
Environment: JDK-1.6.0_38
Reporter: Michal Kubricht
Attachments: TopicSubscriptionTest.java, fix_amq_5716.patch,
junit_amq_5716.patch
I might be wrong, but I think that there is a mistake in
{{FilePendingMessageCursor}} in method {{isFull}}.
The logic implemented in code is:
-- isFull returns true when any of memory usage is full or temp usage is
full.
From my point of view this is a mistake and logic should be:
-- isFull returns true only when both of memory usage and temp usage are
full.
The reason why should this be fixed lies in the impact that this mistake
caused us in our project:
TopicSubscription got into endless loop in method {{add(MessageReference)}}
when sending message into topic and memory limit reached 100% (it passed 100%
in our case, but this is complete different story). Following conditions were
fulfilled:
* the dispatched queue reached consumer prefetch size,
* producer flow control was disabled,
* and finally related pending message cursor was full (because of memory
usage).
The temporary storage remained at 0%, it wasn't created at all.
I understand what is the loop good for, it waits until there is a space in
pending message cursor. This is a correct behavior. Anyway, when topic uses
{{FilePendingMessageCursor}}, it loops for no good reason, because the cursor
itself can handle the situation when memory limit is reached/full. It dumps
all messages from memory list into disk list into temporary storage.
I am providing a patch file for this fix and very basic JUnit test for it, if
this is acknowledged as bug and its solution.
Third file is a JUnit test is not considered to be part of commit (it never
ends without any fix provided), but shows as simple as possible the topic
subscription stuck scenario.
If the cursor would return isFull as false, it would solve described
situation. It is sure that I cannot know or even guess that this
implementation of {{FilePendingMessageCursor}} is there for some other
reason, so please take this only as my personal recommendation after some
time spent on analysis of problem in our project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Naming Suggestions?
It is a good name. Do we need to engage trademarks@ for code names? On Thursday, April 9, 2015, Hiram Chirino hi...@hiramchirino.com wrote: I do like Artemis. ActiveMQ Artemis has a nice ring to it. On Wed, Apr 8, 2015 at 11:04 PM, Christian Posta christian.po...@gmail.com javascript:; wrote: Nice, Dan! ArtemisMQ! I like it. On Wed, Apr 8, 2015 at 1:41 PM, Daniel Kulp dk...@apache.org javascript:; wrote: On Apr 8, 2015, at 4:23 PM, Hiram Chirino hi...@hiramchirino.com javascript:; wrote: Naming things is hard. If we gave the hornetq code grant a code name other than HornetQ or ActiveMQ 6, I think we would be avoid lots of TM confusion. Anybody have any suggestion what would be a good name to give it? Hermes?That would be Apollo’s half brother. Or Artemis, Apollo’s twin sister. Dan -- Hiram Chirino Engineering | Red Hat, Inc. hchir...@redhat.com javascript:; | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino -- Daniel Kulp dk...@apache.org javascript:; - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com -- *Christian Posta* twitter: @christianposta http://www.christianposta.com/blog http://fabric8.io -- Hiram Chirino Engineering | Red Hat, Inc. hchir...@redhat.com javascript:; | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino
Re: Naming Suggestions?
Nope. On Thu, Apr 09, 2015 at 09:18:28AM -0400, James Carman wrote: It is a good name. Do we need to engage trademarks@ for code names? On Thursday, April 9, 2015, Hiram Chirino hi...@hiramchirino.com wrote: I do like Artemis. ActiveMQ Artemis has a nice ring to it. On Wed, Apr 8, 2015 at 11:04 PM, Christian Posta christian.po...@gmail.com javascript:; wrote: Nice, Dan! ArtemisMQ! I like it. On Wed, Apr 8, 2015 at 1:41 PM, Daniel Kulp dk...@apache.org javascript:; wrote: On Apr 8, 2015, at 4:23 PM, Hiram Chirino hi...@hiramchirino.com javascript:; wrote: Naming things is hard. If we gave the hornetq code grant a code name other than HornetQ or ActiveMQ 6, I think we would be avoid lots of TM confusion. Anybody have any suggestion what would be a good name to give it? Hermes?That would be Apollo???s half brother. Or Artemis, Apollo???s twin sister. Dan -- Hiram Chirino Engineering | Red Hat, Inc. hchir...@redhat.com javascript:; | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino -- Daniel Kulp dk...@apache.org javascript:; - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com -- *Christian Posta* twitter: @christianposta http://www.christianposta.com/blog http://fabric8.io -- Hiram Chirino Engineering | Red Hat, Inc. hchir...@redhat.com javascript:; | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino
Re: [VOTE] HornetQ Code Donation should use a codename
+1
On Thu, Apr 9, 2015 at 6:06 AM, Hiram Chirino hi...@hiramchirino.com
wrote:
Lots of confusion has occurred since we did not use a code name for
the code donation from the start. Everyone refers to it as HornetQ
which adds to the Trademark confusions. Also the current state of the
code is not ready to become ActiveMQ 6. We can figure out what the
code name should be later with community and trademarks input.
Please choose an option:
[ ] +1 : Rename the hornetq code grant source code from ActiveMQ 6 to
an ActiveMQ ${codename}
[ ] -1 : No don't rename
[ ] 0 : No preference
Vote is open for 72 hours.
--
Hiram Chirino
Engineering | Red Hat, Inc.
hchir...@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino
--
*Christian Posta*
twitter: @christianposta
http://www.christianposta.com/blog
http://fabric8.io
[jira] [Commented] (AMQ-5155) Heartbeat fails in STOMP over WebSockets
[ https://issues.apache.org/jira/browse/AMQ-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14487682#comment-14487682 ] Timothy Bish commented on AMQ-5155: --- This is not a bug, the default address string in that example is: /queue/test which means that the messages are load balanced across connections, try it with /topic/test and it should work as expected. Heartbeat fails in STOMP over WebSockets Key: AMQ-5155 URL: https://issues.apache.org/jira/browse/AMQ-5155 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.9.1, 5.10.0 Reporter: Arjan van den Berg Assignee: Timothy Bish Priority: Minor Fix For: 5.12.0 Attachments: AMQ-5155-jetty8.diff, AMQ-5155-jetty9.diff From AMQ-4740: I receive the following error after establishing a connection and heartbeat through stomp.js. This seems to occur after the 'PING' is sent. -- stomp.js output CONNECTED heart-beat:1,1 session:ID:localhost.localdomain-45596-1396530920609-2:2 server:ActiveMQ/5.10-SNAPSHOT version:1.1 send PING every 1ms check PONG every 1ms PONG PING did not receive server activity for the last 20005ms Whoops! Lost connection to ws://172.16.99.73:61614/stomp - activemq console --- WARN | Transport Connection to: StompSocket_19548821 failed: java.io.IOException Exception in thread ActiveMQ InactivityMonitor Worker java.lang.NullPointerException at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314) at org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:215) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) WARN | Transport Connection to: StompSocket_19548821 failed: java.io.IOException Exception in thread ActiveMQ InactivityMonitor Worker java.lang.NullPointerException at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314) at org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:215) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) For me it looks as if the StompInactivityMonitor is delivering its events to the wrong Transport, i.e. it needs a narrow() when setting it up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-5716) TopicSubscription gets into endless loop when memory limit reached
[
https://issues.apache.org/jira/browse/AMQ-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14488328#comment-14488328
]
Timothy Bish commented on AMQ-5716:
---
This seems valid to me after review. It'd be nice to have [~gtully] take a
look as there could be unforeseen consequences.
TopicSubscription gets into endless loop when memory limit reached
--
Key: AMQ-5716
URL: https://issues.apache.org/jira/browse/AMQ-5716
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.7.0, 5.10.2, 5.11.1
Environment: JDK-1.6.0_38
Reporter: Michal Kubricht
Attachments: TopicSubscriptionTest.java, fix_amq_5716.patch,
junit_amq_5716.patch
I might be wrong, but I think that there is a mistake in
{{FilePendingMessageCursor}} in method {{isFull}}.
The logic implemented in code is:
-- isFull returns true when any of memory usage is full or temp usage is
full.
From my point of view this is a mistake and logic should be:
-- isFull returns true only when both of memory usage and temp usage are
full.
The reason why should this be fixed lies in the impact that this mistake
caused us in our project:
TopicSubscription got into endless loop in method {{add(MessageReference)}}
when sending message into topic and memory limit reached 100% (it passed 100%
in our case, but this is complete different story). Following conditions were
fulfilled:
* the dispatched queue reached consumer prefetch size,
* producer flow control was disabled,
* and finally related pending message cursor was full (because of memory
usage).
The temporary storage remained at 0%, it wasn't created at all.
I understand what is the loop good for, it waits until there is a space in
pending message cursor. This is a correct behavior. Anyway, when topic uses
{{FilePendingMessageCursor}}, it loops for no good reason, because the cursor
itself can handle the situation when memory limit is reached/full. It dumps
all messages from memory list into disk list into temporary storage.
I am providing a patch file for this fix and very basic JUnit test for it, if
this is acknowledged as bug and its solution.
Third file is a JUnit test is not considered to be part of commit (it never
ends without any fix provided), but shows as simple as possible the topic
subscription stuck scenario.
If the cursor would return isFull as false, it would solve described
situation. It is sure that I cannot know or even guess that this
implementation of {{FilePendingMessageCursor}} is there for some other
reason, so please take this only as my personal recommendation after some
time spent on analysis of problem in our project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [DISCUSS] Fix Sorting of Board Reports
No “objection”, but why don’t we just delete the page and point at the official records: https://whimsy.apache.org/board/minutes/ActiveMQ.html Dan On Apr 9, 2015, at 12:35 PM, Jim Gomes jgo...@apache.org wrote: I recently went out to look at previous Board Reports ( http://activemq.apache.org/apache-activemq-board-reports.html) and found the current sorting method difficult to deal with. Unless we are required to use the page naming format, I would like to change it to the following format: Apache ActiveMQ Board Report - 2009.01 January Apache ActiveMQ Board Report - 2009.04 April Apache ActiveMQ Board Report - 2009.07 July . . . I would then set it to sort in reverse order so the most recent report is automatically at the top, and they descend in chronological order. The current sorting puts the most recent board report (2015/02) in the middle of the pack, making it difficult to find. Good luck trying to find the report directly prior to that. I will make the changes, unless anyone has other suggestions. Best, Jim -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
[jira] [Resolved] (AMQ-5665) memory store is broken in 5.11.0 for advisories (and probably other issues as well)
[
https://issues.apache.org/jira/browse/AMQ-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac resolved AMQ-5665.
Resolution: Fixed
Fix Version/s: 5.12.0
Assignee: Dejan Bosanac
I ran into this writing a test for advisories
http://git-wip-us.apache.org/repos/asf/activemq/commit/69767a2f fixes it
The test for another issue I'm working on will be used to verify and guard the
fix
memory store is broken in 5.11.0 for advisories (and probably other issues as
well)
---
Key: AMQ-5665
URL: https://issues.apache.org/jira/browse/AMQ-5665
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.11.0
Reporter: Kevin Burton
Assignee: Dejan Bosanac
Fix For: 5.12.0
We're running 5.10.2 and don't encounter this issue. We're running a
non-persistent broker in production and testing so that's why we found this
issue.
It looks like 5.11.0 introduced this issue.
Essentially Advisories fail to fire.
It looks like it’s a bug with MemoryTransactionStore. Switching to persistent
brokers fixes the problem.
It’s because addMessage calls:
} else {
destination.addMessage(null, message);
}
.. with an explicit null.
the message given is:
2015-03-16 12:54:17,538 WARN [ActiveMQ Transport:
tcp:///127.0.0.1:56468@16161] org.apache.activemq.advisory.AdvisoryBroker
Failed to fire delivered advisory, reason: java.lang.NullPointerException
… and I saw this when I was running mvn test in the main ActiveMQ test suite
(or at least pretty sure I did) so this is happening not just in my code.
The full exception , which I captured by setting a break point is below.
java.lang.NullPointerException
at
org.apache.activemq.advisory.AdvisoryBroker.fireAdvisory(AdvisoryBroker.java:626)
at
org.apache.activemq.advisory.AdvisoryBroker.messageDelivered(AdvisoryBroker.java:397)
at
org.apache.activemq.broker.BrokerFilter.messageDelivered(BrokerFilter.java:349)
at
org.apache.activemq.broker.BrokerFilter.messageDelivered(BrokerFilter.java:349)
at
org.apache.activemq.broker.MutableBrokerFilter.messageDelivered(MutableBrokerFilter.java:360)
at
org.apache.activemq.broker.MutableBrokerFilter.messageDelivered(MutableBrokerFilter.java:360)
at
org.apache.activemq.broker.region.BaseDestination.messageDelivered(BaseDestination.java:518)
at org.apache.activemq.broker.region.Queue.messageSent(Queue.java:1806)
at
org.apache.activemq.broker.region.Queue.doPendingCursorAdditions(Queue.java:794)
at
org.apache.activemq.broker.region.Queue.orderedCursorAdd(Queue.java:875)
at org.apache.activemq.broker.region.Queue.doMessageSend(Queue.java:854)
at org.apache.activemq.broker.region.Queue.send(Queue.java:733)
at
org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:419)
at
org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:468)
at
org.apache.activemq.broker.jmx.ManagedRegionBroker.send(ManagedRegionBroker.java:297)
at org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:152)
at
org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:96)
at
org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:307)
at
org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:157)
at
org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:157)
at
org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:541)
at
org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:768)
at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:334)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:188)
at
org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
at
org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:270)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
at java.lang.Thread.run(Thread.java:724)
... the core issue here looks like the message doesn't have a TransactionId
and MemoryTransactionStore has an addMessages which has a fall through of
addMessage with a null context which then causes the NPE.
Did
Re: [VOTE] HornetQ Code Donation should use a codename
+1
Hiram Chirino mailto:hi...@hiramchirino.com
9 April 2015 14:06
Lots of confusion has occurred since we did not use a code name for
the code donation from the start. Everyone refers to it as HornetQ
which adds to the Trademark confusions. Also the current state of the
code is not ready to become ActiveMQ 6. We can figure out what the
code name should be later with community and trademarks input.
Please choose an option:
[ ] +1 : Rename the hornetq code grant source code from ActiveMQ 6 to
an ActiveMQ ${codename}
[ ] -1 : No don't rename
[ ] 0 : No preference
Vote is open for 72 hours.
Re: [DISCUSS} HornetQ ActiveMQ's next generation
2015-04-09 3:59 GMT+02:00 James Carman ja...@carmanconsulting.com: I am trying to understand the picture that has been painted for us thus far. Maybe you can help me. First of all, the argument for why we need to start from the HornetQ code base is because the current core broker is in such disrepair that we can't fix it (and some feel that we should thank our lucky stars these guys came along when they did to save us all from our own incompetence). Now we are being told that our opinions really shouldn't matter and we should just blindly trust the folks who made it that way (they wrote most of the code, right) when they tell us that this is the right thing to do for the future of ActiveMQ? I'm simply trying to make a point about *my* opinion (I don't think I've ever said *we* or anything like that would lead people to think *my* opinion is the only valid one). I personally don't feel I have the knowledge to judge whether the current broker can be evolved into a next generation non-blocking broker. I also don't have the time and will to improve that knowledge up to the point I could can form my own opinion on this technical issue. Software technologies do evolve, so implying the current architecture is bad now so that the people that wrote it years ago are to blame for it does not look like a valid argument to me. That's judging past decisions in the light of the present knowledge and possibilities. Now, please don't take this as my opinion. I have nothing but respect for the folks you mentioned as well as the other folks who have contributed to this project. I'm just trying to point out how the arguments seem to contradict one another. On Wednesday, April 8, 2015, Guillaume Nodet gno...@apache.org wrote: I think most of the code has been written over the years by James, Rob, Hiram, Garry, Dejan and Tim. I can't speak for them, but I don't recall having read anything from them that could lead me to believe they were in any way reluctant about replacing the activemq broker with the one from the hornetq donation. Rather the opposite, and I certainly trust them on the technical side... 2015-04-08 22:33 GMT+02:00 Tracy Snell tsn...@gmail.com: Who are in the 90% club and are they really all on board with the new broker? On Apr 8, 2015, at 3:52 PM, Guillaume Nodet gno...@apache.org wrote: In this very case, I think this is a technical decision, and my trust clearly goes to the ones that know and wrote 90% of the code, and when they all seem to say the hornetq broker should replace the activemq 5 one, I don't see why I should give it any more second thoughts.
[jira] [Updated] (AMQ-5715) ActiveMQ cannot load decryption password from environment variable
[
https://issues.apache.org/jira/browse/AMQ-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Wils updated AMQ-5715:
--
Description:
decryption of password not working when using wrapper to start ActiveMQ.
The wrapper (bin/linux-x86-64/activemq) is configured to use a RUN_AS_USER=user.
To decrypt the password I am using the EnvironmentStringPBEConfig with an
passwordEnvName.
When:
* login in as user, I can echo the variable given to EnvironmentStringPBEConfig.
* starting ActiveMQ vi sudo service activemq start, it stop immediately after
this logging:
{noformat}
2015-04-09 12:18:04,851 | INFO | Refreshing
org.apache.activemq.xbean.XBeanBrokerFactory$1@3a510e91: startup date [Thu Apr
09 12:18:04 UTC 2015]; root of context hierarchy |
org.apache.activemq.xbean.XBeanBrokerFactory$1 | WrapperSimpleAppMain
2015-04-09 12:18:06,617 | INFO | Loading properties file from URL
[file:../../conf/credentials.properties] |
org.jasypt.spring.properties.EncryptablePropertyPlaceholderConfigurer |
WrapperSimpleAppMain
{noformat}
The issue is that when ActiveMQ is started via a soft link, it will first
resolve himself with absolute path and then call himself again with absolute
path using the *su* command.
The *su* command is not configured to load the RUN_AS_USER environment. It is
missing the *--logging* option. Hence the variable defined in the user
environment and passed in the passwordEnvName is not set.
Patch provided
was:
decryption of password not working when using wrapper to start ActiveMQ.
The wrapper (bin/linux-x86-64/activemq) is configured to use a RUN_AS_USER=user.
To decrypt the password I am using the EnvironmentStringPBEConfig with an
passwordEnvName.
When login in as user, I can echo the variable given to
EnvironmentStringPBEConfig.
When starting ActiveMQ vi sudo service activemq start, it stop immediately
after this logging:
2015-04-09 12:18:04,851 | INFO | Refreshing
org.apache.activemq.xbean.XBeanBrokerFactory$1@3a510e91: startup date [Thu Apr
09 12:18:04 UTC 2015]; root of context hierarchy |
org.apache.activemq.xbean.XBeanBrokerFactory$1 | WrapperSimpleAppMain
2015-04-09 12:18:06,617 | INFO | Loading properties file from URL
[file:../../conf/credentials.properties] |
org.jasypt.spring.properties.EncryptablePropertyPlaceholderConfigurer |
WrapperSimpleAppMain
The issue is that when ActiveMQ is started via a soft link, it will first
resolve himself with absolute path and then call himself again with absolute
path using the *su* command.
The *su* command is not configured to load the RUN_AS_USER environment. It is
missing the *--logging* option. Hence the variable defined in the user
environment and passed in the passwordEnvName is not set.
Patch provided
ActiveMQ cannot load decryption password from environment variable
--
Key: AMQ-5715
URL: https://issues.apache.org/jira/browse/AMQ-5715
Project: ActiveMQ
Issue Type: Bug
Components: Distribution
Affects Versions: 5.11.1
Environment: ubuntu 64 bit server LTS 12.04
java version 1.7.0_07
Java(TM) SE Runtime Environment (build 1.7.0_07-b10)
Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode)
Reporter: Antoine Wils
Priority: Minor
Attachments: activemq.patch
decryption of password not working when using wrapper to start ActiveMQ.
The wrapper (bin/linux-x86-64/activemq) is configured to use a
RUN_AS_USER=user.
To decrypt the password I am using the EnvironmentStringPBEConfig with an
passwordEnvName.
When:
* login in as user, I can echo the variable given to
EnvironmentStringPBEConfig.
* starting ActiveMQ vi sudo service activemq start, it stop immediately after
this logging:
{noformat}
2015-04-09 12:18:04,851 | INFO | Refreshing
org.apache.activemq.xbean.XBeanBrokerFactory$1@3a510e91: startup date [Thu
Apr 09 12:18:04 UTC 2015]; root of context hierarchy |
org.apache.activemq.xbean.XBeanBrokerFactory$1 | WrapperSimpleAppMain
2015-04-09 12:18:06,617 | INFO | Loading properties file from URL
[file:../../conf/credentials.properties] |
org.jasypt.spring.properties.EncryptablePropertyPlaceholderConfigurer |
WrapperSimpleAppMain
{noformat}
The issue is that when ActiveMQ is started via a soft link, it will first
resolve himself with absolute path and then call himself again with absolute
path using the *su* command.
The *su* command is not configured to load the RUN_AS_USER environment. It is
missing the *--logging* option. Hence the variable defined in the user
environment and passed in the passwordEnvName is not set.
Patch provided
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMQ-5715) ActiveMQ cannot load decryption password from environment variable
Antoine Wils created AMQ-5715: - Summary: ActiveMQ cannot load decryption password from environment variable Key: AMQ-5715 URL: https://issues.apache.org/jira/browse/AMQ-5715 Project: ActiveMQ Issue Type: Bug Components: Distribution Affects Versions: 5.11.1 Environment: ubuntu 64 bit server LTS 12.04 java version 1.7.0_07 Java(TM) SE Runtime Environment (build 1.7.0_07-b10) Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode) Reporter: Antoine Wils Priority: Minor decryption of password not working when using wrapper to start ActiveMQ. The wrapper (bin/linux-x86-64/activemq) is configured to use a RUN_AS_USER=user. To decrypt the password I am using the EnvironmentStringPBEConfig with an passwordEnvName. When login in as user, I can echo the variable given to EnvironmentStringPBEConfig. When starting ActiveMQ vi sudo service activemq start, it stop immediately after this logging: 2015-04-09 12:18:04,851 | INFO | Refreshing org.apache.activemq.xbean.XBeanBrokerFactory$1@3a510e91: startup date [Thu Apr 09 12:18:04 UTC 2015]; root of context hierarchy | org.apache.activemq.xbean.XBeanBrokerFactory$1 | WrapperSimpleAppMain 2015-04-09 12:18:06,617 | INFO | Loading properties file from URL [file:../../conf/credentials.properties] | org.jasypt.spring.properties.EncryptablePropertyPlaceholderConfigurer | WrapperSimpleAppMain The issue is that when ActiveMQ is started via a soft link, it will first resolve himself with absolute path and then call himself again with absolute path using the *su* command. The *su* command is not configured to load the RUN_AS_USER environment. It is missing the *--logging* option. Hence the variable defined in the user environment and passed in the passwordEnvName is not set. Patch provided -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] activemq-6 pull request: few changes I found when debugging the te...
Github user asfgit closed the pull request at: https://github.com/apache/activemq-6/pull/203 --- 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. ---
[jira] [Created] (AMQ-5716) TopicSubscription gets into endless loop when memory limit reached
Michal Kubricht created AMQ-5716:
Summary: TopicSubscription gets into endless loop when memory
limit reached
Key: AMQ-5716
URL: https://issues.apache.org/jira/browse/AMQ-5716
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.7.0
Environment: JDK-1.6.0_38
Reporter: Michal Kubricht
I might be wrong, but I think that there is a mistake in
{{FilePendingMessageCursor}} in method {{isFull}}.
The logic implemented in code is:
-- isFull returns true when any of memory usage is full or temp usage is
full.
From my point of view this is a mistake and logic should be:
-- isFull returns true only when both of memory usage and temp usage are
full.
The reason why should this be fixed lies in the impact that this mistake caused
us in our project:
TopicSubscription got into endless loop in method {{add(MessageReference)}}
when sending message into topic and memory limit reached 100% (it passed 100%
in our case, but this is complete different story). Following conditions were
fulfilled:
* the dispatched queue reached consumer prefetch size,
* producer flow control was disabled,
* and finally related pending message cursor was full (because of memory
usage).
The temporary storage remained at 0%, it wasn't created at all.
I understand what is the loop good for, it waits until there is a space in
pending message cursor. This is a correct behavior. Anyway, when topic uses
{{FilePendingMessageCursor}}, it loops for no good reason, because the cursor
itself can handle the situation when memory limit is reached/full. It dumps all
messages from memory list into disk list into temporary storage.
I am providing a patch file for this fix and very basic JUnit test for it, if
this is acknowledged as bug and its solution.
Third file is a JUnit test is not considered to be part of commit, but shows as
simple as possible the topic subscription stuck scenario.
If the cursor would return isFull as false, it would solve described situation.
It is sure that I cannot know or even guess that this implementation of
{{FilePendingMessageCursor}} is there for some other reason, so please take
this only as my personal recommendation after some time spent on analysis of
problem in our project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [DISCUSS] Fix Sorting of Board Reports
renaming makes sense to me. On 9 Apr 2015 19:44, Jim Gomes e.se...@gmail.com wrote: Thanks, Tim. That is a clear and compelling reason to keep them there. With that clarified, does anyone have any comments on the renaming of the pages to improve the indexing? Best, Jim On Thu, Apr 9, 2015 at 11:16 AM, Timothy Bish tabish...@gmail.com wrote: On 04/09/2015 02:13 PM, Jim Gomes wrote: Thanks for the explanation. That helps. So, I guess we could discuss the merits of keeping the Board Reports on our wiki, as it does seem somewhat redundant. As long as they exist on the wiki, it would be helpful to have a better indexing system. Perhaps Hiram can offer background as to the purpose and intent of the Board Reports being published on the wiki? Best, Jim On Thu, Apr 9, 2015 at 10:27 AM, Daniel Kulp dk...@apache.org wrote: On Apr 9, 2015, at 1:02 PM, Jim Gomes jgo...@apache.org wrote: Thanks for the link, Dan. I didn't know those were there. I think the main difference here is that link is to the Board Minutes, whereas the ActiveMQ wiki has the Board Report. They seem to be identical, but will they always be? Possibly not, but it would NORMALLY be because the board has decided something should be private (like names of people being voted on or something) in which case it should likely not have been in our public version as well. Doesn't happen too often. Also, they would remove any wiki formatting type things that wouldn't look right in the text form they use. And even if they are identical, do we still need to have the redundancy for trace-ability? For instance, if the Board, for whatever reason, claims they didn't receive the report, we have documentation on the wiki showing the Report was produced. I don't really think the board would care if one was produced or not. It's the chair's job to make sure the board gets the report. If they don't get it, they ask the chair to report again next month. If the chair consistently has issues, they'd likely replace the chair.Another thing to keep in mind: it's the Chairs job to create the report that reflects the state of the community. The chair MAY include the wider community in creating that report, but that's not a requirement. Thus, saying the community produced one, the chair didn't submit it really wouldn't matter at all. Dan That's me just trying to understand the reason for the Board Report page's existence. -Jim On Thu, Apr 9, 2015 at 9:53 AM, Daniel Kulp dk...@apache.org wrote: No objection, but why don't we just delete the page and point at the official records: https://whimsy.apache.org/board/minutes/ActiveMQ.html Dan On Apr 9, 2015, at 12:35 PM, Jim Gomes jgo...@apache.org wrote: I recently went out to look at previous Board Reports ( http://activemq.apache.org/apache-activemq-board-reports.html) and found the current sorting method difficult to deal with. Unless we are required to use the page naming format, I would like to change it to the following format: Apache ActiveMQ Board Report - 2009.01 January Apache ActiveMQ Board Report - 2009.04 April Apache ActiveMQ Board Report - 2009.07 July . . . I would then set it to sort in reverse order so the most recent report is automatically at the top, and they descend in chronological order. The current sorting puts the most recent board report (2015/02) in the middle of the pack, making it difficult to find. Good luck trying to find the report directly prior to that. I will make the changes, unless anyone has other suggestions. Best, Jim -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com I believe that he does this as a place to create and edit them and allow for other members to contribute if they so desire before he submits them. I've edited a couple in the past prior to submission to add CMS or NMS release notes. -- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.redhat.com twitter: @tabish121 blog: http://timbish.blogspot.com/
[DISCUSS] Fix Sorting of Board Reports
I recently went out to look at previous Board Reports ( http://activemq.apache.org/apache-activemq-board-reports.html) and found the current sorting method difficult to deal with. Unless we are required to use the page naming format, I would like to change it to the following format: Apache ActiveMQ Board Report - 2009.01 January Apache ActiveMQ Board Report - 2009.04 April Apache ActiveMQ Board Report - 2009.07 July . . . I would then set it to sort in reverse order so the most recent report is automatically at the top, and they descend in chronological order. The current sorting puts the most recent board report (2015/02) in the middle of the pack, making it difficult to find. Good luck trying to find the report directly prior to that. I will make the changes, unless anyone has other suggestions. Best, Jim
[jira] [Updated] (AMQ-5715) ActiveMQ cannot load decryption password from environment variable
[ https://issues.apache.org/jira/browse/AMQ-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Wils updated AMQ-5715: -- Attachment: activemq.patch attaching patch ActiveMQ cannot load decryption password from environment variable -- Key: AMQ-5715 URL: https://issues.apache.org/jira/browse/AMQ-5715 Project: ActiveMQ Issue Type: Bug Components: Distribution Affects Versions: 5.11.1 Environment: ubuntu 64 bit server LTS 12.04 java version 1.7.0_07 Java(TM) SE Runtime Environment (build 1.7.0_07-b10) Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode) Reporter: Antoine Wils Priority: Minor Attachments: activemq.patch decryption of password not working when using wrapper to start ActiveMQ. The wrapper (bin/linux-x86-64/activemq) is configured to use a RUN_AS_USER=user. To decrypt the password I am using the EnvironmentStringPBEConfig with an passwordEnvName. When login in as user, I can echo the variable given to EnvironmentStringPBEConfig. When starting ActiveMQ vi sudo service activemq start, it stop immediately after this logging: 2015-04-09 12:18:04,851 | INFO | Refreshing org.apache.activemq.xbean.XBeanBrokerFactory$1@3a510e91: startup date [Thu Apr 09 12:18:04 UTC 2015]; root of context hierarchy | org.apache.activemq.xbean.XBeanBrokerFactory$1 | WrapperSimpleAppMain 2015-04-09 12:18:06,617 | INFO | Loading properties file from URL [file:../../conf/credentials.properties] | org.jasypt.spring.properties.EncryptablePropertyPlaceholderConfigurer | WrapperSimpleAppMain The issue is that when ActiveMQ is started via a soft link, it will first resolve himself with absolute path and then call himself again with absolute path using the *su* command. The *su* command is not configured to load the RUN_AS_USER environment. It is missing the *--logging* option. Hence the variable defined in the user environment and passed in the passwordEnvName is not set. Patch provided -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-5155) Heartbeat fails in STOMP over WebSockets
[ https://issues.apache.org/jira/browse/AMQ-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14487732#comment-14487732 ] Timothy Bish commented on AMQ-5155: --- Keep testing it and report back if you find any other gremlins. Heartbeat fails in STOMP over WebSockets Key: AMQ-5155 URL: https://issues.apache.org/jira/browse/AMQ-5155 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.9.1, 5.10.0 Reporter: Arjan van den Berg Assignee: Timothy Bish Priority: Minor Fix For: 5.12.0 Attachments: AMQ-5155-jetty8.diff, AMQ-5155-jetty9.diff From AMQ-4740: I receive the following error after establishing a connection and heartbeat through stomp.js. This seems to occur after the 'PING' is sent. -- stomp.js output CONNECTED heart-beat:1,1 session:ID:localhost.localdomain-45596-1396530920609-2:2 server:ActiveMQ/5.10-SNAPSHOT version:1.1 send PING every 1ms check PONG every 1ms PONG PING did not receive server activity for the last 20005ms Whoops! Lost connection to ws://172.16.99.73:61614/stomp - activemq console --- WARN | Transport Connection to: StompSocket_19548821 failed: java.io.IOException Exception in thread ActiveMQ InactivityMonitor Worker java.lang.NullPointerException at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314) at org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:215) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) WARN | Transport Connection to: StompSocket_19548821 failed: java.io.IOException Exception in thread ActiveMQ InactivityMonitor Worker java.lang.NullPointerException at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314) at org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:215) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) For me it looks as if the StompInactivityMonitor is delivering its events to the wrong Transport, i.e. it needs a narrow() when setting it up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] HornetQ Code Donation should use a codename
+1
On Thu, Apr 9, 2015 at 9:06 AM, Hiram Chirino hi...@hiramchirino.com wrote:
Lots of confusion has occurred since we did not use a code name for
the code donation from the start. Everyone refers to it as HornetQ
which adds to the Trademark confusions. Also the current state of the
code is not ready to become ActiveMQ 6. We can figure out what the
code name should be later with community and trademarks input.
Please choose an option:
[ ] +1 : Rename the hornetq code grant source code from ActiveMQ 6 to
an ActiveMQ ${codename}
[ ] -1 : No don't rename
[ ] 0 : No preference
Vote is open for 72 hours.
--
Hiram Chirino
Engineering | Red Hat, Inc.
hchir...@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino
--
Clebert Suconic
http://community.jboss.org/people/clebert.suco...@jboss.com
http://clebertsuconic.blogspot.com
[GitHub] activemq-6 pull request: Add Auto JMS queue creation for OpenWire
Github user asfgit closed the pull request at: https://github.com/apache/activemq-6/pull/202 --- 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. ---
Re: [VOTE] HornetQ Code Donation should use a codename
+1
- Original Message -
From: Hiram Chirino hi...@hiramchirino.com
To: ActiveMQ-Developers dev@activemq.apache.org
Sent: Thursday, April 9, 2015 8:06:16 AM
Subject: [VOTE] HornetQ Code Donation should use a codename
Lots of confusion has occurred since we did not use a code name for
the code donation from the start. Everyone refers to it as HornetQ
which adds to the Trademark confusions. Also the current state of the
code is not ready to become ActiveMQ 6. We can figure out what the
code name should be later with community and trademarks input.
Please choose an option:
[ ] +1 : Rename the hornetq code grant source code from ActiveMQ 6 to
an ActiveMQ ${codename}
[ ] -1 : No don't rename
[ ] 0 : No preference
Vote is open for 72 hours.
--
Hiram Chirino
Engineering | Red Hat, Inc.
hchir...@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino
Re: [VOTE] HornetQ Code Donation should use a codename
+1
On Apr 9, 2015 9:06 AM, Hiram Chirino hi...@hiramchirino.com wrote:
Lots of confusion has occurred since we did not use a code name for
the code donation from the start. Everyone refers to it as HornetQ
which adds to the Trademark confusions. Also the current state of the
code is not ready to become ActiveMQ 6. We can figure out what the
code name should be later with community and trademarks input.
Please choose an option:
[ ] +1 : Rename the hornetq code grant source code from ActiveMQ 6 to
an ActiveMQ ${codename}
[ ] -1 : No don't rename
[ ] 0 : No preference
Vote is open for 72 hours.
--
Hiram Chirino
Engineering | Red Hat, Inc.
hchir...@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino
[GitHub] activemq-6 pull request: few changes I found when debugging the te...
GitHub user clebertsuconic opened a pull request: https://github.com/apache/activemq-6/pull/203 few changes I found when debugging the testsuite I was looking for why the testsuite was broken, and I found these in the process You can merge this pull request into a Git repository by running: $ git pull https://github.com/clebertsuconic/activemq-6 master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/203.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #203 commit 1d7bc7ff64f338d9abe8c1480b61a528853c3819 Author: Clebert Suconic clebertsuco...@apache.org Date: 2015-04-02T18:46:42Z avoiding NPE on race This is just making the proper error and adding a test to validate the proper message commit 94889d3d50aa6622845c1c6233428d0def9c3d0b Author: Clebert Suconic clebertsuco...@apache.org Date: 2015-04-02T19:22:56Z Improving test timing HangConsumerTest was hanging for 20 seconds for no real reason. this change will improve the timing on the test commit c8149829e18f6da357fd9664b82176bb9ba9c21d Author: Clebert Suconic clebertsuco...@apache.org Date: 2015-04-06T15:38:59Z Increase version of logging processor There's a bug I found on logging processor, that it's being fixed at alpha2 https://issues.jboss.org/browse/LOGTOOL-88 https://issues.jboss.org/browse/LOGTOOL-87 --- 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. ---
Re: [DISCUSS] Fix Sorting of Board Reports
Thanks for the feedback, everyone. It looks like there's no technical reason for the current naming scheme. I just wanted to make sure I wasn't breaking some kind of formatting requirement from the Board. I'll get them fixed up shortly. Best, Jim On Thu, Apr 9, 2015 at 12:12 PM, Gary Tully gary.tu...@gmail.com wrote: renaming makes sense to me. On 9 Apr 2015 19:44, Jim Gomes e.se...@gmail.com wrote: Thanks, Tim. That is a clear and compelling reason to keep them there. With that clarified, does anyone have any comments on the renaming of the pages to improve the indexing? Best, Jim On Thu, Apr 9, 2015 at 11:16 AM, Timothy Bish tabish...@gmail.com wrote: On 04/09/2015 02:13 PM, Jim Gomes wrote: Thanks for the explanation. That helps. So, I guess we could discuss the merits of keeping the Board Reports on our wiki, as it does seem somewhat redundant. As long as they exist on the wiki, it would be helpful to have a better indexing system. Perhaps Hiram can offer background as to the purpose and intent of the Board Reports being published on the wiki? Best, Jim On Thu, Apr 9, 2015 at 10:27 AM, Daniel Kulp dk...@apache.org wrote: On Apr 9, 2015, at 1:02 PM, Jim Gomes jgo...@apache.org wrote: Thanks for the link, Dan. I didn't know those were there. I think the main difference here is that link is to the Board Minutes, whereas the ActiveMQ wiki has the Board Report. They seem to be identical, but will they always be? Possibly not, but it would NORMALLY be because the board has decided something should be private (like names of people being voted on or something) in which case it should likely not have been in our public version as well. Doesn't happen too often. Also, they would remove any wiki formatting type things that wouldn't look right in the text form they use. And even if they are identical, do we still need to have the redundancy for trace-ability? For instance, if the Board, for whatever reason, claims they didn't receive the report, we have documentation on the wiki showing the Report was produced. I don't really think the board would care if one was produced or not. It's the chair's job to make sure the board gets the report. If they don't get it, they ask the chair to report again next month. If the chair consistently has issues, they'd likely replace the chair.Another thing to keep in mind: it's the Chairs job to create the report that reflects the state of the community. The chair MAY include the wider community in creating that report, but that's not a requirement. Thus, saying the community produced one, the chair didn't submit it really wouldn't matter at all. Dan That's me just trying to understand the reason for the Board Report page's existence. -Jim On Thu, Apr 9, 2015 at 9:53 AM, Daniel Kulp dk...@apache.org wrote: No objection, but why don't we just delete the page and point at the official records: https://whimsy.apache.org/board/minutes/ActiveMQ.html Dan On Apr 9, 2015, at 12:35 PM, Jim Gomes jgo...@apache.org wrote: I recently went out to look at previous Board Reports ( http://activemq.apache.org/apache-activemq-board-reports.html) and found the current sorting method difficult to deal with. Unless we are required to use the page naming format, I would like to change it to the following format: Apache ActiveMQ Board Report - 2009.01 January Apache ActiveMQ Board Report - 2009.04 April Apache ActiveMQ Board Report - 2009.07 July . . . I would then set it to sort in reverse order so the most recent report is automatically at the top, and they descend in chronological order. The current sorting puts the most recent board report (2015/02) in the middle of the pack, making it difficult to find. Good luck trying to find the report directly prior to that. I will make the changes, unless anyone has other suggestions. Best, Jim -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com I believe that he does this as a place to create and edit them and allow for other members to contribute if they so desire before he submits them. I've edited a couple in the past prior to submission to add CMS or NMS release notes. -- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.redhat.com twitter: @tabish121 blog: http://timbish.blogspot.com/
Re: High Availablity with journal messages
In addition does HA imply redundancy on both storage(messages are duplicated across nodes) as well as connectivity(if a node goes down one would still be able to post to another) -- View this message in context: http://activemq.2283324.n4.nabble.com/High-Availablity-with-journal-messages-tp4694614p4694616.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: [VOTE] HornetQ Code Donation should use a codename
+1
On 9 Apr 2015 14:06, Hiram Chirino hi...@hiramchirino.com wrote:
Lots of confusion has occurred since we did not use a code name for
the code donation from the start. Everyone refers to it as HornetQ
which adds to the Trademark confusions. Also the current state of the
code is not ready to become ActiveMQ 6. We can figure out what the
code name should be later with community and trademarks input.
Please choose an option:
[ ] +1 : Rename the hornetq code grant source code from ActiveMQ 6 to
an ActiveMQ ${codename}
[ ] -1 : No don't rename
[ ] 0 : No preference
Vote is open for 72 hours.
--
Hiram Chirino
Engineering | Red Hat, Inc.
hchir...@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino
Re: [DISCUSS] Fix Sorting of Board Reports
On Apr 9, 2015, at 1:02 PM, Jim Gomes jgo...@apache.org wrote: Thanks for the link, Dan. I didn't know those were there. I think the main difference here is that link is to the Board Minutes, whereas the ActiveMQ wiki has the Board Report. They seem to be identical, but will they always be? Possibly not, but it would NORMALLY be because the board has decided something should be private (like names of people being voted on or something) in which case it should likely not have been in our public version as well. Doesn’t happen too often. Also, they would remove any “wiki formatting” type things that wouldn’t look right in the text form they use. And even if they are identical, do we still need to have the redundancy for trace-ability? For instance, if the Board, for whatever reason, claims they didn't receive the report, we have documentation on the wiki showing the Report was produced. I don’t really think the board would care if one was produced or not. It’s the chair’s job to make sure the board gets the report. If they don’t get it, they ask the chair to report again next month. If the chair consistently has issues, they’d likely replace the chair.Another thing to keep in mind: it’s the Chairs job to create the report that reflects the state of the community. The chair MAY include the wider community in creating that report, but that’s not a requirement. Thus, saying “the community produced one, the chair didn’t submit it” really wouldn’t matter at all. Dan That's me just trying to understand the reason for the Board Report page's existence. -Jim On Thu, Apr 9, 2015 at 9:53 AM, Daniel Kulp dk...@apache.org wrote: No objection, but why don't we just delete the page and point at the official records: https://whimsy.apache.org/board/minutes/ActiveMQ.html Dan On Apr 9, 2015, at 12:35 PM, Jim Gomes jgo...@apache.org wrote: I recently went out to look at previous Board Reports ( http://activemq.apache.org/apache-activemq-board-reports.html) and found the current sorting method difficult to deal with. Unless we are required to use the page naming format, I would like to change it to the following format: Apache ActiveMQ Board Report - 2009.01 January Apache ActiveMQ Board Report - 2009.04 April Apache ActiveMQ Board Report - 2009.07 July . . . I would then set it to sort in reverse order so the most recent report is automatically at the top, and they descend in chronological order. The current sorting puts the most recent board report (2015/02) in the middle of the pack, making it difficult to find. Good luck trying to find the report directly prior to that. I will make the changes, unless anyone has other suggestions. Best, Jim -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
Re: [DISCUSS} HornetQ ActiveMQ's next generation
On Thu, Apr 09, 2015 at 08:51:31AM +0200, Guillaume Nodet wrote: 2015-04-09 3:59 GMT+02:00 James Carman ja...@carmanconsulting.com: I am trying to understand the picture that has been painted for us thus far. Maybe you can help me. First of all, the argument for why we need to start from the HornetQ code base is because the current core broker is in such disrepair that we can't fix it (and some feel that we should thank our lucky stars these guys came along when they did to save us all from our own incompetence). Now we are being told that our opinions really shouldn't matter and we should just blindly trust the folks who made it that way (they wrote most of the code, right) when they tell us that this is the right thing to do for the future of ActiveMQ? I'm simply trying to make a point about *my* opinion (I don't think I've ever said *we* or anything like that would lead people to think *my* opinion is the only valid one). No. You haven't stated it that way, that I recall. But you have implied that. I've seen this technique of argument used here at the ASF over the past 15+ years. Some kind of bullshit argument, then the person gets called on it, and they respond oh, that's not really what I meant, and weasel out of any single bad action. But the *summation* of their interactions is destructive. I've seen this over and over. Given the years and years of watching people try this, it becomes rapidly apparent when they use this approach. I have a long memory for people who do this, Guillaume. At the core, it is a technique used to divide. Always has been. I've seen it destroy Apache communities. Literally. Needless to say, it makes me very angry. Just stop with the history. Stop with the blame. Pick a codename, and never mention HornetQ again. Get the *whole* community involved in the new codebase (the commit statistics suck, on this newly-arrived code). Then get a release out under that new name. Get some feedback. When the community can produce a release, and start working with users around that release... it will bring you all together. And give you something to evaluate for a future path. -g
[jira] [Commented] (AMQ-5716) TopicSubscription gets into endless loop when memory limit reached
[
https://issues.apache.org/jira/browse/AMQ-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14488325#comment-14488325
]
Timothy Bish commented on AMQ-5716:
---
Some work in this area already for related issue.
TopicSubscription gets into endless loop when memory limit reached
--
Key: AMQ-5716
URL: https://issues.apache.org/jira/browse/AMQ-5716
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.7.0, 5.10.2, 5.11.1
Environment: JDK-1.6.0_38
Reporter: Michal Kubricht
Attachments: TopicSubscriptionTest.java, fix_amq_5716.patch,
junit_amq_5716.patch
I might be wrong, but I think that there is a mistake in
{{FilePendingMessageCursor}} in method {{isFull}}.
The logic implemented in code is:
-- isFull returns true when any of memory usage is full or temp usage is
full.
From my point of view this is a mistake and logic should be:
-- isFull returns true only when both of memory usage and temp usage are
full.
The reason why should this be fixed lies in the impact that this mistake
caused us in our project:
TopicSubscription got into endless loop in method {{add(MessageReference)}}
when sending message into topic and memory limit reached 100% (it passed 100%
in our case, but this is complete different story). Following conditions were
fulfilled:
* the dispatched queue reached consumer prefetch size,
* producer flow control was disabled,
* and finally related pending message cursor was full (because of memory
usage).
The temporary storage remained at 0%, it wasn't created at all.
I understand what is the loop good for, it waits until there is a space in
pending message cursor. This is a correct behavior. Anyway, when topic uses
{{FilePendingMessageCursor}}, it loops for no good reason, because the cursor
itself can handle the situation when memory limit is reached/full. It dumps
all messages from memory list into disk list into temporary storage.
I am providing a patch file for this fix and very basic JUnit test for it, if
this is acknowledged as bug and its solution.
Third file is a JUnit test is not considered to be part of commit (it never
ends without any fix provided), but shows as simple as possible the topic
subscription stuck scenario.
If the cursor would return isFull as false, it would solve described
situation. It is sure that I cannot know or even guess that this
implementation of {{FilePendingMessageCursor}} is there for some other
reason, so please take this only as my personal recommendation after some
time spent on analysis of problem in our project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMQ-5716) TopicSubscription gets into endless loop when memory limit reached
[
https://issues.apache.org/jira/browse/AMQ-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michal Kubricht updated AMQ-5716:
-
Attachment: TopicSubscriptionTest.java
junit_amq_5716.patch
fix_amq_5716.patch
TopicSubscription gets into endless loop when memory limit reached
--
Key: AMQ-5716
URL: https://issues.apache.org/jira/browse/AMQ-5716
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.7.0
Environment: JDK-1.6.0_38
Reporter: Michal Kubricht
Attachments: TopicSubscriptionTest.java, fix_amq_5716.patch,
junit_amq_5716.patch
I might be wrong, but I think that there is a mistake in
{{FilePendingMessageCursor}} in method {{isFull}}.
The logic implemented in code is:
-- isFull returns true when any of memory usage is full or temp usage is
full.
From my point of view this is a mistake and logic should be:
-- isFull returns true only when both of memory usage and temp usage are
full.
The reason why should this be fixed lies in the impact that this mistake
caused us in our project:
TopicSubscription got into endless loop in method {{add(MessageReference)}}
when sending message into topic and memory limit reached 100% (it passed 100%
in our case, but this is complete different story). Following conditions were
fulfilled:
* the dispatched queue reached consumer prefetch size,
* producer flow control was disabled,
* and finally related pending message cursor was full (because of memory
usage).
The temporary storage remained at 0%, it wasn't created at all.
I understand what is the loop good for, it waits until there is a space in
pending message cursor. This is a correct behavior. Anyway, when topic uses
{{FilePendingMessageCursor}}, it loops for no good reason, because the cursor
itself can handle the situation when memory limit is reached/full. It dumps
all messages from memory list into disk list into temporary storage.
I am providing a patch file for this fix and very basic JUnit test for it, if
this is acknowledged as bug and its solution.
Third file is a JUnit test is not considered to be part of commit (it never
ends without any fix provided), but shows as simple as possible the topic
subscription stuck scenario.
If the cursor would return isFull as false, it would solve described
situation. It is sure that I cannot know or even guess that this
implementation of {{FilePendingMessageCursor}} is there for some other
reason, so please take this only as my personal recommendation after some
time spent on analysis of problem in our project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Future of Apollo...
Well, I've stopped working on apollo since the community aspects of it did not seem to be getting much traction. If your using it and find any problems with it, please send in patches :) You part of solving the community problem and help maintain and push apollo forward. On Thu, Apr 9, 2015 at 1:09 PM, redboy1972 redboy1...@live.com wrote: I tested many brokers and am very impressed with the performance characteristics of Apollo. I work for a large company and the broker is going to be the backbone of a large infrastructure project. The issue is that while Apollo does well in my tests, its future seems uncertain. Especially being a subproject of a future ActiveMQ 6 release. 1) Will there be continued bug fixes should we run into something and for how long? 2) Any general timeline for inclusion of Reactor Based Thread Model into ActiveMQ? Our ship timeline is Q4 2015. -- View this message in context: http://activemq.2283324.n4.nabble.com/Future-of-Apollo-tp4694644.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] [Created] (ACTIVEMQ6-96) Implement administrative limit for the maximum client connections allowed
Justin Bertram created ACTIVEMQ6-96: --- Summary: Implement administrative limit for the maximum client connections allowed Key: ACTIVEMQ6-96 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-96 Project: Apache ActiveMQ 6 Issue Type: Sub-task Reporter: Justin Bertram Assignee: Justin Bertram Fix For: 6.1.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [DISCUSS] Fix Sorting of Board Reports
Thanks for the link, Dan. I didn't know those were there. I think the main difference here is that link is to the Board Minutes, whereas the ActiveMQ wiki has the Board Report. They seem to be identical, but will they always be? And even if they are identical, do we still need to have the redundancy for trace-ability? For instance, if the Board, for whatever reason, claims they didn't receive the report, we have documentation on the wiki showing the Report was produced. That's me just trying to understand the reason for the Board Report page's existence. -Jim On Thu, Apr 9, 2015 at 9:53 AM, Daniel Kulp dk...@apache.org wrote: No objection, but why don't we just delete the page and point at the official records: https://whimsy.apache.org/board/minutes/ActiveMQ.html Dan On Apr 9, 2015, at 12:35 PM, Jim Gomes jgo...@apache.org wrote: I recently went out to look at previous Board Reports ( http://activemq.apache.org/apache-activemq-board-reports.html) and found the current sorting method difficult to deal with. Unless we are required to use the page naming format, I would like to change it to the following format: Apache ActiveMQ Board Report - 2009.01 January Apache ActiveMQ Board Report - 2009.04 April Apache ActiveMQ Board Report - 2009.07 July . . . I would then set it to sort in reverse order so the most recent report is automatically at the top, and they descend in chronological order. The current sorting puts the most recent board report (2015/02) in the middle of the pack, making it difficult to find. Good luck trying to find the report directly prior to that. I will make the changes, unless anyone has other suggestions. Best, Jim -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
Re: [VOTE] HornetQ Code Donation should use a codename
On 04/09/2015 09:06 AM, Hiram Chirino wrote:
Lots of confusion has occurred since we did not use a code name for
the code donation from the start. Everyone refers to it as HornetQ
which adds to the Trademark confusions. Also the current state of the
code is not ready to become ActiveMQ 6. We can figure out what the
code name should be later with community and trademarks input.
Please choose an option:
[ ] +1 : Rename the hornetq code grant source code from ActiveMQ 6 to
an ActiveMQ ${codename}
[ ] -1 : No don't rename
[ ] 0 : No preference
Vote is open for 72 hours.
+1
--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
twitter: @tabish121
blog: http://timbish.blogspot.com/
Re: [DISCUSS] Fix Sorting of Board Reports
On 04/09/2015 02:13 PM, Jim Gomes wrote: Thanks for the explanation. That helps. So, I guess we could discuss the merits of keeping the Board Reports on our wiki, as it does seem somewhat redundant. As long as they exist on the wiki, it would be helpful to have a better indexing system. Perhaps Hiram can offer background as to the purpose and intent of the Board Reports being published on the wiki? Best, Jim On Thu, Apr 9, 2015 at 10:27 AM, Daniel Kulp dk...@apache.org wrote: On Apr 9, 2015, at 1:02 PM, Jim Gomes jgo...@apache.org wrote: Thanks for the link, Dan. I didn't know those were there. I think the main difference here is that link is to the Board Minutes, whereas the ActiveMQ wiki has the Board Report. They seem to be identical, but will they always be? Possibly not, but it would NORMALLY be because the board has decided something should be private (like names of people being voted on or something) in which case it should likely not have been in our public version as well. Doesn't happen too often. Also, they would remove any wiki formatting type things that wouldn't look right in the text form they use. And even if they are identical, do we still need to have the redundancy for trace-ability? For instance, if the Board, for whatever reason, claims they didn't receive the report, we have documentation on the wiki showing the Report was produced. I don't really think the board would care if one was produced or not. It's the chair's job to make sure the board gets the report. If they don't get it, they ask the chair to report again next month. If the chair consistently has issues, they'd likely replace the chair.Another thing to keep in mind: it's the Chairs job to create the report that reflects the state of the community. The chair MAY include the wider community in creating that report, but that's not a requirement. Thus, saying the community produced one, the chair didn't submit it really wouldn't matter at all. Dan That's me just trying to understand the reason for the Board Report page's existence. -Jim On Thu, Apr 9, 2015 at 9:53 AM, Daniel Kulp dk...@apache.org wrote: No objection, but why don't we just delete the page and point at the official records: https://whimsy.apache.org/board/minutes/ActiveMQ.html Dan On Apr 9, 2015, at 12:35 PM, Jim Gomes jgo...@apache.org wrote: I recently went out to look at previous Board Reports ( http://activemq.apache.org/apache-activemq-board-reports.html) and found the current sorting method difficult to deal with. Unless we are required to use the page naming format, I would like to change it to the following format: Apache ActiveMQ Board Report - 2009.01 January Apache ActiveMQ Board Report - 2009.04 April Apache ActiveMQ Board Report - 2009.07 July . . . I would then set it to sort in reverse order so the most recent report is automatically at the top, and they descend in chronological order. The current sorting puts the most recent board report (2015/02) in the middle of the pack, making it difficult to find. Good luck trying to find the report directly prior to that. I will make the changes, unless anyone has other suggestions. Best, Jim -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com I believe that he does this as a place to create and edit them and allow for other members to contribute if they so desire before he submits them. I've edited a couple in the past prior to submission to add CMS or NMS release notes. -- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.redhat.com twitter: @tabish121 blog: http://timbish.blogspot.com/
High Availablity with journal messages
I am new to activemq. We are prototyping a few queuing frameworks. 2 Of the things we require is High Availability and journaling. I understand that you can get HA with the Master/slave setup. Would this also guarantee durability. ie no messages that has been posted will be lost? Another thing we require is journal that keeps all the messages that have been taken of the queue so that we can replay them at a later stage. Is this possible and what is the best configuration for this? -- View this message in context: http://activemq.2283324.n4.nabble.com/High-Availablity-with-journal-messages-tp4694614.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: [VOTE] HornetQ Code Donation should use a codename
+1
On 09/04/15 14:06, Hiram Chirino wrote:
Lots of confusion has occurred since we did not use a code name for
the code donation from the start. Everyone refers to it as HornetQ
which adds to the Trademark confusions. Also the current state of the
code is not ready to become ActiveMQ 6. We can figure out what the
code name should be later with community and trademarks input.
Please choose an option:
[ ] +1 : Rename the hornetq code grant source code from ActiveMQ 6 to
an ActiveMQ ${codename}
[ ] -1 : No don't rename
[ ] 0 : No preference
Vote is open for 72 hours.
Re: Naming Suggestions?
I do like Artemis. ActiveMQ Artemis has a nice ring to it. On Wed, Apr 8, 2015 at 11:04 PM, Christian Posta christian.po...@gmail.com wrote: Nice, Dan! ArtemisMQ! I like it. On Wed, Apr 8, 2015 at 1:41 PM, Daniel Kulp dk...@apache.org wrote: On Apr 8, 2015, at 4:23 PM, Hiram Chirino hi...@hiramchirino.com wrote: Naming things is hard. If we gave the hornetq code grant a code name other than HornetQ or ActiveMQ 6, I think we would be avoid lots of TM confusion. Anybody have any suggestion what would be a good name to give it? Hermes?That would be Apollo’s half brother. Or Artemis, Apollo’s twin sister. Dan -- Hiram Chirino Engineering | Red Hat, Inc. hchir...@redhat.com | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com -- *Christian Posta* twitter: @christianposta http://www.christianposta.com/blog http://fabric8.io -- Hiram Chirino Engineering | Red Hat, Inc. hchir...@redhat.com | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino
[jira] [Updated] (AMQ-5716) TopicSubscription gets into endless loop when memory limit reached
[
https://issues.apache.org/jira/browse/AMQ-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michal Kubricht updated AMQ-5716:
-
Description:
I might be wrong, but I think that there is a mistake in
{{FilePendingMessageCursor}} in method {{isFull}}.
The logic implemented in code is:
-- isFull returns true when any of memory usage is full or temp usage is
full.
From my point of view this is a mistake and logic should be:
-- isFull returns true only when both of memory usage and temp usage are
full.
The reason why should this be fixed lies in the impact that this mistake caused
us in our project:
TopicSubscription got into endless loop in method {{add(MessageReference)}}
when sending message into topic and memory limit reached 100% (it passed 100%
in our case, but this is complete different story). Following conditions were
fulfilled:
* the dispatched queue reached consumer prefetch size,
* producer flow control was disabled,
* and finally related pending message cursor was full (because of memory
usage).
The temporary storage remained at 0%, it wasn't created at all.
I understand what is the loop good for, it waits until there is a space in
pending message cursor. This is a correct behavior. Anyway, when topic uses
{{FilePendingMessageCursor}}, it loops for no good reason, because the cursor
itself can handle the situation when memory limit is reached/full. It dumps all
messages from memory list into disk list into temporary storage.
I am providing a patch file for this fix and very basic JUnit test for it, if
this is acknowledged as bug and its solution.
Third file is a JUnit test is not considered to be part of commit (it never
ends without any fix provided), but shows as simple as possible the topic
subscription stuck scenario.
If the cursor would return isFull as false, it would solve described situation.
It is sure that I cannot know or even guess that this implementation of
{{FilePendingMessageCursor}} is there for some other reason, so please take
this only as my personal recommendation after some time spent on analysis of
problem in our project.
was:
I might be wrong, but I think that there is a mistake in
{{FilePendingMessageCursor}} in method {{isFull}}.
The logic implemented in code is:
-- isFull returns true when any of memory usage is full or temp usage is
full.
From my point of view this is a mistake and logic should be:
-- isFull returns true only when both of memory usage and temp usage are
full.
The reason why should this be fixed lies in the impact that this mistake caused
us in our project:
TopicSubscription got into endless loop in method {{add(MessageReference)}}
when sending message into topic and memory limit reached 100% (it passed 100%
in our case, but this is complete different story). Following conditions were
fulfilled:
* the dispatched queue reached consumer prefetch size,
* producer flow control was disabled,
* and finally related pending message cursor was full (because of memory
usage).
The temporary storage remained at 0%, it wasn't created at all.
I understand what is the loop good for, it waits until there is a space in
pending message cursor. This is a correct behavior. Anyway, when topic uses
{{FilePendingMessageCursor}}, it loops for no good reason, because the cursor
itself can handle the situation when memory limit is reached/full. It dumps all
messages from memory list into disk list into temporary storage.
I am providing a patch file for this fix and very basic JUnit test for it, if
this is acknowledged as bug and its solution.
Third file is a JUnit test is not considered to be part of commit, but shows as
simple as possible the topic subscription stuck scenario.
If the cursor would return isFull as false, it would solve described situation.
It is sure that I cannot know or even guess that this implementation of
{{FilePendingMessageCursor}} is there for some other reason, so please take
this only as my personal recommendation after some time spent on analysis of
problem in our project.
TopicSubscription gets into endless loop when memory limit reached
--
Key: AMQ-5716
URL: https://issues.apache.org/jira/browse/AMQ-5716
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.7.0
Environment: JDK-1.6.0_38
Reporter: Michal Kubricht
I might be wrong, but I think that there is a mistake in
{{FilePendingMessageCursor}} in method {{isFull}}.
The logic implemented in code is:
-- isFull returns true when any of memory usage is full or temp usage is
full.
From my point of view this is a mistake and logic should be:
-- isFull returns true only when both of memory usage and temp usage are
full.
The reason why should this be fixed lies in the impact that this
Re: [VOTE] HornetQ Code Donation should use a codename
+1
On Apr 9, 2015 7:25 AM, Clebert Suconic clebert.suco...@gmail.com wrote:
+1
On Thu, Apr 9, 2015 at 9:06 AM, Hiram Chirino hi...@hiramchirino.com
wrote:
Lots of confusion has occurred since we did not use a code name for
the code donation from the start. Everyone refers to it as HornetQ
which adds to the Trademark confusions. Also the current state of the
code is not ready to become ActiveMQ 6. We can figure out what the
code name should be later with community and trademarks input.
Please choose an option:
[ ] +1 : Rename the hornetq code grant source code from ActiveMQ 6 to
an ActiveMQ ${codename}
[ ] -1 : No don't rename
[ ] 0 : No preference
Vote is open for 72 hours.
--
Hiram Chirino
Engineering | Red Hat, Inc.
hchir...@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino
--
Clebert Suconic
http://community.jboss.org/people/clebert.suco...@jboss.com
http://clebertsuconic.blogspot.com
Future of Apollo...
I tested many brokers and am very impressed with the performance characteristics of Apollo. I work for a large company and the broker is going to be the backbone of a large infrastructure project. The issue is that while Apollo does well in my tests, its future seems uncertain. Especially being a subproject of a future ActiveMQ 6 release. 1) Will there be continued bug fixes should we run into something and for how long? 2) Any general timeline for inclusion of Reactor Based Thread Model into ActiveMQ? Our ship timeline is Q4 2015. -- View this message in context: http://activemq.2283324.n4.nabble.com/Future-of-Apollo-tp4694644.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
