[jira] [Commented] (AMQ-3131) Failed to reset batching ... java.lang.IllegalStateException: PageFile is not loaded

[ https://issues.apache.org/jira/browse/AMQ-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187960#comment-13187960 ] Gary Tully commented on AMQ-3131: - Glad you got sorted :-) On Jan 17, 2012 7:51 p.m., "Arthu

[jira] [Commented] (AMQ-3131) Failed to reset batching ... java.lang.IllegalStateException: PageFile is not loaded

[ https://issues.apache.org/jira/browse/AMQ-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187945#comment-13187945 ] Arthur Naseef commented on AMQ-3131: SCRATCH THAT. I had build problems that prevented

[jira] [Commented] (AMQ-3666) Javascript AMQ Connector XML response truncated in Firefox

[ https://issues.apache.org/jira/browse/AMQ-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187818#comment-13187818 ] Neznayenko Anton commented on AMQ-3666: --- btw, found another solution, but it needs act

[jira] [Commented] (AMQ-3666) Javascript AMQ Connector XML response truncated in Firefox

[ https://issues.apache.org/jira/browse/AMQ-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187809#comment-13187809 ] Neznayenko Anton commented on AMQ-3666: --- Oh, I thought I'm the only one who is affecte

[jira] [Commented] (AMQ-3666) Javascript AMQ Connector XML response truncated in Firefox

[ https://issues.apache.org/jira/browse/AMQ-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187803#comment-13187803 ] Claudio Squarcella commented on AMQ-3666: - hi, I [reported the same|https://issues

[jira] [Updated] (AMQ-3666) Javascript AMQ Connector XML response truncated in Firefox

[ https://issues.apache.org/jira/browse/AMQ-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neznayenko Anton updated AMQ-3666: -- Attachment: amq.js.patch > Javascript AMQ Connector XML response truncated in Firefox > -

[jira] [Created] (AMQ-3666) Javascript AMQ Connector XML response truncated in Firefox

Javascript AMQ Connector XML response truncated in Firefox -- Key: AMQ-3666 URL: https://issues.apache.org/jira/browse/AMQ-3666 Project: ActiveMQ Issue Type: Bug Reporter: N

[jira] [Commented] (AMQ-3653) content-length header should be considered only for SEND frames

[ https://issues.apache.org/jira/browse/AMQ-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187776#comment-13187776 ] Timothy Bish commented on AMQ-3653: --- Added a small fix for the test. > co

[jira] [Commented] (AMQ-3664) Not all messages will be acknowledged when optimizeAcknowledge is true

[ https://issues.apache.org/jira/browse/AMQ-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187771#comment-13187771 ] Gary Tully commented on AMQ-3664: - I suspect you need to explicitly set a cache level (use c

[jira] [Updated] (AMQ-3665) Velocity's IntroSpectionCache causes OutOfMemoryError on large AMQ stores when running activem-admin journal-audit

[ https://issues.apache.org/jira/browse/AMQ-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-3665: Description: activemq-admin journal-audit can be used to dump the content of the AMQ store to system

[jira] [Commented] (AMQ-3665) Velocity's IntroSpectionCache causes OutOfMemoryError on large AMQ stores when running activem-admin journal-audit

[ https://issues.apache.org/jira/browse/AMQ-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187718#comment-13187718 ] Torsten Mielke commented on AMQ-3665: - The quote from Velocity Developers Guide above su

[jira] [Created] (AMQ-3665) Velocity's IntroSpectionCache causes OutOfMemoryError on large AMQ stores when running activem-admin journal-audit

Velocity's IntroSpectionCache causes OutOfMemoryError on large AMQ stores when running activem-admin journal-audit -- Key: AMQ-3665 URL: https://issues

[jira] [Commented] (AMQNET-358) Why do ActiveMQ Consumers Recover to Pull Mode instead of Prefetch

[ https://issues.apache.org/jira/browse/AMQNET-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187657#comment-13187657 ] Jonathan Parker McClure commented on AMQNET-358: Sorry for the belated res

[jira] [Updated] (AMQ-3664) Not all messages will be acknowledged when optimizeAcknowledge is true

[ https://issues.apache.org/jira/browse/AMQ-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Wessel updated AMQ-3664: - Summary: Not all messages will be acknowledged when optimizeAcknowledge is true (was: Not all mess

[jira] [Updated] (AMQ-3664) Not all messages will be consumed when optimizeAcknowledge is true

[ https://issues.apache.org/jira/browse/AMQ-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Wessel updated AMQ-3664: - Description: I make performance test with activemq. When I set optimizeAcknowledge = true I get a

[jira] [Updated] (AMQ-3664) Not all messages will be consumed when optimizeAcknowledge is true

[ https://issues.apache.org/jira/browse/AMQ-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Wessel updated AMQ-3664: - Component/s: Broker Description: I make performance test with activemq. When I set

[jira] [Created] (AMQ-3664) Not all messages will be consumed when optimizeAcknowledge is true

Not all messages will be consumed when optimizeAcknowledge is true -- Key: AMQ-3664 URL: https://issues.apache.org/jira/browse/AMQ-3664 Project: ActiveMQ Issue Type: Bug

[jira] [Commented] (AMQ-1853) Optional non-blocking redelivery

[ https://issues.apache.org/jira/browse/AMQ-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187547#comment-13187547 ] Per Steffensen commented on AMQ-1853: - It is nice that there will finally be done someth

Jenkins build is still unstable: ActiveMQ #858

See