[jira] [Commented] (AMQ-5709) Logging of Database ... is locked should be done on level DEBUG

[ https://issues.apache.org/jira/browse/AMQ-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14507491#comment-14507491 ] Arthur Naseef commented on AMQ-5709: If I'm reading the commits correctly, the fix was

[jira] [Commented] (AMQ-5709) Logging of Database ... is locked should be done on level DEBUG

[ https://issues.apache.org/jira/browse/AMQ-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14507708#comment-14507708 ] Arthur Naseef commented on AMQ-5709: It would be good to hear from Gary since it was his

[jira] [Commented] (AMQ-5709) Logging of Database ... is locked should be done on level DEBUG

[ https://issues.apache.org/jira/browse/AMQ-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14507935#comment-14507935 ] Arthur Naseef commented on AMQ-5709: Great - thank you Gary. Logging of Database ...

[jira] [Commented] (AMQ-5598) MQTT+NIO+SSL: Concurrent connections lead to 100% CPU usage

[ https://issues.apache.org/jira/browse/AMQ-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14506456#comment-14506456 ] Arthur Naseef commented on AMQ-5598: I see - thank you for the clarification. MQTT and

[jira] [Created] (AMQCPP-569) thread creation leak with failover transport after disconnect

Arthur Naseef created AMQCPP-569: Summary: thread creation leak with failover transport after disconnect Key: AMQCPP-569 URL: https://issues.apache.org/jira/browse/AMQCPP-569 Project: ActiveMQ C++

[jira] [Commented] (AMQ-5660) Dequeue count for Topics does not increase for durable subscribers

[ https://issues.apache.org/jira/browse/AMQ-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14361127#comment-14361127 ] Arthur Naseef commented on AMQ-5660: Because of the nature of topics (being a broadcast)

[jira] [Resolved] (AMQ-5636) Upgrade the bundled DBCP component. The current one is very old and buggy.

[ https://issues.apache.org/jira/browse/AMQ-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef resolved AMQ-5636. Resolution: Fixed Fix Version/s: 5.12.0 Assignee: Arthur Naseef Fixed with commit

[jira] [Commented] (AMQ-5598) MQTT+NIO+SSL: Concurrent connections lead to 100% CPU usage

[ https://issues.apache.org/jira/browse/AMQ-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14351423#comment-14351423 ] Arthur Naseef commented on AMQ-5598: Hey Timothy - does the MQTT code in question go

[jira] [Updated] (AMQ-5598) MQTT+NIO+SSL: Concurrent connections lead to 100% CPU usage

[ https://issues.apache.org/jira/browse/AMQ-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-5598: --- Attachment: Screen Shot 2015-02-12 at 8.31.58 PM.png screen shot showing the excessive CPU usage during

[jira] [Updated] (AMQ-5565) Need to be able to start/stop brokers in karaf via commands

[ https://issues.apache.org/jira/browse/AMQ-5565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-5565: --- Fix Version/s: (was: 5.11.1) Need to be able to start/stop brokers in karaf via commands

[jira] [Updated] (AMQ-5580) Thread unsafe operations on the PersistenceAdapters in the mKahaDB implementation

[ https://issues.apache.org/jira/browse/AMQ-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-5580: --- Fix Version/s: 5.11.1 Thread unsafe operations on the PersistenceAdapters in the mKahaDB

[jira] [Resolved] (AMQ-5583) Release 5.11.1 preparation

[ https://issues.apache.org/jira/browse/AMQ-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef resolved AMQ-5583. Resolution: Fixed Release 5.11.1 has been prepared. Release 5.11.1 preparation

[jira] [Updated] (AMQ-5542) KahaDB data files containing acknowledgements are deleted during cleanup

[ https://issues.apache.org/jira/browse/AMQ-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-5542: --- Fix Version/s: 5.11.1 KahaDB data files containing acknowledgements are deleted during cleanup

[jira] [Updated] (AMQ-5573) Configurable messages size for Stomp producer

[ https://issues.apache.org/jira/browse/AMQ-5573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-5573: --- Fix Version/s: 5.11.1 Configurable messages size for Stomp producer

[jira] [Updated] (AMQ-5564) activemq-pool - Either adds new mbeans or add/remove pair of mbean for each producer in use

[ https://issues.apache.org/jira/browse/AMQ-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-5564: --- Priority: Blocker (was: Major) activemq-pool - Either adds new mbeans or add/remove pair of mbean for

[jira] [Updated] (AMQ-5567) JDBC XA - Store COMMIT FAILED: java.io.IOException: Could not remove prepared transaction state from message add for sequenceId

[ https://issues.apache.org/jira/browse/AMQ-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-5567: --- Fix Version/s: 5.11.1 JDBC XA - Store COMMIT FAILED: java.io.IOException: Could not remove

[jira] [Resolved] (AMQ-5586) Unused ConnectionControl command should be removed

[ https://issues.apache.org/jira/browse/AMQ-5586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef resolved AMQ-5586. Resolution: Fixed Fix Version/s: 5.10.2 Fixe by commit

[jira] [Created] (AMQ-5586) Unused ConnectionControl command should be removed

Arthur Naseef created AMQ-5586: -- Summary: Unused ConnectionControl command should be removed Key: AMQ-5586 URL: https://issues.apache.org/jira/browse/AMQ-5586 Project: ActiveMQ Issue Type: Bug

[jira] [Updated] (AMQ-5584) Release 5.10.2 preparation

[ https://issues.apache.org/jira/browse/AMQ-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-5584: --- Description: Prepare for the 5.10.2 release. Administrative and minor release-specific updates will be

[jira] [Created] (AMQ-5584) Release 5.10.2 preparation

Arthur Naseef created AMQ-5584: -- Summary: Release 5.10.2 preparation Key: AMQ-5584 URL: https://issues.apache.org/jira/browse/AMQ-5584 Project: ActiveMQ Issue Type: Bug Reporter:

[jira] [Created] (AMQ-5583) Release 5.11.1 preparation

Arthur Naseef created AMQ-5583: -- Summary: Release 5.11.1 preparation Key: AMQ-5583 URL: https://issues.apache.org/jira/browse/AMQ-5583 Project: ActiveMQ Issue Type: Bug Reporter:

[jira] [Commented] (AMQ-5471) Configuration server for Network of Brokers

[ https://issues.apache.org/jira/browse/AMQ-5471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14319129#comment-14319129 ] Arthur Naseef commented on AMQ-5471: Tim's comments are interesting. Reminds me of

[jira] [Assigned] (AMQ-5478) REST endpoint creates topic instead of queue

[ https://issues.apache.org/jira/browse/AMQ-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef reassigned AMQ-5478: -- Assignee: Arthur Naseef REST endpoint creates topic instead of queue

[jira] [Created] (AMQ-5579) REST production of message bodies can result in IllegalStateException: STREAMED

Arthur Naseef created AMQ-5579: -- Summary: REST production of message bodies can result in IllegalStateException: STREAMED Key: AMQ-5579 URL: https://issues.apache.org/jira/browse/AMQ-5579 Project:

[jira] [Updated] (AMQ-5579) REST production of message bodies can result in IllegalStateException: STREAMED

[ https://issues.apache.org/jira/browse/AMQ-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-5579: --- Description: Attempting to post a message to AMQ using the following yields an IllegalStateException:

[jira] [Resolved] (AMQ-5579) REST production of message bodies can result in IllegalStateException: STREAMED

[ https://issues.apache.org/jira/browse/AMQ-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef resolved AMQ-5579. Resolution: Fixed Thanks Mark. Looks like a good way to resolve under the circumstances. REST

[jira] [Commented] (AMQ-5579) REST production of message bodies can result in IllegalStateException: STREAMED

[ https://issues.apache.org/jira/browse/AMQ-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317546#comment-14317546 ] Arthur Naseef commented on AMQ-5579: Sure thing - go for it Mark. REST production of

[jira] [Commented] (AMQ-5574) OSGi import ranges for javax.jms should include version 2.0

[ https://issues.apache.org/jira/browse/AMQ-5574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14313100#comment-14313100 ] Arthur Naseef commented on AMQ-5574: From what I understand of the JMS 2 spec, I agree;

[jira] [Commented] (AMQ-5564) activemq-pool - Either adds new mbeans or add/remove pair of mbean for each producer in use

[ https://issues.apache.org/jira/browse/AMQ-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14308100#comment-14308100 ] Arthur Naseef commented on AMQ-5564: So, the anonymous producer is getting created and

[jira] [Commented] (AMQ-5566) Karaf test fails when standard ports already in-use on the system

[ https://issues.apache.org/jira/browse/AMQ-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14305437#comment-14305437 ] Arthur Naseef commented on AMQ-5566: *Port 1099 Failure Exception* {noformat} karaf@root

[jira] [Updated] (AMQ-5566) Karaf test fails when standard ports already in-use on the system

[ https://issues.apache.org/jira/browse/AMQ-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-5566: --- Priority: Minor (was: Major) Karaf test fails when standard ports already in-use on the system

[jira] [Created] (AMQ-5566) Karaf test fails when standard ports already in-use on the system

Arthur Naseef created AMQ-5566: -- Summary: Karaf test fails when standard ports already in-use on the system Key: AMQ-5566 URL: https://issues.apache.org/jira/browse/AMQ-5566 Project: ActiveMQ

[jira] [Commented] (AMQ-5566) Karaf test fails when standard ports already in-use on the system

[ https://issues.apache.org/jira/browse/AMQ-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14305436#comment-14305436 ] Arthur Naseef commented on AMQ-5566: *Port 61616 Failure Exception* {noformat}

[jira] [Commented] (AMQ-5557) GC of inactive queues should happen even if consumers 0

[ https://issues.apache.org/jira/browse/AMQ-5557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14300870#comment-14300870 ] Arthur Naseef commented on AMQ-5557: As I mentioned on the USER mail list, it seems odd

[jira] [Commented] (AMQ-5557) GC of inactive queues should happen even if consumers 0

[ https://issues.apache.org/jira/browse/AMQ-5557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14300871#comment-14300871 ] Arthur Naseef commented on AMQ-5557: {quote}For example, if you have a 60 second window,

[jira] [Commented] (AMQ-5552) introduce a smoke-test profile that is enabled by default and during release:prepare

[ https://issues.apache.org/jira/browse/AMQ-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14300031#comment-14300031 ] Arthur Naseef commented on AMQ-5552: There is good and bad here. I like the idea of a

[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=14299692#comment-14299692 ] Arthur Naseef commented on AMQ-5549: One thing to make clear here (it seemed unclear

[jira] [Commented] (AMQ-5542) KahaDB data files containing acknowledgements are deleted during cleanup

[ https://issues.apache.org/jira/browse/AMQ-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296330#comment-14296330 ] Arthur Naseef commented on AMQ-5542: DLQs are a common cause of this problem. My

[jira] [Commented] (AMQ-5542) KahaDB data files containing acknowledgements are deleted during cleanup

[ https://issues.apache.org/jira/browse/AMQ-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295399#comment-14295399 ] Arthur Naseef commented on AMQ-5542: To Tim's point -- if there is *any* content in the

[jira] [Updated] (AMQ-5509) Broker quits silently when no access to activemq-data folder

[ https://issues.apache.org/jira/browse/AMQ-5509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-5509: --- Fix Version/s: (was: 5.10.1) Broker quits silently when no access to activemq-data folder

[jira] [Assigned] (AMQ-5514) Create Release 5.10.1

[ https://issues.apache.org/jira/browse/AMQ-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef reassigned AMQ-5514: -- Assignee: Arthur Naseef Create Release 5.10.1 - Key:

[jira] [Resolved] (AMQ-5514) Create Release 5.10.1

[ https://issues.apache.org/jira/browse/AMQ-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef resolved AMQ-5514. Resolution: Done Fix Version/s: 5.10.1 Work to prepare the 5.10.1 release is complete.

[jira] [Created] (AMQ-5522) Limit the number of messages in individual queues instead of, or in addition to, limiting memory and store usage

Arthur Naseef created AMQ-5522: -- Summary: Limit the number of messages in individual queues instead of, or in addition to, limiting memory and store usage Key: AMQ-5522 URL:

[jira] [Created] (AMQ-5514) Create Release 5.10.1

Arthur Naseef created AMQ-5514: -- Summary: Create Release 5.10.1 Key: AMQ-5514 URL: https://issues.apache.org/jira/browse/AMQ-5514 Project: ActiveMQ Issue Type: Bug Reporter: Arthur

[jira] [Commented] (AMQ-5514) Create Release 5.10.1

[ https://issues.apache.org/jira/browse/AMQ-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14271741#comment-14271741 ] Arthur Naseef commented on AMQ-5514: From Dejan: {quote} spring.schemas should be

[jira] [Commented] (AMQ-5514) Create Release 5.10.1

[ https://issues.apache.org/jira/browse/AMQ-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14271767#comment-14271767 ] Arthur Naseef commented on AMQ-5514: Spring schema's updated: git revisions: *

[jira] [Commented] (AMQ-5509) Broker quits silently when no access to activemq-data folder

[ https://issues.apache.org/jira/browse/AMQ-5509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270169#comment-14270169 ] Arthur Naseef commented on AMQ-5509: Using the code above to create a test program, I

[jira] [Resolved] (AMQ-5499) Add means to dynamically allocate port number for integration testing using maven plugin

[ https://issues.apache.org/jira/browse/AMQ-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef resolved AMQ-5499. Resolution: Fixed Added registration of all transport connector publishable addresses on broker

[jira] [Assigned] (AMQ-4510) activemq-maven-plugin should optionally not fail if already started

[ https://issues.apache.org/jira/browse/AMQ-4510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef reassigned AMQ-4510: -- Assignee: Arthur Naseef activemq-maven-plugin should optionally not fail if already started

[jira] [Created] (AMQ-5499) Add means to dynamically allocate port number for integration testing using maven plugin

Arthur Naseef created AMQ-5499: -- Summary: Add means to dynamically allocate port number for integration testing using maven plugin Key: AMQ-5499 URL: https://issues.apache.org/jira/browse/AMQ-5499

[jira] [Commented] (AMQ-4893) UTF8Buffer should be a valid object for setObjectProperty

[ https://issues.apache.org/jira/browse/AMQ-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027302#comment-14027302 ] Arthur Naseef commented on AMQ-4893: Fix revision:

[jira] [Commented] (AMQ-4892) MQTT clients disconnecting due to socket error do not publish the configured last will and testament message.

[ https://issues.apache.org/jira/browse/AMQ-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027305#comment-14027305 ] Arthur Naseef commented on AMQ-4892: Fix revision:

[jira] [Commented] (AMQ-4883) Fusesource release repo not needed

[ https://issues.apache.org/jira/browse/AMQ-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027308#comment-14027308 ] Arthur Naseef commented on AMQ-4883: Fix revision:

[jira] [Commented] (AMQ-4970) Deletion of a queue inaffective across broker restart

[ https://issues.apache.org/jira/browse/AMQ-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027309#comment-14027309 ] Arthur Naseef commented on AMQ-4970: Fix revision:

[jira] [Commented] (AMQ-4857) WSServlet.doWebSocketConnect throws NPE if called with null protocol

[ https://issues.apache.org/jira/browse/AMQ-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027307#comment-14027307 ] Arthur Naseef commented on AMQ-4857: Fix revision:

[jira] [Reopened] (AMQ-4794) activemq web console fails in karaf+equinox

[ https://issues.apache.org/jira/browse/AMQ-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef reopened AMQ-4794: Re-opening this issue as the ActiveMQ console remains an active, important part of the solution.

[jira] [Updated] (AMQ-4794) activemq web console fails in karaf+equinox

[ https://issues.apache.org/jira/browse/AMQ-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-4794: --- Fix Version/s: (was: 5.10.0) Removing the fix-in version as this is still open. activemq web

[jira] [Reopened] (AMQ-4958) Ignored InterruptedException in IdGenerator

[ https://issues.apache.org/jira/browse/AMQ-4958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef reopened AMQ-4958: I'm reopening this issue because of the following making it hard to tell that any change was made to

[jira] [Resolved] (AMQ-4958) Ignored InterruptedException in IdGenerator

[ https://issues.apache.org/jira/browse/AMQ-4958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef resolved AMQ-4958. Resolution: Fixed My mistake - the patch was applied, with edits, on commit

[jira] [Commented] (AMQ-4967) activemq-camel should explicitly Import-Package org.apache.activemq.pool

[ https://issues.apache.org/jira/browse/AMQ-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020920#comment-14020920 ] Arthur Naseef commented on AMQ-4967: Fix commit:

[jira] [Commented] (AMQ-4947) Reduce the reliance on fsync when writing to disk

[ https://issues.apache.org/jira/browse/AMQ-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020925#comment-14020925 ] Arthur Naseef commented on AMQ-4947: Fix commits:

[jira] [Commented] (AMQ-4927) clients can not receive mqtt retained message

[ https://issues.apache.org/jira/browse/AMQ-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020927#comment-14020927 ] Arthur Naseef commented on AMQ-4927: @Paddy - can you provide evidence this is not fixed

[jira] [Commented] (AMQ-4926) Extends activemq-karaf import version range to work with both Karaf 2 3

[ https://issues.apache.org/jira/browse/AMQ-4926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020956#comment-14020956 ] Arthur Naseef commented on AMQ-4926: Fixed with Commit:

[jira] [Commented] (AMQ-4906) advisory producerCount = 0 is not received on temporary queue

[ https://issues.apache.org/jira/browse/AMQ-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020957#comment-14020957 ] Arthur Naseef commented on AMQ-4906: Git commit:

[jira] [Commented] (AMQ-4917) LevelDB store can fail when using durable subs

[ https://issues.apache.org/jira/browse/AMQ-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020959#comment-14020959 ] Arthur Naseef commented on AMQ-4917: Git commit:

[jira] [Commented] (AMQ-4918) Added JMX metics for networks per destination

[ https://issues.apache.org/jira/browse/AMQ-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020960#comment-14020960 ] Arthur Naseef commented on AMQ-4918: Git commits:

[jira] [Commented] (AMQ-4909) OSGi granularity of activemq-osgi bundle

[ https://issues.apache.org/jira/browse/AMQ-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020961#comment-14020961 ] Arthur Naseef commented on AMQ-4909: Git commits:

[jira] [Commented] (AMQ-4399) jdbcPersistenceAdapter takes a long time to shutdown, causing journal recovery

[ https://issues.apache.org/jira/browse/AMQ-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020966#comment-14020966 ] Arthur Naseef commented on AMQ-4399: Git commit:

[jira] [Commented] (AMQ-4325) camel doen't honor credentials set on activemqcomponent bean via spring

[ https://issues.apache.org/jira/browse/AMQ-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020967#comment-14020967 ] Arthur Naseef commented on AMQ-4325: Git commit:

[jira] [Commented] (AMQ-2960) PooledConnectionFactoryBean returns null in OSGi env sometimes

[ https://issues.apache.org/jira/browse/AMQ-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020972#comment-14020972 ] Arthur Naseef commented on AMQ-2960: Git commit:

[jira] [Commented] (AMQ-2429) Show flow control being active on web console ...

[ https://issues.apache.org/jira/browse/AMQ-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020973#comment-14020973 ] Arthur Naseef commented on AMQ-2429: Commit link:

[jira] [Commented] (AMQ-3388) Http/https protocol uses Xstream for serializing commands in xml. Field additions to the commands bresks xtream serializacion between amq versions

[ https://issues.apache.org/jira/browse/AMQ-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020975#comment-14020975 ] Arthur Naseef commented on AMQ-3388: Git commit:

[jira] [Commented] (AMQ-3725) Kahadb error during SAN failover delayed write - Allow kahaDB to recover in a similar manner as the JDBC store using the IOExceptionHandler

[ https://issues.apache.org/jira/browse/AMQ-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020977#comment-14020977 ] Arthur Naseef commented on AMQ-3725: Git commits:

[jira] [Commented] (AMQ-4823) NetworkConnector not registered in JMX when created from Broker View

[ https://issues.apache.org/jira/browse/AMQ-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020979#comment-14020979 ] Arthur Naseef commented on AMQ-4823: Git commit:

[jira] [Commented] (AMQ-4822) DynamicallyIncludedDestinationsDuplexNetworkTest.testDynamicallyIncludedDestinationsForDuplex fails on EC2 boxes

[ https://issues.apache.org/jira/browse/AMQ-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020978#comment-14020978 ] Arthur Naseef commented on AMQ-4822: Git commit:

[jira] [Commented] (AMQ-4825) ConnectionFactory and ActiveMQCamelComponent should default to the right port if on OpenShift

[ https://issues.apache.org/jira/browse/AMQ-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020981#comment-14020981 ] Arthur Naseef commented on AMQ-4825: Git commit:

[jira] [Commented] (AMQ-4706) Failover transport - Add option to configure WARN logging internval for failover attempts still failing

[ https://issues.apache.org/jira/browse/AMQ-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020983#comment-14020983 ] Arthur Naseef commented on AMQ-4706: Git commit:

[jira] [Commented] (AMQ-5137) make networkConnector decreaseNetworkConsumerPriority=true the default

[ https://issues.apache.org/jira/browse/AMQ-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13962474#comment-13962474 ] Arthur Naseef commented on AMQ-5137: There are use cases for both settings - so, the

[jira] [Commented] (AMQ-5137) make networkConnector decreaseNetworkConsumerPriority=true the default

[ https://issues.apache.org/jira/browse/AMQ-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13961103#comment-13961103 ] Arthur Naseef commented on AMQ-5137: While it may make sense to have true be the

[jira] [Closed] (AMQ-4882) LevelDB can get to a corrupt state when using XA transactions

[ https://issues.apache.org/jira/browse/AMQ-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef closed AMQ-4882. -- Resolution: Cannot Reproduce Closing this since we failed to reproduce and the creator of the issue is

[jira] [Commented] (AMQ-4955) TCP Connections and related thread leak.

[ https://issues.apache.org/jira/browse/AMQ-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13956115#comment-13956115 ] Arthur Naseef commented on AMQ-4955: Throwing an exception on dispatching a BrokerInfo

[jira] [Commented] (AMQ-4955) TCP Connections and related thread leak.

[ https://issues.apache.org/jira/browse/AMQ-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13956124#comment-13956124 ] Arthur Naseef commented on AMQ-4955: Reading back through the comments, I see the issue

[jira] [Resolved] (AMQ-5107) In-flight queue message redelivered to multiple listeners upon broker shutdown

[ https://issues.apache.org/jira/browse/AMQ-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef resolved AMQ-5107. Resolution: Fixed Fix Version/s: (was: NEEDS_REVIEW) 5.10.0 Fixed

[jira] [Commented] (AMQ-5098) ActiveMQ fails and starts complaining lock is already held for the JVM

[ https://issues.apache.org/jira/browse/AMQ-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13948785#comment-13948785 ] Arthur Naseef commented on AMQ-5098: Great. Let me know if you find anything.

[jira] [Commented] (AMQ-5107) In-flight queue message redelivered to multiple listeners upon broker shutdown

[ https://issues.apache.org/jira/browse/AMQ-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13940463#comment-13940463 ] Arthur Naseef commented on AMQ-5107: Thanks Gary - I'll take a look at that; if it

[jira] [Assigned] (AMQ-5107) In-flight queue message redelivered to multiple listeners upon broker shutdown

[ https://issues.apache.org/jira/browse/AMQ-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef reassigned AMQ-5107: -- Assignee: Arthur Naseef In-flight queue message redelivered to multiple listeners upon broker

[jira] [Commented] (AMQ-5107) In-flight queue message redelivered to multiple listeners upon broker shutdown

[ https://issues.apache.org/jira/browse/AMQ-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13939910#comment-13939910 ] Arthur Naseef commented on AMQ-5107: Are the duplicates only as the broker shuts down,

[jira] [Commented] (AMQ-5107) In-flight queue message redelivered to multiple listeners upon broker shutdown

[ https://issues.apache.org/jira/browse/AMQ-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13939940#comment-13939940 ] Arthur Naseef commented on AMQ-5107: Problem exists on 5.10-SNAPSHOT. In-flight queue

[jira] [Commented] (AMQ-5107) In-flight queue message redelivered to multiple listeners upon broker shutdown

[ https://issues.apache.org/jira/browse/AMQ-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13940096#comment-13940096 ] Arthur Naseef commented on AMQ-5107: Looking at this more closely, I'm leaning toward

[jira] [Commented] (AMQ-2429) Show flow control being active on web console ...

[ https://issues.apache.org/jira/browse/AMQ-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13936014#comment-13936014 ] Arthur Naseef commented on AMQ-2429: Fixed with commit

[jira] [Resolved] (AMQ-5104) Show non-durable Topic subscriptions on the web console

[ https://issues.apache.org/jira/browse/AMQ-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef resolved AMQ-5104. Resolution: Fixed Fix Version/s: 5.10.0 Fixed with commit

[jira] [Commented] (AMQ-4499) Enhance the web console

[ https://issues.apache.org/jira/browse/AMQ-4499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13936028#comment-13936028 ] Arthur Naseef commented on AMQ-4499: For number 2 on the list (producer list on

[jira] [Updated] (AMQ-5098) ActiveMQ fails and starts complaining lock is already held for the JVM

[ https://issues.apache.org/jira/browse/AMQ-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-5098: --- Fix Version/s: (was: 5.10.0) ActiveMQ fails and starts complaining lock is already held for the

[jira] [Assigned] (AMQ-2429) Show flow control being active on web console ...

[ https://issues.apache.org/jira/browse/AMQ-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef reassigned AMQ-2429: -- Assignee: Arthur Naseef Show flow control being active on web console ...

[jira] [Resolved] (AMQ-2429) Show flow control being active on web console ...

[ https://issues.apache.org/jira/browse/AMQ-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef resolved AMQ-2429. Resolution: Fixed Fix Version/s: (was: 5.x) 5.10.0 Added pages listing

[jira] [Created] (AMQ-5104) Show non-durable Topic subscriptions on the web console

Arthur Naseef created AMQ-5104: -- Summary: Show non-durable Topic subscriptions on the web console Key: AMQ-5104 URL: https://issues.apache.org/jira/browse/AMQ-5104 Project: ActiveMQ Issue Type:

[jira] [Commented] (AMQ-5018) LockFile unlock method not reliable in case of network issues

[ https://issues.apache.org/jira/browse/AMQ-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933168#comment-13933168 ] Arthur Naseef commented on AMQ-5018: That workaround only makes sense if the JVM is not

[jira] [Created] (AMQ-5098) ActiveMQ fails to start complaining lock is already held for the JVM

Arthur Naseef created AMQ-5098: -- Summary: ActiveMQ fails to start complaining lock is already held for the JVM Key: AMQ-5098 URL: https://issues.apache.org/jira/browse/AMQ-5098 Project: ActiveMQ

[jira] [Updated] (AMQ-5098) ActiveMQ fails to start complaining lock is already held for the JVM

[ https://issues.apache.org/jira/browse/AMQ-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-5098: --- Attachment: STACK_DIFFS.txt Attaching STACK_DIFFS.txt which contains a unified diff of the two stack

[jira] [Updated] (AMQ-5098) ActiveMQ fails to start complaining lock is already held for the JVM

[ https://issues.apache.org/jira/browse/AMQ-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-5098: --- Attachment: activemq.log Attaching activemq.log from a failed start, with the two stack traces

  1   2   3   >