[jira] Commented: (AMQ-1786) Journal files don't get cleaned up

[ https://issues.apache.org/activemq/browse/AMQ-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=52254#action_52254 ] Gary Tully commented on AMQ-1786: - Sudip, have you tried a 5.3-SNAPSHOT? Could you possibly

Re: ActiveMQ 6.0 Broker Core Prototype -- Flow Control / Memory Management

On the 'temporary blocking', we need to think of ways to place maximums on these blocks. A 5.x trait is that flushing buffers to disk on reaching a memory limit is a single op, so a producer or consumer could be blocked for N writes (where N can be quite large) The flow model can be more linear

[jira] Created: (AMQCPP-247) Exception thrown while using failover and Transacted sessions.

Exception thrown while using failover and Transacted sessions. -- Key: AMQCPP-247 URL: https://issues.apache.org/activemq/browse/AMQCPP-247 Project: ActiveMQ C++ Client Issue Type:

[jira] Created: (AMQ-2288) AdvisoryBroker does not set up SecurityContext so advisory message not sent on startup

AdvisoryBroker does not set up SecurityContext so advisory message not sent on startup -- Key: AMQ-2288 URL: https://issues.apache.org/activemq/browse/AMQ-2288

[jira] Created: (AMQ-2289) Browsing Queue through JMX has unintended side effects for producer flow control

Browsing Queue through JMX has unintended side effects for producer flow control Key: AMQ-2289 URL: https://issues.apache.org/activemq/browse/AMQ-2289 Project: ActiveMQ

NMS 1.1.0 RC1 Available

* ANNOUNCEMENT * The Apache NMS 1.1.0 Release Candidate 1 is now available at the following location: http://people.apache.org/~jgomes/nms_1.1.0 The following projects are included: Apache.NMS Apache.NMS.ActiveMQ Apache.NMS.EMS Apache.NMS.MSMQ Apache.NMS.WCF

Re: NMS 1.1.0 RC1 Available

Just to clarify, this isn't a call for a vote yet. Just merely an announcement for preview. A vote will be called shortly. On Mon, Jun 15, 2009 at 7:15 AM, Jim Gomes e.se...@gmail.com wrote: * ANNOUNCEMENT * The Apache NMS 1.1.0 Release Candidate 1 is now

Re: NMS 1.1.0 RC1 Available

On Mon, 2009-06-15 at 07:15 -0700, Jim Gomes wrote: * ANNOUNCEMENT * The Apache NMS 1.1.0 Release Candidate 1 is now available at the following location: http://people.apache.org/~jgomes/nms_1.1.0 The following projects are included: Apache.NMS Apache.NMS.ActiveMQ

[jira] Resolved: (AMQCPP-247) Exception thrown while using failover and Transacted sessions.

[ https://issues.apache.org/activemq/browse/AMQCPP-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQCPP-247. - Resolution: Fixed Fixed in Trunk Exception thrown while using failover and Transacted

[jira] Created: (AMQ-2290) Memory leak in SelectorParser LRUCache

Memory leak in SelectorParser LRUCache -- Key: AMQ-2290 URL: https://issues.apache.org/activemq/browse/AMQ-2290 Project: ActiveMQ Issue Type: Bug Components: Selector Affects Versions: 5.3.0

[jira] Updated: (AMQ-2290) Memory leak in SelectorParser LRUCache

[ https://issues.apache.org/activemq/browse/AMQ-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Sarva updated AMQ-2290: -- Attachment: selectorparser-leak.png Attached is a screenshot from our heap dump analysis showing the

[jira] Commented: (AMQ-2139) Batch up multiple socket write calls in the TCP transport.

[ https://issues.apache.org/activemq/browse/AMQ-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=52264#action_52264 ] MARCHAL commented on AMQ-2139: -- Hi I'm working on servicemix 3 and I had some problems with load

[jira] Commented: (AMQ-2290) Memory leak in SelectorParser LRUCache

[ https://issues.apache.org/activemq/browse/AMQ-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=52265#action_52265 ] Gary Tully commented on AMQ-2290: - does the 80 in that screenshot indicate the number of

[jira] Created: (AMQ-2291) Messages with an ID (2^31 - 1) are not persisted to long term storage

Messages with an ID (2^31 - 1) are not persisted to long term storage --- Key: AMQ-2291 URL: https://issues.apache.org/activemq/browse/AMQ-2291 Project: ActiveMQ Issue

[jira] Resolved: (AMQ-2291) Messages with an ID (2^31 - 1) are not persisted to long term storage

[ https://issues.apache.org/activemq/browse/AMQ-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-2291. Resolution: Fixed fixed in svn revision 784862 Messages with an ID (2^31 - 1) are not

[jira] Commented: (AMQ-2290) Memory leak in SelectorParser LRUCache

[ https://issues.apache.org/activemq/browse/AMQ-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=52268#action_52268 ] Chetan Sarva commented on AMQ-2290: --- Sorry, I should have captured the column headers as

[jira] Updated: (AMQ-1786) Journal files don't get cleaned up

[ https://issues.apache.org/activemq/browse/AMQ-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudip Pulapura updated AMQ-1786: Attachment: PersistentStorageCleanup.java The class takes the persistent directory as an

[jira] Updated: (AMQ-2292) NullPointerException in ReadOnlyAsyncDataManager as accessorPool is not initialized

[ https://issues.apache.org/activemq/browse/AMQ-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Stanley updated AMQ-2292: -- Attachment: readonly_async_data_mgr_patch.txt Patch attached. NullPointerException in

[jira] Created: (AMQ-2292) NullPointerException in ReadOnlyAsyncDataManager as accessorPool is not initialized

NullPointerException in ReadOnlyAsyncDataManager as accessorPool is not initialized Key: AMQ-2292 URL: https://issues.apache.org/activemq/browse/AMQ-2292 Project:

RE: ActiveMQ 6.0 Broker Core Prototype -- Flow Control / Memory Management

Hi Gary, Putting maximums on these blocks may not be possible in cases where we are not willing to discard messages on a queue. Ultimately the publisher rate is tied to the disk sync rate. I think the best we can do in this case is to try to smooth out the publisher's profile. The point of the

RE: NMS 1.1.0 RC1 Available

at the log4net project and it looks like there they just package everything into one file. See: http://logging.apache.org/log4net/download.html Regards Tim. __ Information from ESET NOD32 Antivirus, version of virus signature database 4155 (20090615) __ The message was checked

RE: NMS 1.1.0 RC1 Available

from ESET NOD32 Antivirus, version of virus signature database 4155 (20090615) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __ Information from ESET NOD32 Antivirus, version of virus signature database 4156 (20090615) __ The message