[jira] [Commented] (ARTEMIS-1812) [core] Any Subsequent messages are lost after queue is emptied from slave broker (succ failover from master kill)

[ https://issues.apache.org/jira/browse/ARTEMIS-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443591#comment-16443591 ] ASF GitHub Bot commented on ARTEMIS-1812: - Github user stanlyDoge commented on the issue:

[jira] [Commented] (ARTEMIS-1498) [interop] Openwire internal headers should not be part of message properties

[ https://issues.apache.org/jira/browse/ARTEMIS-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443155#comment-16443155 ] ASF GitHub Bot commented on ARTEMIS-1498: - Github user clebertsuconic commented on the issue:

[jira] [Commented] (ARTEMIS-1498) [interop] Openwire internal headers should not be part of message properties

[ https://issues.apache.org/jira/browse/ARTEMIS-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443121#comment-16443121 ] ASF GitHub Bot commented on ARTEMIS-1498: - Github user michaelandrepearce commented on the

[jira] [Commented] (ARTEMIS-1498) [interop] Openwire internal headers should not be part of message properties

[ https://issues.apache.org/jira/browse/ARTEMIS-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443113#comment-16443113 ] ASF GitHub Bot commented on ARTEMIS-1498: - Github user clebertsuconic commented on the issue:

[jira] [Commented] (ARTEMIS-1498) [interop] Openwire internal headers should not be part of message properties

[ https://issues.apache.org/jira/browse/ARTEMIS-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443109#comment-16443109 ] ASF GitHub Bot commented on ARTEMIS-1498: - Github user michaelandrepearce commented on the

[jira] [Updated] (AMQ-6947) Queue pending message count can go negative on duplicates

[ https://issues.apache.org/jira/browse/AMQ-6947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-6947: Fix Version/s: (was: 5.15.4) (was: 5.16.0) > Queue pending

[jira] [Commented] (AMQ-6947) Queue pending message count can go negative on duplicates

[ https://issues.apache.org/jira/browse/AMQ-6947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442816#comment-16442816 ] Christopher L. Shannon commented on AMQ-6947: - I reverted my commits because the issue still

[jira] [Commented] (AMQ-6947) Queue pending message count can go negative on duplicates

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

[jira] [Commented] (AMQ-6947) Queue pending message count can go negative on duplicates

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

[jira] [Commented] (AMQ-6947) Queue pending message count can go negative on duplicates

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

[jira] [Commented] (AMQ-6947) Queue pending message count can go negative on duplicates

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

[jira] [Reopened] (AMQ-6947) Queue pending message count can go negative on duplicates

[ https://issues.apache.org/jira/browse/AMQ-6947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon reopened AMQ-6947: - Assignee: (was: Christopher L. Shannon) > Queue pending message count can go

[jira] [Commented] (ARTEMIS-1793) Do not expose the _AMQ_ROUTING_TYPE header (at least) in STOMP

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

[jira] [Commented] (ARTEMIS-1793) Do not expose the _AMQ_ROUTING_TYPE header (at least) in STOMP

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

[jira] [Commented] (ARTEMIS-1793) Do not expose the _AMQ_ROUTING_TYPE header (at least) in STOMP

[ https://issues.apache.org/jira/browse/ARTEMIS-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442754#comment-16442754 ] ASF GitHub Bot commented on ARTEMIS-1793: - Github user asfgit closed the pull request at:

[jira] [Commented] (ARTEMIS-1813) DB2 should avoid Blob to append data

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

[jira] [Closed] (ARTEMIS-1784) JDBC NodeManager should just use DMBS clock

[ https://issues.apache.org/jira/browse/ARTEMIS-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro closed ARTEMIS-1784. Resolution: Fixed > JDBC NodeManager should just use DMBS clock >

[jira] [Commented] (ARTEMIS-1812) [core] Any Subsequent messages are lost after queue is emptied from slave broker (succ failover from master kill)

[ https://issues.apache.org/jira/browse/ARTEMIS-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442715#comment-16442715 ] ASF GitHub Bot commented on ARTEMIS-1812: - Github user clebertsuconic commented on the issue:

[jira] [Commented] (ARTEMIS-1812) [core] Any Subsequent messages are lost after queue is emptied from slave broker (succ failover from master kill)

[ https://issues.apache.org/jira/browse/ARTEMIS-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442714#comment-16442714 ] ASF GitHub Bot commented on ARTEMIS-1812: - Github user asfgit closed the pull request at:

[jira] [Commented] (ARTEMIS-1812) [core] Any Subsequent messages are lost after queue is emptied from slave broker (succ failover from master kill)

[ https://issues.apache.org/jira/browse/ARTEMIS-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442713#comment-16442713 ] ASF GitHub Bot commented on ARTEMIS-1812: - Github user jbertram commented on the issue:

[jira] [Commented] (ARTEMIS-1810) JDBCSequentialFileFactoryDriver should check <=0 read length

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

[jira] [Commented] (ARTEMIS-1285) Standby slave would not announce replication to master when the slave is down

[ https://issues.apache.org/jira/browse/ARTEMIS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442701#comment-16442701 ] Justin Bertram commented on ARTEMIS-1285: - bq. How should we proceed? Make a new ticket here?

[jira] [Commented] (ARTEMIS-1812) [core] Any Subsequent messages are lost after queue is emptied from slave broker (succ failover from master kill)

[ https://issues.apache.org/jira/browse/ARTEMIS-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442687#comment-16442687 ] ASF GitHub Bot commented on ARTEMIS-1812: - Github user clebertsuconic commented on the issue:

[jira] [Commented] (ARTEMIS-1812) [core] Any Subsequent messages are lost after queue is emptied from slave broker (succ failover from master kill)

[ https://issues.apache.org/jira/browse/ARTEMIS-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442684#comment-16442684 ] clebert suconic commented on ARTEMIS-1812: -- HA with auto-create is not a good idea...     I

[jira] [Closed] (ARTEMIS-1812) [core] Any Subsequent messages are lost after queue is emptied from slave broker (succ failover from master kill)

[ https://issues.apache.org/jira/browse/ARTEMIS-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1812. Resolution: Won't Fix > [core] Any Subsequent messages are lost after queue is emptied

[jira] [Commented] (ARTEMIS-1788) JDBC HA should use JDBC Network Timeout

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

[jira] [Commented] (ARTEMIS-1812) [core] Any Subsequent messages are lost after queue is emptied from slave broker (succ failover from master kill)

[ https://issues.apache.org/jira/browse/ARTEMIS-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442558#comment-16442558 ] ASF GitHub Bot commented on ARTEMIS-1812: - Github user clebertsuconic commented on a diff in the

[jira] [Commented] (ARTEMIS-1812) [core] Any Subsequent messages are lost after queue is emptied from slave broker (succ failover from master kill)

[ https://issues.apache.org/jira/browse/ARTEMIS-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442555#comment-16442555 ] ASF GitHub Bot commented on ARTEMIS-1812: - Github user clebertsuconic commented on a diff in the

[jira] [Commented] (ARTEMIS-1806) JDBC Connection leaks

[ https://issues.apache.org/jira/browse/ARTEMIS-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442543#comment-16442543 ] ASF GitHub Bot commented on ARTEMIS-1806: - Github user franz1981 closed the pull request at:

[jira] [Commented] (ARTEMIS-1653) Allow database tables to be created externally

[ https://issues.apache.org/jira/browse/ARTEMIS-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442542#comment-16442542 ] ASF GitHub Bot commented on ARTEMIS-1653: - Github user franz1981 closed the pull request at:

[jira] [Commented] (ARTEMIS-1784) JDBC NodeManager should just use DMBS clock

[ https://issues.apache.org/jira/browse/ARTEMIS-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442541#comment-16442541 ] ASF GitHub Bot commented on ARTEMIS-1784: - Github user asfgit closed the pull request at:

[jira] [Commented] (ARTEMIS-1784) JDBC NodeManager should just use DMBS clock

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

[jira] [Commented] (ARTEMIS-1653) Allow database tables to be created externally

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

[jira] [Commented] (ARTEMIS-1653) Allow database tables to be created externally

[ https://issues.apache.org/jira/browse/ARTEMIS-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442537#comment-16442537 ] ASF GitHub Bot commented on ARTEMIS-1653: - Github user clebertsuconic commented on the issue:

[jira] [Commented] (ARTEMIS-1653) Allow database tables to be created externally

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

[jira] [Commented] (ARTEMIS-1812) [core] Any Subsequent messages are lost after queue is emptied from slave broker (succ failover from master kill)

[ https://issues.apache.org/jira/browse/ARTEMIS-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442534#comment-16442534 ] ASF GitHub Bot commented on ARTEMIS-1812: - Github user stanlyDoge commented on the issue:

[jira] [Commented] (ARTEMIS-1806) JDBC Connection leaks

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

[jira] [Commented] (ARTEMIS-1806) JDBC Connection leaks

[ https://issues.apache.org/jira/browse/ARTEMIS-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442531#comment-16442531 ] ASF GitHub Bot commented on ARTEMIS-1806: - Github user clebertsuconic commented on the issue:

[jira] [Commented] (ARTEMIS-1538) trustAll is ignored when specified in the connectionFactory URI

[ https://issues.apache.org/jira/browse/ARTEMIS-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442533#comment-16442533 ] Jiri Daněk commented on ARTEMIS-1538: - I see now where I confused you. I wrote "I noticed that the

[jira] [Commented] (ARTEMIS-1814) Try Original Connector when Live and Backup are both restarted

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

[jira] [Commented] (ARTEMIS-1814) Try Original Connector when Live and Backup are both restarted

[ https://issues.apache.org/jira/browse/ARTEMIS-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442524#comment-16442524 ] ASF GitHub Bot commented on ARTEMIS-1814: - Github user asfgit closed the pull request at:

[jira] [Commented] (ARTEMIS-1784) JDBC NodeManager should just use DMBS clock

[ https://issues.apache.org/jira/browse/ARTEMIS-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442519#comment-16442519 ] ASF GitHub Bot commented on ARTEMIS-1784: - Github user clebertsuconic commented on the issue:

[jira] [Commented] (ARTEMIS-1806) JDBC Connection leaks

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

[jira] [Commented] (AMQ-6947) Queue pending message count can go negative on duplicates

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

[jira] [Commented] (AMQ-6947) Queue pending message count can go negative on duplicates

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

[jira] [Commented] (ARTEMIS-1653) Allow database tables to be created externally

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

[jira] [Updated] (ARTEMIS-1784) JDBC NodeManager should just use DMBS clock

[ https://issues.apache.org/jira/browse/ARTEMIS-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1784: - Description: JdbcNodeManager rely on the correct synchronization between broker

[jira] [Updated] (ARTEMIS-1784) JDBC NodeManager should just use DMBS clock

[ https://issues.apache.org/jira/browse/ARTEMIS-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1784: - Description: It avoid using the system clock to perform the locks logic by using the

[jira] [Closed] (ARTEMIS-1813) DB2 should avoid Blob to append data

[ https://issues.apache.org/jira/browse/ARTEMIS-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro closed ARTEMIS-1813. Resolution: Fixed > DB2 should avoid Blob to append data >

[jira] [Commented] (ARTEMIS-1784) JDBC NodeManager should just use DMBS clock

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

[jira] [Commented] (ARTEMIS-1751) Artemis backup servers hawtio web management doesn't come online

[ https://issues.apache.org/jira/browse/ARTEMIS-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442197#comment-16442197 ] Catalin Alexandru Zamfir commented on ARTEMIS-1751: --- Hello, We have a

[jira] [Commented] (ARTEMIS-1737) When live-slave fails-back to master, it turns off everything down, even its console

[ https://issues.apache.org/jira/browse/ARTEMIS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442198#comment-16442198 ] Catalin Alexandru Zamfir commented on ARTEMIS-1737: --- Hello, We have a

[jira] [Comment Edited] (ARTEMIS-1285) Standby slave would not announce replication to master when the slave is down

[ https://issues.apache.org/jira/browse/ARTEMIS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442092#comment-16442092 ] Catalin Alexandru Zamfir edited comment on ARTEMIS-1285 at 4/18/18 9:21 AM:

[jira] [Comment Edited] (ARTEMIS-1285) Standby slave would not announce replication to master when the slave is down

[ https://issues.apache.org/jira/browse/ARTEMIS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442174#comment-16442174 ] Catalin Alexandru Zamfir edited comment on ARTEMIS-1285 at 4/18/18 9:20 AM:

[jira] [Comment Edited] (ARTEMIS-1285) Standby slave would not announce replication to master when the slave is down

[ https://issues.apache.org/jira/browse/ARTEMIS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442174#comment-16442174 ] Catalin Alexandru Zamfir edited comment on ARTEMIS-1285 at 4/18/18 9:19 AM:

[jira] [Commented] (ARTEMIS-1285) Standby slave would not announce replication to master when the slave is down

[ https://issues.apache.org/jira/browse/ARTEMIS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442174#comment-16442174 ] Catalin Alexandru Zamfir commented on ARTEMIS-1285: --- Ok, so we have 2 issues here: *

[jira] [Commented] (ARTEMIS-1285) Standby slave would not announce replication to master when the slave is down

[ https://issues.apache.org/jira/browse/ARTEMIS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442128#comment-16442128 ] Catalin Alexandru Zamfir commented on ARTEMIS-1285: --- Hello, Confirming. The Hawtio

[jira] [Commented] (ARTEMIS-1285) Standby slave would not announce replication to master when the slave is down

[ https://issues.apache.org/jira/browse/ARTEMIS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442092#comment-16442092 ] Catalin Alexandru Zamfir commented on ARTEMIS-1285: --- Further information, this

[jira] [Commented] (ARTEMIS-1285) Standby slave would not announce replication to master when the slave is down

[ https://issues.apache.org/jira/browse/ARTEMIS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442083#comment-16442083 ] Catalin Alexandru Zamfir commented on ARTEMIS-1285: --- Hello,  [~jbertram] here's the

[jira] [Commented] (ARTEMIS-1285) Standby slave would not announce replication to master when the slave is down

[ https://issues.apache.org/jira/browse/ARTEMIS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442018#comment-16442018 ] Denis Volkov commented on ARTEMIS-1285: --- > because when the connection between the live and active

[jira] [Commented] (ARTEMIS-1815) add "exclusive-queue" example

[ https://issues.apache.org/jira/browse/ARTEMIS-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442003#comment-16442003 ] ASF GitHub Bot commented on ARTEMIS-1815: - Github user pgfox commented on the issue:

[jira] [Commented] (AMQ-6937) Recycling TCP/IP stack on z/OS causes an infinite error loop in transport server

[ https://issues.apache.org/jira/browse/AMQ-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441979#comment-16441979 ] Tomas Pavelka commented on AMQ-6937: Thanks, I see it now. The number of open sockets will be capped by