[jira] [Commented] (ARTEMIS-392) Artemis NettyConnetor 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=15137188#comment-15137188 ] ASF subversion and git services commented on ARTEMIS-392: - Commit

[jira] [Commented] (ARTEMIS-392) Artemis NettyConnetor 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=15137187#comment-15137187 ] ASF subversion and git services commented on ARTEMIS-392: - Commit

[jira] [Commented] (AMQ-6153) Toggle the TCP transport's ability to size a socket's read and write buffer

[ https://issues.apache.org/jira/browse/AMQ-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15137116#comment-15137116 ] Gary Tully commented on AMQ-6153: - this may be a case where using a 0 or -1 value works. Both are illegal

[jira] [Updated] (AMQ-6153) Toggle the TCP transport's ability to size a socket's read and write buffer

[ https://issues.apache.org/jira/browse/AMQ-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-6153: Fix Version/s: (was: 5.13.1) 5.13.2 5.14.0

[jira] [Commented] (ARTEMIS-365) [Artemis Testsuite] AddressControlTest#testGetNumberOfPages fails

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

[jira] [Created] (ARTEMIS-394) Use a classLoading operation to load the JDBC Driver

clebert suconic created ARTEMIS-394: --- Summary: Use a classLoading operation to load the JDBC Driver Key: ARTEMIS-394 URL: https://issues.apache.org/jira/browse/ARTEMIS-394 Project: ActiveMQ Artemis

[jira] [Commented] (AMQ-6153) Toggle the TCP transport's ability to size a socket's read and write buffer

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

[jira] [Commented] (AMQ-6153) Toggle the TCP transport's ability to size a socket's read and write buffer

[ https://issues.apache.org/jira/browse/AMQ-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15137133#comment-15137133 ] Christopher L. Shannon commented on AMQ-6153: - Agreed, I'm just going to switch the logic

[jira] [Commented] (AMQ-6153) Toggle the TCP transport's ability to size a socket's read and write buffer

[ https://issues.apache.org/jira/browse/AMQ-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15137236#comment-15137236 ] Paul Gale commented on AMQ-6153: Any unit tests for this patch? There's an edge case that can still creep

[jira] [Created] (ARTEMIS-393) Server logs message with queue deploy even when topic is being deployed.

Andy Taylor created ARTEMIS-393: --- Summary: Server logs message with queue deploy even when topic is being deployed. Key: ARTEMIS-393 URL: https://issues.apache.org/jira/browse/ARTEMIS-393 Project:

[jira] [Commented] (ARTEMIS-393) Server logs message with queue deploy even when topic is being deployed.

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

[jira] [Resolved] (ARTEMIS-365) [Artemis Testsuite] AddressControlTest#testGetNumberOfPages fails

[ https://issues.apache.org/jira/browse/ARTEMIS-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erich Duda resolved ARTEMIS-365. Resolution: Fixed > [Artemis Testsuite] AddressControlTest#testGetNumberOfPages fails >

[jira] [Resolved] (ARTEMIS-364) [Artemis Testsuite] PagingTest#testPagingDifferentSizes fails

[ https://issues.apache.org/jira/browse/ARTEMIS-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erich Duda resolved ARTEMIS-364. Resolution: Fixed > [Artemis Testsuite] PagingTest#testPagingDifferentSizes fails >

[jira] [Commented] (ARTEMIS-393) Server logs message with queue deploy even when topic is being deployed.

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

[jira] [Assigned] (AMQ-6153) Toggle the TCP transport's ability to size a socket's read and write buffer

[ https://issues.apache.org/jira/browse/AMQ-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon reassigned AMQ-6153: --- Assignee: Christopher L. Shannon > Toggle the TCP transport's ability to size

[jira] [Reopened] (ARTEMIS-364) [Artemis Testsuite] PagingTest#testPagingDifferentSizes fails

[ https://issues.apache.org/jira/browse/ARTEMIS-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erich Duda reopened ARTEMIS-364: The test fails on 32-bit machines. > [Artemis Testsuite] PagingTest#testPagingDifferentSizes fails >

[jira] [Updated] (AMQ-6162) DLQ'd message does not get DLQ'd again until broker restart

[ https://issues.apache.org/jira/browse/AMQ-6162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jo Vandermeeren updated AMQ-6162: - Priority: Critical (was: Major) Regression: Regression Component/s: Broker > DLQ'd

[jira] [Commented] (ARTEMIS-365) [Artemis Testsuite] AddressControlTest#testGetNumberOfPages fails

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

[jira] [Reopened] (ARTEMIS-365) [Artemis Testsuite] AddressControlTest#testGetNumberOfPages fails

[ https://issues.apache.org/jira/browse/ARTEMIS-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erich Duda reopened ARTEMIS-365: The test still fails on 32 bit machines. > [Artemis Testsuite]

[jira] [Commented] (ARTEMIS-364) [Artemis Testsuite] PagingTest#testPagingDifferentSizes fails

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

[jira] [Commented] (ARTEMIS-393) Server logs message with queue deploy even when topic is being deployed.

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

[jira] [Commented] (AMQ-6153) Toggle the TCP transport's ability to size a socket's read and write buffer

[ https://issues.apache.org/jira/browse/AMQ-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15137265#comment-15137265 ] Christopher L. Shannon commented on AMQ-6153: - Indeed it looks like setting it using

[jira] [Commented] (AMQ-5297) PooledSession with lots of consumers can fail to start fully

[ https://issues.apache.org/jira/browse/AMQ-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15137382#comment-15137382 ] Tim Kieschnick commented on AMQ-5297: - Was this ever resolved or worked around? > PooledSession with

[jira] [Commented] (ARTEMIS-365) [Artemis Testsuite] AddressControlTest#testGetNumberOfPages fails

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

[jira] [Commented] (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:comment-tabpanel=15137740#comment-15137740 ] ASF GitHub Bot commented on ARTEMIS-388: GitHub user jbertram opened a pull request:

[jira] [Commented] (AMQ-5297) PooledSession with lots of consumers can fail to start fully

[ https://issues.apache.org/jira/browse/AMQ-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15137693#comment-15137693 ] Sam hendley commented on AMQ-5297: -- This still occurs for us on 5.12 in some cases. I think it is related

[jira] [Comment Edited] (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=15137546#comment-15137546 ] Justin Bertram edited comment on ARTEMIS-391 at 2/8/16 9:36 PM: Adding

[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=15137546#comment-15137546 ] Justin Bertram commented on ARTEMIS-391: Adding the logging here is easy. However, I'm not sure

[jira] [Commented] (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:comment-tabpanel=15137860#comment-15137860 ] ASF GitHub Bot commented on ARTEMIS-388: Github user clebertsuconic commented on the pull

[jira] [Commented] (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:comment-tabpanel=15137857#comment-15137857 ] ASF GitHub Bot commented on ARTEMIS-388: Github user mikehearn commented on the pull request:

[jira] [Commented] (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:comment-tabpanel=15137946#comment-15137946 ] ASF GitHub Bot commented on ARTEMIS-388: Github user clebertsuconic commented on the pull

[jira] [Commented] (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:comment-tabpanel=15137976#comment-15137976 ] ASF GitHub Bot commented on ARTEMIS-388: Github user jbertram commented on the pull request: