[jira] [Updated] (AMQ-5692) Inactivity monitor does not time out on stuck socket writes

[ https://issues.apache.org/jira/browse/AMQ-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-5692: Attachment: AMQ-5692.pl Inactivity monitor does not time out on stuck socket writes

[jira] [Commented] (AMQ-5692) Inactivity monitor does not time out on stuck socket writes

[ https://issues.apache.org/jira/browse/AMQ-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14483067#comment-14483067 ] Torsten Mielke commented on AMQ-5692: - Attached reproducer in AMQ-5692.pl. To reproduce

[jira] [Created] (AMQ-5692) Inactivity monitor does not time out on stuck socket writes

Torsten Mielke created AMQ-5692: --- Summary: Inactivity monitor does not time out on stuck socket writes Key: AMQ-5692 URL: https://issues.apache.org/jira/browse/AMQ-5692 Project: ActiveMQ

[jira] [Commented] (AMQ-5692) Inactivity monitor does not time out on stuck socket writes

[ https://issues.apache.org/jira/browse/AMQ-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383802#comment-14383802 ] Torsten Mielke commented on AMQ-5692: - A workaround currently is to configure

[jira] [Commented] (AMQ-5683) [doc] No documentation of transport.soWriteTimeout

[ https://issues.apache.org/jira/browse/AMQ-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376132#comment-14376132 ] Torsten Mielke commented on AMQ-5683: - Resolved in [version

[jira] [Created] (AMQ-5683) [doc] No documentation of transport.soWriteTimeout

Torsten Mielke created AMQ-5683: --- Summary: [doc] No documentation of transport.soWriteTimeout Key: AMQ-5683 URL: https://issues.apache.org/jira/browse/AMQ-5683 Project: ActiveMQ Issue Type:

[jira] [Resolved] (AMQ-5683) [doc] No documentation of transport.soWriteTimeout

[ https://issues.apache.org/jira/browse/AMQ-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke resolved AMQ-5683. - Resolution: Fixed Fix Version/s: 5.11.1 [doc] No documentation of transport.soWriteTimeout

[jira] [Created] (AMQ-5668) NPE in kahadb with concurrentStoreAndDispatchTopics when sending MQTT msgs with different QoS

Torsten Mielke created AMQ-5668: --- Summary: NPE in kahadb with concurrentStoreAndDispatchTopics when sending MQTT msgs with different QoS Key: AMQ-5668 URL: https://issues.apache.org/jira/browse/AMQ-5668

[jira] [Commented] (AMQ-5668) NPE in kahadb with concurrentStoreAndDispatchTopics when sending MQTT msgs with different QoS

[ https://issues.apache.org/jira/browse/AMQ-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365057#comment-14365057 ] Torsten Mielke commented on AMQ-5668: - Possible workarounds: -

[jira] [Updated] (AMQ-5640) negative TotalMessageCount in JMX Broker MBean

[ https://issues.apache.org/jira/browse/AMQ-5640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-5640: Attachment: TotalMessageCountTest.java negative TotalMessageCount in JMX Broker MBean

[jira] [Comment Edited] (AMQ-5640) negative TotalMessageCount in JMX Broker MBean

[ https://issues.apache.org/jira/browse/AMQ-5640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348715#comment-14348715 ] Torsten Mielke edited comment on AMQ-5640 at 3/5/15 2:21 PM: -

[jira] [Created] (AMQ-5640) negative TotalMessageCount in JMX Broker MBean

Torsten Mielke created AMQ-5640: --- Summary: negative TotalMessageCount in JMX Broker MBean Key: AMQ-5640 URL: https://issues.apache.org/jira/browse/AMQ-5640 Project: ActiveMQ Issue Type:

[jira] [Commented] (AMQ-5640) negative TotalMessageCount in JMX Broker MBean

[ https://issues.apache.org/jira/browse/AMQ-5640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348715#comment-14348715 ] Torsten Mielke commented on AMQ-5640: - Unit test to follow. negative

[jira] [Commented] (AMQ-4366) PooledConnectionFactory closes connections that are in use

[ https://issues.apache.org/jira/browse/AMQ-4366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14343384#comment-14343384 ] Torsten Mielke commented on AMQ-4366: - Yes, 5.10 will include the fix for this bug.

[jira] [Commented] (AMQ-4705) Add keep alive support to shared file locker

[ https://issues.apache.org/jira/browse/AMQ-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14309094#comment-14309094 ] Torsten Mielke commented on AMQ-4705: - Kind of follow up problem: AMQ-5568 Add keep

[jira] [Created] (AMQ-5568) deleting lock file on broker shut down can take a master broker down

Torsten Mielke created AMQ-5568: --- Summary: deleting lock file on broker shut down can take a master broker down Key: AMQ-5568 URL: https://issues.apache.org/jira/browse/AMQ-5568 Project: ActiveMQ

[jira] [Commented] (AMQ-5568) Deleting lock file on broker shut down can take a master broker down

[ https://issues.apache.org/jira/browse/AMQ-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14309106#comment-14309106 ] Torsten Mielke commented on AMQ-5568: - It seems the broker simply deletes the lock file

[jira] [Updated] (AMQ-5568) deleting lock file on broker shut down can take a master broker down

[ https://issues.apache.org/jira/browse/AMQ-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-5568: Description: This problem may only occur on a shared file system master/slave setup. I can reproduce

[jira] [Commented] (AMQ-5549) Shared Filesystem Master/Slave using NFSv4 allows both brokers become active at the same time

[ https://issues.apache.org/jira/browse/AMQ-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14309119#comment-14309119 ] Torsten Mielke commented on AMQ-5549: - Also see AMQ-5568. Shared Filesystem

[jira] [Comment Edited] (AMQ-5568) deleting lock file on broker shut down can take a master broker down

[ https://issues.apache.org/jira/browse/AMQ-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14309092#comment-14309092 ] Torsten Mielke edited comment on AMQ-5568 at 2/6/15 1:05 PM: -

[jira] [Commented] (AMQ-5568) deleting lock file on broker shut down can take a master broker down

[ https://issues.apache.org/jira/browse/AMQ-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14309092#comment-14309092 ] Torsten Mielke commented on AMQ-5568: - The keepAlive ping is needed due to

[jira] [Updated] (AMQ-5568) Deleting lock file on broker shut down can take a master broker down

[ https://issues.apache.org/jira/browse/AMQ-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-5568: Summary: Deleting lock file on broker shut down can take a master broker down (was: deleting lock

[jira] [Commented] (AMQ-5549) Shared Filesystem Master/Slave using NFSv4 allows both brokers become active at the same time

[ https://issues.apache.org/jira/browse/AMQ-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14298738#comment-14298738 ] Torsten Mielke commented on AMQ-5549: - {quote} Maybe I wasn't clear enough in the

[jira] [Comment Edited] (AMQ-5549) Shared Filesystem Master/Slave using NFSv4 allows both brokers become active at the same time

[ https://issues.apache.org/jira/browse/AMQ-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14298361#comment-14298361 ] Torsten Mielke edited comment on AMQ-5549 at 1/30/15 8:29 AM: --

[jira] [Commented] (AMQ-5549) Shared Filesystem Master/Slave using NFSv4 allows both brokers become active at the same time

[ https://issues.apache.org/jira/browse/AMQ-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14298361#comment-14298361 ] Torsten Mielke commented on AMQ-5549: - Some of the NFS mount options may not support a

[jira] [Comment Edited] (AMQ-5549) Shared Filesystem Master/Slave using NFSv4 allows both brokers become active at the same time

[ https://issues.apache.org/jira/browse/AMQ-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14298361#comment-14298361 ] Torsten Mielke edited comment on AMQ-5549 at 1/30/15 8:28 AM: --

[jira] [Commented] (AMQ-5549) Shared Filesystem Master/Slave using NFSv4 allows both brokers become active at the same time

[ https://issues.apache.org/jira/browse/AMQ-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14298603#comment-14298603 ] Torsten Mielke commented on AMQ-5549: - I am not suggesting ActiveMQ requires a soft NFS

[jira] [Updated] (AMQ-4495) Improve cursor memory management

[ https://issues.apache.org/jira/browse/AMQ-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-4495: Summary: Improve cursor memory management (was: Imporve cursor memory management) Improve cursor

[jira] [Commented] (AMQ-5549) Shared Filesystem Master/Slave using NFSv4 allows both brokers become active at the same time

[ https://issues.apache.org/jira/browse/AMQ-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296863#comment-14296863 ] Torsten Mielke commented on AMQ-5549: - Hi, the config {code:xml} kahaDB

[jira] [Comment Edited] (AMQ-5549) Shared Filesystem Master/Slave using NFSv4 allows both brokers become active at the same time

[ https://issues.apache.org/jira/browse/AMQ-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296863#comment-14296863 ] Torsten Mielke edited comment on AMQ-5549 at 1/29/15 2:42 PM: --

[jira] [Commented] (ACTIVEMQ6-36) Disallow use of SSLv3 to protect against POODLE

[ https://issues.apache.org/jira/browse/ACTIVEMQ6-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14234311#comment-14234311 ] Torsten Mielke commented on ACTIVEMQ6-36: - Using this configuration should

[jira] [Commented] (AMQ-5399) MQTT - out of order acks

[ https://issues.apache.org/jira/browse/AMQ-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176941#comment-14176941 ] Torsten Mielke commented on AMQ-5399: - I can confirm the bug is fixed on latest

[jira] [Comment Edited] (AMQ-5274) Stuck messages and CPU churn when aborted transacted message expires

[ https://issues.apache.org/jira/browse/AMQ-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14112193#comment-14112193 ] Torsten Mielke edited comment on AMQ-5274 at 8/27/14 12:23 PM: ---

[jira] [Updated] (AMQ-5274) Stuck messages and CPU churn when aborted transacted message expires

[ https://issues.apache.org/jira/browse/AMQ-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-5274: Attachment: AMQ-5274v2.zip Uploading a modified version of AMQ-5274.zip that runs a JUnit test.

[jira] [Updated] (AMQ-5274) Stuck messages and CPU churn when aborted transacted message expires

[ https://issues.apache.org/jira/browse/AMQ-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-5274: Attachment: AMQ-5274v2.zip Stuck messages and CPU churn when aborted transacted message expires

[jira] [Commented] (AMQ-5304) groupClass not applied to TempDestinationAuthorizationEntry

[ https://issues.apache.org/jira/browse/AMQ-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093858#comment-14093858 ] Torsten Mielke commented on AMQ-5304: - Fixed in commit

[jira] [Resolved] (AMQ-5304) groupClass not applied to TempDestinationAuthorizationEntry

[ https://issues.apache.org/jira/browse/AMQ-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke resolved AMQ-5304. - Resolution: Fixed Fix Version/s: 5.11.0 groupClass not applied to

[jira] [Commented] (AMQ-5307) MQTT Transport codec does not properly deal with partial read of frame header

[ https://issues.apache.org/jira/browse/AMQ-5307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14085941#comment-14085941 ] Torsten Mielke commented on AMQ-5307: - I can confirm the problem is resolved using the

[jira] [Commented] (AMQ-5307) MQTT Transport codec does not properly deal with partial read of frame header

[ https://issues.apache.org/jira/browse/AMQ-5307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14084765#comment-14084765 ] Torsten Mielke commented on AMQ-5307: - Seems to be related to

[jira] [Created] (AMQ-5304) groupClass not applied to TempDestinationAuthorizationEntry

Torsten Mielke created AMQ-5304: --- Summary: groupClass not applied to TempDestinationAuthorizationEntry Key: AMQ-5304 URL: https://issues.apache.org/jira/browse/AMQ-5304 Project: ActiveMQ

[jira] [Commented] (AMQ-5304) groupClass not applied to TempDestinationAuthorizationEntry

[ https://issues.apache.org/jira/browse/AMQ-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14082191#comment-14082191 ] Torsten Mielke commented on AMQ-5304: - I have a unit test but its based on Pax-Exam and

[jira] [Updated] (AMQ-5304) groupClass not applied to TempDestinationAuthorizationEntry

[ https://issues.apache.org/jira/browse/AMQ-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-5304: Description: When configuring the authorization plugin with a tempDestinationAuthorizationEntry

[jira] [Updated] (AMQ-5304) groupClass not applied to TempDestinationAuthorizationEntry

[ https://issues.apache.org/jira/browse/AMQ-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-5304: Attachment: AMQ-5304.patch Attaching a possible fix for this bug in AMQ-5304.patch. Will still try

[jira] [Issue Comment Deleted] (AMQ-5304) groupClass not applied to TempDestinationAuthorizationEntry

[ https://issues.apache.org/jira/browse/AMQ-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-5304: Comment: was deleted (was: A comment with security level 'activemq-developers' was removed.)

[jira] [Created] (AMQ-5141) Message expiry that is done as part of a removeSubscription command should not use the clients credentials.

Torsten Mielke created AMQ-5141: --- Summary: Message expiry that is done as part of a removeSubscription command should not use the clients credentials. Key: AMQ-5141 URL:

[jira] [Commented] (AMQ-5141) Message expiry that is done as part of a removeSubscription command should not use the clients credentials.

[ https://issues.apache.org/jira/browse/AMQ-5141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13966427#comment-13966427 ] Torsten Mielke commented on AMQ-5141: - Don't have a Unit test at hand but could build

[jira] [Commented] (AMQ-5141) Message expiry that is done as part of a removeSubscription command should not use the clients credentials.

[ https://issues.apache.org/jira/browse/AMQ-5141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13966450#comment-13966450 ] Torsten Mielke commented on AMQ-5141: - Here are two possible workarounds: 1) The quick

[jira] [Comment Edited] (AMQ-5141) Message expiry that is done as part of a removeSubscription command should not use the clients credentials.

[ https://issues.apache.org/jira/browse/AMQ-5141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13966450#comment-13966450 ] Torsten Mielke edited comment on AMQ-5141 at 4/11/14 12:13 PM: ---

[jira] [Resolved] (AMQ-4950) java.lang.ClassCastException: org.apache.activemq.command.ExceptionResponse cannot be cast to org.apache.activemq.command.IntegerResponse, attempting to automatically re

[ https://issues.apache.org/jira/browse/AMQ-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke resolved AMQ-4950. - Resolution: Fixed Fix Version/s: 5.10.0 Fixed in commit

[jira] [Comment Edited] (AMQ-4950) java.lang.ClassCastException: org.apache.activemq.command.ExceptionResponse cannot be cast to org.apache.activemq.command.IntegerResponse, attempting to automatica

[ https://issues.apache.org/jira/browse/AMQ-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862984#comment-13862984 ] Torsten Mielke edited comment on AMQ-4950 at 1/6/14 1:27 PM: -

[jira] [Issue Comment Deleted] (AMQ-4950) java.lang.ClassCastException: org.apache.activemq.command.ExceptionResponse cannot be cast to org.apache.activemq.command.IntegerResponse, attempting to aut

[ https://issues.apache.org/jira/browse/AMQ-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-4950: Comment: was deleted (was: I have a unit test and possible patch already but want to test it

[jira] [Commented] (AMQ-4950) java.lang.ClassCastException: org.apache.activemq.command.ExceptionResponse cannot be cast to org.apache.activemq.command.IntegerResponse, attempting to automatically r

[ https://issues.apache.org/jira/browse/AMQ-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13855282#comment-13855282 ] Torsten Mielke commented on AMQ-4950: - I have a unit test and possible patch already but

[jira] [Created] (AMQ-4950) java.lang.ClassCastException: org.apache.activemq.command.ExceptionResponse cannot be cast to org.apache.activemq.command.IntegerResponse, attempting to automatically rec

Torsten Mielke created AMQ-4950: --- Summary: java.lang.ClassCastException: org.apache.activemq.command.ExceptionResponse cannot be cast to org.apache.activemq.command.IntegerResponse, attempting to automatically reconnect Key:

[jira] [Commented] (AMQ-4950) java.lang.ClassCastException: org.apache.activemq.command.ExceptionResponse cannot be cast to org.apache.activemq.command.IntegerResponse, attempting to automatically r

[ https://issues.apache.org/jira/browse/AMQ-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13853933#comment-13853933 ] Torsten Mielke commented on AMQ-4950: - Full error message: {noformat} 2013-12-20

[jira] [Commented] (AMQ-4465) Rethink replayWhenNoConsumers solution

[ https://issues.apache.org/jira/browse/AMQ-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851921#comment-13851921 ] Torsten Mielke commented on AMQ-4465: - Agreed Gary. I will mark this bug as resolved.

[jira] [Resolved] (AMQ-4465) Rethink replayWhenNoConsumers solution

[ https://issues.apache.org/jira/browse/AMQ-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke resolved AMQ-4465. - Resolution: Fixed Fix Version/s: 5.9.0 This should be fixed by the changes in AMQ-4607.

[jira] [Commented] (AMQ-4595) QueueBrowser hangs when browsing large queues

[ https://issues.apache.org/jira/browse/AMQ-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731719#comment-13731719 ] Torsten Mielke commented on AMQ-4595: - @Nicholas - Thx for the update. Will do.

[jira] [Commented] (AMQ-4595) QueueBrowser hangs when browsing large queues

[ https://issues.apache.org/jira/browse/AMQ-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13706779#comment-13706779 ] Torsten Mielke commented on AMQ-4595: - Hi Tim, Do you mind explaining a bit more why

[jira] [Resolved] (AMQ-4571) Improve DestinationFilter to allow any filter to unsubscribe its wrapped destination from a durable subscruption

[ https://issues.apache.org/jira/browse/AMQ-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke resolved AMQ-4571. - Resolution: Fixed Improve DestinationFilter to allow any filter to unsubscribe its wrapped

[jira] [Commented] (AMQ-4571) Improve DestinationFilter to allow any filter to unsubscribe its wrapped destination from a durable subscruption

[ https://issues.apache.org/jira/browse/AMQ-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13675835#comment-13675835 ] Torsten Mielke commented on AMQ-4571: - Unit test for this fix added in

[jira] [Commented] (AMQ-4356) unsubcribes DurableSuscriber does not work well with Virtual Topics

[ https://issues.apache.org/jira/browse/AMQ-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13675843#comment-13675843 ] Torsten Mielke commented on AMQ-4356: - This fix is superseded by AMQ-4571.

[jira] [Commented] (AMQ-4567) JMX operations on broker bypass authorization plugin

[ https://issues.apache.org/jira/browse/AMQ-4567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13673192#comment-13673192 ] Torsten Mielke commented on AMQ-4567: - Hi Christian, Yes, I think we should enhance it.

[jira] [Commented] (AMQ-4565) Cannot unsubscribe from virtual topics

[ https://issues.apache.org/jira/browse/AMQ-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13673204#comment-13673204 ] Torsten Mielke commented on AMQ-4565: - Is this problem related to or even the same as

[jira] [Created] (AMQ-4562) SimplePriorityMessageDispatchChannel.clear() needs to reset size attribute

Torsten Mielke created AMQ-4562: --- Summary: SimplePriorityMessageDispatchChannel.clear() needs to reset size attribute Key: AMQ-4562 URL: https://issues.apache.org/jira/browse/AMQ-4562 Project: ActiveMQ

[jira] [Commented] (AMQ-4562) SimplePriorityMessageDispatchChannel.clear() needs to reset size attribute

[ https://issues.apache.org/jira/browse/AMQ-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670159#comment-13670159 ] Torsten Mielke commented on AMQ-4562: - I hope this fix is obvious as I am not sure yet

[jira] [Commented] (AMQ-4480) mkahadb with perDestination=true lazily loads kahadb journal files after startup

[ https://issues.apache.org/jira/browse/AMQ-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13637941#comment-13637941 ] Torsten Mielke commented on AMQ-4480: - Will try to work out a JUnit test later.

[jira] [Created] (AMQ-4480) mkahadb with perDestination=true lazily loads kahadb journal files after startup

Torsten Mielke created AMQ-4480: --- Summary: mkahadb with perDestination=true lazily loads kahadb journal files after startup Key: AMQ-4480 URL: https://issues.apache.org/jira/browse/AMQ-4480 Project:

[jira] [Updated] (AMQ-4480) mkahadb with perDestination=true lazily loads kahadb journal files after startup

[ https://issues.apache.org/jira/browse/AMQ-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-4480: Affects Version/s: 5.8.0 mkahadb with perDestination=true lazily loads kahadb journal files

[jira] [Commented] (AMQ-4480) mkahadb with perDestination=true lazily loads kahadb journal files after startup

[ https://issues.apache.org/jira/browse/AMQ-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13637999#comment-13637999 ] Torsten Mielke commented on AMQ-4480: - This seems to be caused by the default file and

[jira] [Comment Edited] (AMQ-4480) mkahadb with perDestination=true lazily loads kahadb journal files after startup

[ https://issues.apache.org/jira/browse/AMQ-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13637999#comment-13637999 ] Torsten Mielke edited comment on AMQ-4480 at 4/22/13 1:44 PM: --

[jira] [Created] (AMQ-4465) Rethink replayWhenNoConsumers solution

Torsten Mielke created AMQ-4465: --- Summary: Rethink replayWhenNoConsumers solution Key: AMQ-4465 URL: https://issues.apache.org/jira/browse/AMQ-4465 Project: ActiveMQ Issue Type: Improvement

[jira] [Commented] (AMQ-4366) PooledConnectionFactory closes connections that are in use

[ https://issues.apache.org/jira/browse/AMQ-4366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13626330#comment-13626330 ] Torsten Mielke commented on AMQ-4366: - I am not aware of any side effects when applying

[jira] [Commented] (AMQ-4366) PooledConnectionFactory closes connections that are in use

[ https://issues.apache.org/jira/browse/AMQ-4366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619630#comment-13619630 ] Torsten Mielke commented on AMQ-4366: - A proper workaround for any 5.7 and 5.8 versioned

[jira] [Commented] (AMQ-4212) Broker may be unable to recover durable topic subscription from the kahadb journal

[ https://issues.apache.org/jira/browse/AMQ-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13556387#comment-13556387 ] Torsten Mielke commented on AMQ-4212: - @Tim, don't have a unit test yet but presumably

[jira] [Created] (AMQ-4212) Broker may be unable to recover durable topic subscription from the kahadb journal

Torsten Mielke created AMQ-4212: --- Summary: Broker may be unable to recover durable topic subscription from the kahadb journal Key: AMQ-4212 URL: https://issues.apache.org/jira/browse/AMQ-4212 Project:

[jira] [Commented] (AMQ-4000) Durable subscription not getting unregistered on networked broker

[ https://issues.apache.org/jira/browse/AMQ-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13444017#comment-13444017 ] Torsten Mielke commented on AMQ-4000: - org.apache.activemq.advisory.AdvisoryBroker does

[jira] [Created] (AMQ-4000) Durable subscription not getting unregistered on networked broker

Torsten Mielke created AMQ-4000: --- Summary: Durable subscription not getting unregistered on networked broker Key: AMQ-4000 URL: https://issues.apache.org/jira/browse/AMQ-4000 Project: ActiveMQ

[jira] [Updated] (AMQ-4000) Durable subscription not getting unregistered on networked broker

[ https://issues.apache.org/jira/browse/AMQ-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-4000: Attachment: JUnitTest.patch Attaching patch file containing JUnit test but no fix yet.

[jira] [Assigned] (AMQ-3965) Expired msgs not getting acked to broker causing consumer to fill up its prefetch and not getting more msgs.

[ https://issues.apache.org/jira/browse/AMQ-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke reassigned AMQ-3965: --- Assignee: Torsten Mielke Expired msgs not getting acked to broker causing consumer to

[jira] [Resolved] (AMQ-3965) Expired msgs not getting acked to broker causing consumer to fill up its prefetch and not getting more msgs.

[ https://issues.apache.org/jira/browse/AMQ-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke resolved AMQ-3965. - Resolution: Fixed Fix Version/s: 5.7.0 Resolved by this

[jira] [Updated] (AMQ-3965) Expired msgs not getting acked to broker causing consumer to fill up its prefetch and not getting more msgs.

[ https://issues.apache.org/jira/browse/AMQ-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-3965: Attachment: AMQ-3956.patch Attaching possible patch plus JUnit test. Would ask for review and if

[jira] [Commented] (AMQ-3965) Expired msgs not getting acked to broker causing consumer to fill up its prefetch and not getting more msgs.

[ https://issues.apache.org/jira/browse/AMQ-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13431945#comment-13431945 ] Torsten Mielke commented on AMQ-3965: - We thought that the following fix could do the

[jira] [Created] (AMQ-3965) Expired msgs not getting acked to broker causing consumer to fill up its prefetch and not getting more msgs.

Torsten Mielke created AMQ-3965: --- Summary: Expired msgs not getting acked to broker causing consumer to fill up its prefetch and not getting more msgs. Key: AMQ-3965 URL:

[jira] [Commented] (AMQ-3965) Expired msgs not getting acked to broker causing consumer to fill up its prefetch and not getting more msgs.

[ https://issues.apache.org/jira/browse/AMQ-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13431146#comment-13431146 ] Torsten Mielke commented on AMQ-3965: - A possible fix for this may be to no hold back

[jira] [Commented] (AMQ-3557) Performance of consumption with JDBC persistance and Microsoft SQL Server

[ https://issues.apache.org/jira/browse/AMQ-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13416048#comment-13416048 ] Torsten Mielke commented on AMQ-3557: - There was recently an improvement made to the

[jira] [Assigned] (AMQ-3904) InactivityMonitor doc

[ https://issues.apache.org/jira/browse/AMQ-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke reassigned AMQ-3904: --- Assignee: Torsten Mielke InactivityMonitor doc -

[jira] [Commented] (AMQ-3904) InactivityMonitor doc

[ https://issues.apache.org/jira/browse/AMQ-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13403942#comment-13403942 ] Torsten Mielke commented on AMQ-3904: - Many thanks to Pat Fox for providing this

[jira] [Resolved] (AMQ-3904) InactivityMonitor doc

[ https://issues.apache.org/jira/browse/AMQ-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke resolved AMQ-3904. - Resolution: Fixed https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+InactivityMonitor

[jira] [Updated] (AMQ-3506) Access to ConnectionPool.createSession needs to be synchronized

[ https://issues.apache.org/jira/browse/AMQ-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-3506: Attachment: AMQ-3506.patch Attaching possible fix and corresponding JUnit test Access to

[jira] [Commented] (AMQ-3503) Too many open files for db log

[ https://issues.apache.org/jira/browse/AMQ-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13106065#comment-13106065 ] Torsten Mielke commented on AMQ-3503: - You can get the latest snapshot version from

[jira] [Created] (AMQ-3492) enhance maven-activemq-perf-plugin to send specific message loaded from a file

enhance maven-activemq-perf-plugin to send specific message loaded from a file -- Key: AMQ-3492 URL: https://issues.apache.org/jira/browse/AMQ-3492 Project: ActiveMQ

[jira] [Updated] (AMQ-3492) enhance maven-activemq-perf-plugin to send specific message loaded from a file

[ https://issues.apache.org/jira/browse/AMQ-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-3492: Attachment: AMQ-3492.patch Attaching a patch based on 5.6-SNAPSHOT version. enhance

[jira] [Updated] (AMQ-3482) Make PooledConnectionFactory's sessionPool non-blocking in case its full.

[ https://issues.apache.org/jira/browse/AMQ-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-3482: Attachment: AMQ-3482.patch Attaching a possible patch including JUnit test. This patch allows to

[jira] [Created] (AMQ-3430) activemq-web: SessionPool.returnSession() should discard sessions that are closed.

activemq-web: SessionPool.returnSession() should discard sessions that are closed. --- Key: AMQ-3430 URL: https://issues.apache.org/jira/browse/AMQ-3430 Project:

[jira] [Commented] (AMQ-3430) activemq-web: SessionPool.returnSession() should discard sessions that are closed.

[ https://issues.apache.org/jira/browse/AMQ-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13073485#comment-13073485 ] Torsten Mielke commented on AMQ-3430: - full stack trace of the error reads: {noformat}

[jira] [Updated] (AMQ-3430) activemq-web: SessionPool.returnSession() should discard sessions that are closed.

[ https://issues.apache.org/jira/browse/AMQ-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-3430: Attachment: AMQ-3430.patch Attaching a possible fix including some logging for SessionPool.java It

[jira] [Created] (AMQ-3425) Unable to delete a queue via web console

Unable to delete a queue via web console Key: AMQ-3425 URL: https://issues.apache.org/jira/browse/AMQ-3425 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.5.0,

[jira] [Commented] (AMQ-2455) Need a facility to retry jms connections to a foreign provider by the ActiveMQ JMS bridge.

[ https://issues.apache.org/jira/browse/AMQ-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068869#comment-13068869 ] Torsten Mielke commented on AMQ-2455: - I can confirm that this issue isn't fixed in 5.5

[jira] [Reopened] (AMQ-2455) Need a facility to retry jms connections to a foreign provider by the ActiveMQ JMS bridge.

[ https://issues.apache.org/jira/browse/AMQ-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke reopened AMQ-2455: - Reopening the case as the issue is not fixed. Need a facility to retry jms connections to a foreign

[jira] [Updated] (AMQ-3375) stomp consumer might not receive all msgs of a queue

[ https://issues.apache.org/jira/browse/AMQ-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-3375: Attachment: stomp-testcase.tgz Attaching a test case in JUnit format. It may take a number of test

  1   2   >