[jira] [Comment Edited] (AMQ-4898) LocalTransaction PRE COMMIT FAILED: java.util.ConcurrentModificationException

[ https://issues.apache.org/jira/browse/AMQ-4898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827783#comment-13827783 ] Gary Tully edited comment on AMQ-4898 at 11/20/13 3:57 PM: --- using

[jira] [Commented] (AMQ-4898) LocalTransaction PRE COMMIT FAILED: java.util.ConcurrentModificationException

[ https://issues.apache.org/jira/browse/AMQ-4898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827783#comment-13827783 ] Gary Tully commented on AMQ-4898: - using alwaysSendSync will also avoid this > LocalTransac

[jira] [Commented] (AMQ-4898) LocalTransaction PRE COMMIT FAILED: java.util.ConcurrentModificationException

[ https://issues.apache.org/jira/browse/AMQ-4898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827780#comment-13827780 ] Gary Tully commented on AMQ-4898: - this points to pfc and transactions not working well. the

AMQ 5.8 | Issue with re-generating Kerberos token during failover

We are using failover transport for connecting to network of brokers and we are using kerberos for authentication and authorization. During connection setup in connection factory create connection we generate a kerberos token and set is in the password field of the AMQ connection factory. Broker a

[jira] [Commented] (AMQ-4097) Broker-to-Broker Reconnect fails wrongly due to duplicate name

[ https://issues.apache.org/jira/browse/AMQ-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827665#comment-13827665 ] Ron Koerner commented on AMQ-4097: -- Hi Amine, what you wrote is probably a prerequisite to

[jira] [Commented] (AMQ-4837) LevelDB corrupted in AMQ cluster

[ https://issues.apache.org/jira/browse/AMQ-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827654#comment-13827654 ] Tenzin giatso commented on AMQ-4837: I've try this night with AMQ 5.9 levelDb (no cluste

[jira] [Created] (AMQ-4898) LocalTransaction PRE COMMIT FAILED: java.util.ConcurrentModificationException

Gary Tully created AMQ-4898: --- Summary: LocalTransaction PRE COMMIT FAILED: java.util.ConcurrentModificationException Key: AMQ-4898 URL: https://issues.apache.org/jira/browse/AMQ-4898 Project: ActiveMQ

[jira] [Comment Edited] (AMQ-4097) Broker-to-Broker Reconnect fails wrongly due to duplicate name

[ https://issues.apache.org/jira/browse/AMQ-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827509#comment-13827509 ] Amine edited comment on AMQ-4097 at 11/20/13 11:21 AM: --- Hi, To resolv

[jira] [Commented] (AMQ-4693) Add kerberos [SASL] authentication for TCP connectors

[ https://issues.apache.org/jira/browse/AMQ-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827518#comment-13827518 ] Steven commented on AMQ-4693: - Hmm.. Is there any roadmap/projects pipeline page where we could

[jira] [Commented] (AMQ-4693) Add kerberos [SASL] authentication for TCP connectors

[ https://issues.apache.org/jira/browse/AMQ-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827517#comment-13827517 ] John Bing commented on AMQ-4693: Taking this up in January might be ok for my case. I guess

[jira] [Commented] (AMQ-4097) Broker-to-Broker Reconnect fails wrongly due to duplicate name

[ https://issues.apache.org/jira/browse/AMQ-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827509#comment-13827509 ] Amine commented on AMQ-4097: Hi, To resolve this, the network connector name between your broke