[jira] [Commented] (ARTEMIS-392) Netty doesn't set Allocators after HTTP socket upgrade

[ https://issues.apache.org/jira/browse/ARTEMIS-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15135067#comment-15135067 ] ASF GitHub Bot commented on ARTEMIS-392: GitHub user clebertsuconic opened a pull request:

[jira] [Commented] (AMQ-6156) ActiveMQConnection threads in parked state during startup

[ https://issues.apache.org/jira/browse/AMQ-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134434#comment-15134434 ] Timothy Bish commented on AMQ-6156: --- Would need to check your tests, I just did this and it works as

[jira] [Commented] (ARTEMIS-387) Typos in error message

[ https://issues.apache.org/jira/browse/ARTEMIS-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134419#comment-15134419 ] Mike Hearn commented on ARTEMIS-387: Eventually, sure. Right now I'm under some time/delivery

[jira] [Assigned] (ARTEMIS-388) No obvious way to discover whether an embedded server actually started OK or not

[ https://issues.apache.org/jira/browse/ARTEMIS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-388: -- Assignee: Justin Bertram > No obvious way to discover whether an embedded server

[jira] [Commented] (AMQ-6156) ActiveMQConnection threads in parked state during startup

[ https://issues.apache.org/jira/browse/AMQ-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134306#comment-15134306 ] Ger Lawlor commented on AMQ-6156: - Hi Timothy, I've started making changes in respect of your comments

[jira] [Commented] (AMQ-6156) ActiveMQConnection threads in parked state during startup

[ https://issues.apache.org/jira/browse/AMQ-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134321#comment-15134321 ] Timothy Bish commented on AMQ-6156: --- Your URI is incorrect, the failover options don't get applied to each

[jira] [Created] (AMQ-6161) Not able start active mq 5.13.0

Vijaya Ragavan created AMQ-6161: Summary: Not able start active mq 5.13.0 Key: AMQ-6161 URL: https://issues.apache.org/jira/browse/AMQ-6161 Project: ActiveMQ Issue Type: Bug

[jira] [Commented] (AMQ-6156) ActiveMQConnection threads in parked state during startup

[ https://issues.apache.org/jira/browse/AMQ-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134369#comment-15134369 ] Ger Lawlor commented on AMQ-6156: - Hi, I also tried the format you suggest e.g.

[jira] [Commented] (AMQ-6156) ActiveMQConnection threads in parked state during startup

[ https://issues.apache.org/jira/browse/AMQ-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134423#comment-15134423 ] Ger Lawlor commented on AMQ-6156: - I've upgraded from 5.11.1 to 5.13.0 on suspicion that the error may have

[jira] [Updated] (ARTEMIS-389) See NPE on artemis backup log (ReplicationAddTXMessage)

[ https://issues.apache.org/jira/browse/ARTEMIS-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Howard Nguyen updated ARTEMIS-389: -- Description: {code} 00:02:11,891 WARN [org.apache.activemq.artemis.core.server] AMQ222086:

[jira] [Commented] (ARTEMIS-387) Typos in error message

[ https://issues.apache.org/jira/browse/ARTEMIS-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134604#comment-15134604 ] ASF GitHub Bot commented on ARTEMIS-387: GitHub user jbertram opened a pull request:

[jira] [Commented] (AMQ-6161) Not able start active mq 5.13.0

[ https://issues.apache.org/jira/browse/AMQ-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134521#comment-15134521 ] Christopher L. Shannon commented on AMQ-6161: - Are you using the tar.gz distribution? On my 64

[jira] [Closed] (ARTEMIS-387) Typos in error message

[ https://issues.apache.org/jira/browse/ARTEMIS-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-387. --- Resolution: Fixed Fix Version/s: 1.3.0 > Typos in error message >

[jira] [Commented] (ARTEMIS-390) ReplicationAddMessage java.lang.IllegalStateException: Cannot find add info

[ https://issues.apache.org/jira/browse/ARTEMIS-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134751#comment-15134751 ] Justin Bertram commented on ARTEMIS-390: Can you provide details on the use-case here or

[jira] [Commented] (ARTEMIS-389) See NPE on artemis backup log (ReplicationAddTXMessage)

[ https://issues.apache.org/jira/browse/ARTEMIS-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134745#comment-15134745 ] Justin Bertram commented on ARTEMIS-389: Can you provide details on the use-case here or

[jira] [Created] (ARTEMIS-389) See NPE on artemis backup log (ReplicationAddTXMessage)

Howard Nguyen created ARTEMIS-389: - Summary: See NPE on artemis backup log (ReplicationAddTXMessage) Key: ARTEMIS-389 URL: https://issues.apache.org/jira/browse/ARTEMIS-389 Project: ActiveMQ Artemis

[jira] [Commented] (AMQ-6161) Not able start active mq 5.13.0

[ https://issues.apache.org/jira/browse/AMQ-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134799#comment-15134799 ] Christopher L. Shannon commented on AMQ-6161: - It looks like you are using SunOS on sparc

[jira] [Created] (ARTEMIS-392) Netty doesn't set Allocators after HTTP socket upgrade

clebert suconic created ARTEMIS-392: --- Summary: Netty doesn't set Allocators after HTTP socket upgrade Key: ARTEMIS-392 URL: https://issues.apache.org/jira/browse/ARTEMIS-392 Project: ActiveMQ

[jira] [Created] (OPENWIRE-12) Remove dependency on Hawtbuf

Timothy Bish created OPENWIRE-12: Summary: Remove dependency on Hawtbuf Key: OPENWIRE-12 URL: https://issues.apache.org/jira/browse/OPENWIRE-12 Project: ActiveMQ OpenWire Issue Type:

[jira] [Commented] (OPENWIRE-12) Remove dependency on Hawtbuf

[ https://issues.apache.org/jira/browse/OPENWIRE-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134877#comment-15134877 ] ASF subversion and git services commented on OPENWIRE-12: - Commit

[jira] [Updated] (OPENWIRE-12) Remove dependency on Hawtbuf

[ https://issues.apache.org/jira/browse/OPENWIRE-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated OPENWIRE-12: - Fix Version/s: 1.0 > Remove dependency on Hawtbuf > > >

[jira] [Created] (ARTEMIS-391) Connection Limit doesn't log when over the limit

clebert suconic created ARTEMIS-391: --- Summary: Connection Limit doesn't log when over the limit Key: ARTEMIS-391 URL: https://issues.apache.org/jira/browse/ARTEMIS-391 Project: ActiveMQ Artemis

[jira] [Commented] (ARTEMIS-391) Connection Limit doesn't log when over the limit

[ https://issues.apache.org/jira/browse/ARTEMIS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134950#comment-15134950 ] clebert suconic commented on ARTEMIS-391: - [~jbertram] I am assigining this to you just as I know

[jira] [Updated] (ARTEMIS-391) Connection Limit doesn't log when over the limit

[ https://issues.apache.org/jira/browse/ARTEMIS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-391: Assignee: Justin Bertram Affects Version/s: 1.2.0 Fix Version/s: 1.3.0

[jira] [Resolved] (OPENWIRE-12) Remove dependency on Hawtbuf

[ https://issues.apache.org/jira/browse/OPENWIRE-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved OPENWIRE-12. -- Resolution: Fixed > Remove dependency on Hawtbuf > > >

[jira] [Updated] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID

[ https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Hadlich updated AMQ-6160: -- Description: The messageId.getEntryLocator() gives null which leads to the NPE. Example stacktrace:

[jira] [Commented] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID

[ https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133904#comment-15133904 ] Jens Hadlich commented on AMQ-6160: --- Proposed solution: Use messageId.getFutureOrSequenceLong() to get the

[jira] [Updated] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID

[ https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Hadlich updated AMQ-6160: -- Description: The messageId.getEntryLocator() gives null which leads to the NPE. The NPE seems to lead to

[jira] [Updated] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID

[ https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Hadlich updated AMQ-6160: -- Description: The messageId.getEntryLocator() gives null which leads to the NPE. The NPE seems to lead to

[jira] [Updated] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID

[ https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Hadlich updated AMQ-6160: -- Affects Version/s: 5.13.0 > JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to >

[jira] [Comment Edited] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID

[ https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133904#comment-15133904 ] Jens Hadlich edited comment on AMQ-6160 at 2/5/16 9:48 AM: --- Actually, I'm not

[jira] [Commented] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID

[ https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133907#comment-15133907 ] ASF GitHub Bot commented on AMQ-6160: - GitHub user jenshadlich opened a pull request:

[jira] [Comment Edited] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID

[ https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133904#comment-15133904 ] Jens Hadlich edited comment on AMQ-6160 at 2/5/16 9:48 AM: --- Actually, I'm not

[jira] [Created] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID

Jens Hadlich created AMQ-6160: - Summary: JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID Key: AMQ-6160 URL: https://issues.apache.org/jira/browse/AMQ-6160

[jira] [Commented] (AMQ-6147) AMQP: Update Proton-J to 0.12.0

[ https://issues.apache.org/jira/browse/AMQ-6147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133965#comment-15133965 ] Robbie Gemmell commented on AMQ-6147: - Yep, planned to eventually, don't think I had added that yet when

[jira] [Resolved] (AMQ-6157) Thread leak when failover fails to connect at startup

[ https://issues.apache.org/jira/browse/AMQ-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik resolved AMQ-6157. --- Resolution: Not A Problem You are right, the problem is not in the failover but in the JMS bridge, or the use of both

[jira] [Comment Edited] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID

[ https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133904#comment-15133904 ] Jens Hadlich edited comment on AMQ-6160 at 2/5/16 9:46 AM: --- Actually I'm not quite

[jira] [Comment Edited] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID

[ https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133904#comment-15133904 ] Jens Hadlich edited comment on AMQ-6160 at 2/5/16 9:47 AM: --- Actually, I'm not

[jira] [Commented] (ARTEMIS-387) Typos in error message

[ https://issues.apache.org/jira/browse/ARTEMIS-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134235#comment-15134235 ] clebert suconic commented on ARTEMIS-387: - Nice candidate for a Pull Request. Can you do it? >

[jira] [Commented] (ARTEMIS-355) Duplex bridges

[ https://issues.apache.org/jira/browse/ARTEMIS-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134254#comment-15134254 ] Mike Hearn commented on ARTEMIS-355: Yes, my use case is to have separate servers some of which may

[jira] [Created] (ARTEMIS-388) No obvious way to discover whether an embedded server actually started OK or not

Mike Hearn created ARTEMIS-388: -- Summary: No obvious way to discover whether an embedded server actually started OK or not Key: ARTEMIS-388 URL: https://issues.apache.org/jira/browse/ARTEMIS-388

[jira] [Updated] (ARTEMIS-355) Duplex bridges

[ https://issues.apache.org/jira/browse/ARTEMIS-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-355: Fix Version/s: 1.3.0 > Duplex bridges > -- > > Key: