Hudson build is back to normal: ActiveMQ » ActiveMQ :: RA #136

See

Hudson build is back to normal: ActiveMQ » ActiveMQ :: Atomikos System Test #136

See

Hudson build is back to normal: ActiveMQ » ActiveMQ :: Memory Usage Test Plugin #136

See

Hudson build is back to normal: ActiveMQ » ActiveMQ Tooling #136

See

Hudson build is back to normal: Ac tiveMQ » ActiveMQ :: Optional #136

See

Hudson build is back to normal: ActiveMQ » ActiveMQ :: RAR #136

See

Hudson build is back to normal: A ctiveMQ » ActiveMQ :: Run Jar #136

See

Hudson build is back to normal: ActiveMQ » ActiveMQ :: Camel #136

See

Hudson build is unstable: ActiveMQ » ActiveMQ :: Core #136

See

Hudson build is back to normal: Active MQ » ActiveMQ :: JPA Message Store #136

See

Hudson build is back to normal: ActiveMQ » ActiveMQ :: Pool #136

See

Hudson build is back to normal: A ctiveMQ » ActiveMQ User Guide #136

See

Hudson build is back to normal: ActiveMQ » ActiveMQ :: Web #136

See

Hudson build is back to normal: Act iveMQ » ActiveMQ :: File Server #136

See

Hudson build is back to normal: A ctiveMQ » ActiveMQ :: Console #136

See

Hudson build is back to normal: ActiveMQ » ActiveMQ :: Performance Test Plugin #136

See

Hudson build is back to normal: Act iveMQ » ActiveMQ :: Web Console #136

See

Hudson build is back to normal: Activ eMQ » ActiveMQ :: StartUp Plugin #136

See

Hudson build is back to normal: ActiveMQ » ActiveMQ :: XMPP #136

See

Hudson build is back to normal: Ac tiveMQ » ActiveMQ :: Web Demo #136

See

[jira] Created: (AMQ-2409) Document the 'daemon' option to the TCP transport

Document the 'daemon' option to the TCP transport - Key: AMQ-2409 URL: https://issues.apache.org/activemq/browse/AMQ-2409 Project: ActiveMQ Issue Type: Task Components: Transport

[jira] Updated: (AMQ-2401) Hangs in fan-in to DUPS_OK_ACKNOWLEDGE queue receivers

[ https://issues.apache.org/activemq/browse/AMQ-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated AMQ-2401: --- Attachment: AMQ-2401.patch Attaching patch which changes the DUPS_OK queue consumer behavior to mat

[jira] Resolved: (AMQ-2404) Frequent kahadb messages: "KahaDB long enqueue time: Journal Add Took: 0 ms, Index Update took 125 ms"

[ https://issues.apache.org/activemq/browse/AMQ-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino resolved AMQ-2404. Resolution: Fixed committed. > Frequent kahadb messages: "KahaDB long enqueue time: Journal Add

[jira] Commented: (AMQ-2401) Hangs in fan-in to DUPS_OK_ACKNOWLEDGE queue receivers

[ https://issues.apache.org/activemq/browse/AMQ-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54471#action_54471 ] Hiram Chirino commented on AMQ-2401: I think the safest bet will be to change the client so

[jira] Commented: (AMQ-2404) Frequent kahadb messages: "KahaDB long enqueue time: Journal Add Took: 0 ms, Index Update took 125 ms"

[ https://issues.apache.org/activemq/browse/AMQ-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54470#action_54470 ] Hiram Chirino commented on AMQ-2404: You will now be able to use a system property to set w

[jira] Commented: (AMQ-2404) Frequent kahadb messages: "KahaDB long enqueue time: Journal Add Took: 0 ms, Index Update took 125 ms"

[ https://issues.apache.org/activemq/browse/AMQ-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54469#action_54469 ] Hiram Chirino commented on AMQ-2404: well I assume you bean reduce the logging level instea

[jira] Resolved: (AMQ-2407) New tool to manually inspect/audit the amqPersistenceAdapter's journal files.

[ https://issues.apache.org/activemq/browse/AMQ-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino resolved AMQ-2407. Resolution: Fixed committed contribution. > New tool to manually inspect/audit the amqPersisten

[jira] Resolved: (AMQ-2408) New HTTP based discovery agent

[ https://issues.apache.org/activemq/browse/AMQ-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino resolved AMQ-2408. Resolution: Fixed committed contribution. > New HTTP based discovery agent > --

[jira] Created: (AMQ-2407) New tool to manually inspect/audit the amqPersistenceAdapter's journal files.

New tool to manually inspect/audit the amqPersistenceAdapter's journal files. - Key: AMQ-2407 URL: https://issues.apache.org/activemq/browse/AMQ-2407 Project: ActiveMQ

[jira] Created: (AMQ-2408) New HTTP based discovery agent

New HTTP based discovery agent -- Key: AMQ-2408 URL: https://issues.apache.org/activemq/browse/AMQ-2408 Project: ActiveMQ Issue Type: New Feature Reporter: Hiram Chirino It's sometimes handy to be ab

[jira] Updated: (AMQ-2406) activemq-xmpp contains some System.out.println statements

[ https://issues.apache.org/activemq/browse/AMQ-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stan Lewis updated AMQ-2406: Attachment: patch.txt > activemq-xmpp contains some System.out.println statements > -

[jira] Created: (AMQ-2406) activemq-xmpp contains some System.out.println statements

activemq-xmpp contains some System.out.println statements - Key: AMQ-2406 URL: https://issues.apache.org/activemq/browse/AMQ-2406 Project: ActiveMQ Issue Type: Improvement Com

Re: producerFlowControl

On Wed, Sep 23, 2009 at 7:24 AM, Rob Davies wrote: > hopefully - depends what we decide - 5.3 still not released. > Flow control is enabled by default in 5.2 - we disabled it in trunk - but > now I'm suggesting we revert back to having it enabled in trunk and > hopefully 5.3 too +1 Yeah, I agree

[jira] Commented: (AMQ-1732) Add an Individual acknowledge mode for message consumption

[ https://issues.apache.org/activemq/browse/AMQ-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54464#action_54464 ] Bruce Snyder commented on AMQ-1732: --- See [revision 657817|http://svn.apache.org/viewvc?view=r

[jira] Resolved: (AMQ-2405) Support gracefull data recovery in even when datafile are corrupted.

[ https://issues.apache.org/activemq/browse/AMQ-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino resolved AMQ-2405. Resolution: Fixed Fix Version/s: 5.3.0 patch applied. > Support gracefull data recovery i

[jira] Created: (AMQ-2405) Support gracefull data recovery in even when datafile are corrupted.

Support gracefull data recovery in even when datafile are corrupted. - Key: AMQ-2405 URL: https://issues.apache.org/activemq/browse/AMQ-2405 Project: ActiveMQ Issue Type: N

[jira] Created: (AMQ-2404) Frequent kahadb messages: "KahaDB long enqueue time: Journal Add Took: 0 ms, Index Update took 125 ms"

Frequent kahadb messages: "KahaDB long enqueue time: Journal Add Took: 0 ms, Index Update took 125 ms" --- Key: AMQ-2404 URL: https://issues.apache.org/activemq/b

[jira] Resolved: (AMQ-2403) Enable producer flow control again

[ https://issues.apache.org/activemq/browse/AMQ-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-2403. - Resolution: Fixed Fixed by SVN revision 818147 > Enable producer flow control again >

Re: producerFlowControl

Yeah.. disabling flow control was bandage to the problem. If the root issue has been fixed, I'm all for enabling it again since it then you can have a 'throughput' oriented config by default. Regards, Hiram On Wed, Sep 23, 2009 at 9:30 AM, Rob Davies wrote: > Raised an issue for it - > https:/

Re: [RESULT][VOTE] ActiveMQ Protocol Buffers 1.0 RC3

yay! Thanks doing the release! On Wed, Sep 23, 2009 at 7:32 AM, Dejan Bosanac wrote: > Hi, > > vote passed with the following result : > > +1: 8 votes > -1: 0 votes > 0: 0 votes > > I will promote the artifacts to the central repo. Thanks all for helping > with this release. > > Cheers > --

Re: producerFlowControl

Raised an issue for it - https://issues.apache.org/activemq/browse/AMQ-2403 On 23 Sep 2009, at 14:06, Bruce Snyder wrote: On Wed, Sep 23, 2009 at 6:46 AM, Rob Davies wrote: Any objections if this set back to true by default for destinations ? Now the bug in the memory limit has been resolve

[jira] Created: (AMQ-2403) Enable producer flow control again

Enable producer flow control again -- Key: AMQ-2403 URL: https://issues.apache.org/activemq/browse/AMQ-2403 Project: ActiveMQ Issue Type: Improvement Affects Versions: 5.3.0 Reporter: Rob Davie

[jira] Updated: (AMQ-2403) Enable producer flow control again

[ https://issues.apache.org/activemq/browse/AMQ-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies updated AMQ-2403: Description: There was a problem with memory limits not being set correctly for cursors with cacheEnabled

Re: producerFlowControl

hopefully - depends what we decide - 5.3 still not released. Flow control is enabled by default in 5.2 - we disabled it in trunk - but now I'm suggesting we revert back to having it enabled in trunk and hopefully 5.3 too On 23 Sep 2009, at 14:06, Bruce Snyder wrote: On Wed, Sep 23, 2009 at 6

Re: producerFlowControl

On Wed, Sep 23, 2009 at 6:46 AM, Rob Davies wrote: > > Any objections if this set back to true by default for destinations ? > Now the bug in the memory limit has been resolved for persistent cursors - > it would be generally safer to have this enabled again. Would this take place in 5.3? Bruce

Re: producerFlowControl

+1 Cheers -- Dejan Bosanac Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Wed, Sep 23, 2009 at 2:46 PM, Rob Davies wrote: > > Any objections if this set back to true by default for destinations ? > Now th

producerFlowControl

Any objections if this set back to true by default for destinations ? Now the bug in the memory limit has been resolved for persistent cursors - it would be generally safer to have this enabled again. cheers, Rob Rob Davies http://twitter.com/rajdavies I work here: http://fusesource.com My

[ANNOUNCE] AciveMQ Protocol Buffers 1.0 Released

Hi, You can find artifacts in the following repo https://repository.apache.org/content/repositories/releases/org/apache/activemq/protobuf/ (hopefully they will be in the central repo soon) Source release can be found here https://repository.apache.org/content/repositories/releases/org/apache/a

[RESULT][VOTE] ActiveMQ Protocol Buffers 1.0 RC3

Hi, vote passed with the following result : +1: 8 votes -1: 0 votes 0: 0 votes I will promote the artifacts to the central repo. Thanks all for helping with this release. Cheers -- Dejan Bosanac Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/sny

Re: Horizontally scaling JMS listener/consumer application.....in Active MQ environment

Both queues and topics can have multiple consumers, however the purpose of a topic is so that each consumer gets a copy of the message, while the purpose of a queue is that each message is only delivered to one consumer. Gabe -Original Message- From: "G1" Sent: Wednesday, September 23,

Re: Horizontally scaling JMS listener/consumer application.....in Active MQ environment

Hi msmyers, Are you referring to that I use Queue for the producer appl, Instead of Appl-P publishing to a VirtualTopic.Appl-P.SomeName, are you suggesting that it send to a Queue? But then, how can I have multiple subscriber's @ the listnener end (i want to horizontally scale the consumer App