[jira] [Updated] (ARTEMIS-168) Pluggable ACL Hierarchies
[ https://issues.apache.org/jira/browse/ARTEMIS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-168: --- Fix Version/s: (was: 1.3.0) 1.1.1 > Pluggable ACL Hierarchies > - > > Key: ARTEMIS-168 > URL: https://issues.apache.org/jira/browse/ARTEMIS-168 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: clebert suconic >Assignee: Justin Bertram >Priority: Critical > Fix For: 1.1.1 > > > ActiveMQ5 has a way to plug the security-settings into LDAP | Files, or a > Pluggable ACL implementation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ARTEMIS-255) Make failover timeout for non-blocking sends configurable
[ https://issues.apache.org/jira/browse/ARTEMIS-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-255. Resolution: Fixed > Make failover timeout for non-blocking sends configurable > - > > Key: ARTEMIS-255 > URL: https://issues.apache.org/jira/browse/ARTEMIS-255 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 1.1.0 >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 1.1.1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ARTEMIS-289) Potential ConcurrentModificationException when closing connections
[ https://issues.apache.org/jira/browse/ARTEMIS-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-289. Resolution: Fixed > Potential ConcurrentModificationException when closing connections > -- > > Key: ARTEMIS-289 > URL: https://issues.apache.org/jira/browse/ARTEMIS-289 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 1.1.0 >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 1.1.1 > > > org.apache.activemq.artemis.core.server.impl.QueueImpl#getConsumers returns > the actual Set of consumers, but if another thread modifies this collection > while the caller loops through the Set then a ConcurrentModificationException > will be thrown. This is possible particularly in management operations that > work on the Set of consumers like > org.apache.activemq.artemis.api.core.management.ActiveMQServerControl#closeConsumerConnectionsForAddress. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-289) Potential ConcurrentModificationException when closing connections
[ https://issues.apache.org/jira/browse/ARTEMIS-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981190#comment-14981190 ] ASF subversion and git services commented on ARTEMIS-289: - Commit 43b421a5884280900f6bae740c07a1eee8736f1e in activemq-artemis's branch refs/heads/master from [~jbertram] [ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=43b421a ] ARTEMIS-289 potential ConcurrentModificationException > Potential ConcurrentModificationException when closing connections > -- > > Key: ARTEMIS-289 > URL: https://issues.apache.org/jira/browse/ARTEMIS-289 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 1.1.0 >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 1.1.1 > > > org.apache.activemq.artemis.core.server.impl.QueueImpl#getConsumers returns > the actual Set of consumers, but if another thread modifies this collection > while the caller loops through the Set then a ConcurrentModificationException > will be thrown. This is possible particularly in management operations that > work on the Set of consumers like > org.apache.activemq.artemis.api.core.management.ActiveMQServerControl#closeConsumerConnectionsForAddress. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-289) Potential ConcurrentModificationException when closing connections
[ https://issues.apache.org/jira/browse/ARTEMIS-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981191#comment-14981191 ] ASF GitHub Bot commented on ARTEMIS-289: Github user asfgit closed the pull request at: https://github.com/apache/activemq-artemis/pull/224 > Potential ConcurrentModificationException when closing connections > -- > > Key: ARTEMIS-289 > URL: https://issues.apache.org/jira/browse/ARTEMIS-289 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 1.1.0 >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 1.1.1 > > > org.apache.activemq.artemis.core.server.impl.QueueImpl#getConsumers returns > the actual Set of consumers, but if another thread modifies this collection > while the caller loops through the Set then a ConcurrentModificationException > will be thrown. This is possible particularly in management operations that > work on the Set of consumers like > org.apache.activemq.artemis.api.core.management.ActiveMQServerControl#closeConsumerConnectionsForAddress. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ARTEMIS-289) Potential ConcurrentModificationException when closing connections
[ https://issues.apache.org/jira/browse/ARTEMIS-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-289: --- Affects Version/s: 1.1.0 > Potential ConcurrentModificationException when closing connections > -- > > Key: ARTEMIS-289 > URL: https://issues.apache.org/jira/browse/ARTEMIS-289 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 1.1.0 >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 1.1.1 > > > org.apache.activemq.artemis.core.server.impl.QueueImpl#getConsumers returns > the actual Set of consumers, but if another thread modifies this collection > while the caller loops through the Set then a ConcurrentModificationException > will be thrown. This is possible particularly in management operations that > work on the Set of consumers like > org.apache.activemq.artemis.api.core.management.ActiveMQServerControl#closeConsumerConnectionsForAddress. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ARTEMIS-289) Potential ConcurrentModificationException when closing connections
[ https://issues.apache.org/jira/browse/ARTEMIS-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-289: --- Description: org.apache.activemq.artemis.core.server.impl.QueueImpl#getConsumers returns the actual Set of consumers, but if another thread modifies this collection while the caller loops through the Set then a ConcurrentModificationException will be thrown. This is possible particularly in management operations that work on the Set of consumers like org.apache.activemq.artemis.api.core.management.ActiveMQServerControl#closeConsumerConnectionsForAddress. (was: org.apache.activemq.artemis.core.server.impl.QueueImpl#getConsumers returns the actual Set of consumers, but if another thread modifies this collection while the caller loops through the Set then a ConcurrentModificationException will be thrown.) > Potential ConcurrentModificationException when closing connections > -- > > Key: ARTEMIS-289 > URL: https://issues.apache.org/jira/browse/ARTEMIS-289 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 1.1.0 >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 1.1.1 > > > org.apache.activemq.artemis.core.server.impl.QueueImpl#getConsumers returns > the actual Set of consumers, but if another thread modifies this collection > while the caller loops through the Set then a ConcurrentModificationException > will be thrown. This is possible particularly in management operations that > work on the Set of consumers like > org.apache.activemq.artemis.api.core.management.ActiveMQServerControl#closeConsumerConnectionsForAddress. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-289) Potential ConcurrentModificationException when closing connections
[ https://issues.apache.org/jira/browse/ARTEMIS-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981021#comment-14981021 ] ASF GitHub Bot commented on ARTEMIS-289: GitHub user jbertram opened a pull request: https://github.com/apache/activemq-artemis/pull/224 ARTEMIS-289 potential ConcurrentModificationException You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-artemis master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/224.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #224 commit 43b421a5884280900f6bae740c07a1eee8736f1e Author: jbertram Date: 2015-10-29T18:41:08Z ARTEMIS-289 potential ConcurrentModificationException > Potential ConcurrentModificationException when closing connections > -- > > Key: ARTEMIS-289 > URL: https://issues.apache.org/jira/browse/ARTEMIS-289 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 1.1.1 > > > org.apache.activemq.artemis.core.server.impl.QueueImpl#getConsumers returns > the actual Set of consumers, but if another thread modifies this collection > while the caller loops through the Set then a ConcurrentModificationException > will be thrown. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ARTEMIS-289) Potential ConcurrentModificationException when closing connections
Justin Bertram created ARTEMIS-289: -- Summary: Potential ConcurrentModificationException when closing connections Key: ARTEMIS-289 URL: https://issues.apache.org/jira/browse/ARTEMIS-289 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Justin Bertram Assignee: Justin Bertram Fix For: 1.1.1 org.apache.activemq.artemis.core.server.impl.QueueImpl#getConsumers returns the actual Set of consumers, but if another thread modifies this collection while the caller loops through the Set then a ConcurrentModificationException will be thrown. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (ARTEMIS-288) Disconnecting client results in log warnings
[ https://issues.apache.org/jira/browse/ARTEMIS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-288. --- Resolution: Fixed > Disconnecting client results in log warnings > > > Key: ARTEMIS-288 > URL: https://issues.apache.org/jira/browse/ARTEMIS-288 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 1.0.0, 1.1.0 >Reporter: Martyn Taylor > Fix For: 1.2.0, 1.1.1 > > > When the server sends a disconnect to a client. The client logs a bunch of > warning messages, and then an error. > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-2 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-18 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-4 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-13 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-14 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-11 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-12 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-7 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-17 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-9 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-19 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-10 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-21 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-22 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-16 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ARTEMIS-288) Disconnecting client results in log warnings
[ https://issues.apache.org/jira/browse/ARTEMIS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-288: Affects Version/s: 1.0.0 1.1.0 Fix Version/s: 1.1.1 1.2.0 > Disconnecting client results in log warnings > > > Key: ARTEMIS-288 > URL: https://issues.apache.org/jira/browse/ARTEMIS-288 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 1.0.0, 1.1.0 >Reporter: Martyn Taylor > Fix For: 1.2.0, 1.1.1 > > > When the server sends a disconnect to a client. The client logs a bunch of > warning messages, and then an error. > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-2 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-18 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-4 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-13 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-14 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-11 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-12 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-7 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-17 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-9 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-19 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-10 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-21 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-22 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-16 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-288) Disconnecting client results in log warnings
[ https://issues.apache.org/jira/browse/ARTEMIS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980640#comment-14980640 ] ASF GitHub Bot commented on ARTEMIS-288: Github user asfgit closed the pull request at: https://github.com/apache/activemq-artemis/pull/223 > Disconnecting client results in log warnings > > > Key: ARTEMIS-288 > URL: https://issues.apache.org/jira/browse/ARTEMIS-288 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Martyn Taylor > > When the server sends a disconnect to a client. The client logs a bunch of > warning messages, and then an error. > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-2 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-18 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-4 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-13 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-14 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-11 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-12 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-7 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-17 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-9 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-19 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-10 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-21 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-22 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-16 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-288) Disconnecting client results in log warnings
[ https://issues.apache.org/jira/browse/ARTEMIS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980639#comment-14980639 ] ASF subversion and git services commented on ARTEMIS-288: - Commit 26898e4663ce00468ec9cebf00c57d72658dd191 in activemq-artemis's branch refs/heads/master from [~martyntaylor] [ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=26898e4 ] ARTEMIS-288 Start close method in separate executor When server sends disconnect to the client, the ClientSession schedules a close task on it's ordered executor. Once the close method starts it's waits to check to see if all jobs in it's executor has completed. To do this it adds a job to it's ordered executor, once it is run it knows there is nothing more to do and thus is ready to close. However, this causes a deadlock as both jobs are running in the ordered executor and thus are both waiting on each other. The close eventually timesout which is why we see the logs as reported in the JIRA. This commit runs the close method in it's own ordered executor, thus preventing the two jobs blocking each other. > Disconnecting client results in log warnings > > > Key: ARTEMIS-288 > URL: https://issues.apache.org/jira/browse/ARTEMIS-288 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Martyn Taylor > > When the server sends a disconnect to a client. The client logs a bunch of > warning messages, and then an error. > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-2 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-18 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-4 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-13 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-14 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-11 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-12 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-7 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-17 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-9 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-19 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-10 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-21 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-22 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-16 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-288) Disconnecting client results in log warnings
[ https://issues.apache.org/jira/browse/ARTEMIS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980603#comment-14980603 ] ASF GitHub Bot commented on ARTEMIS-288: GitHub user mtaylor opened a pull request: https://github.com/apache/activemq-artemis/pull/223 ARTEMIS-288 Start close method in separate executor When server sends disconnect to the client, the ClientSession schedules a close task on it's ordered executor. Once the close method starts it's waits to check to see if all jobs in it's executor has completed. To do this it adds a job to it's ordered executor, once it is run it knows there is nothing more to do and thus is ready to close. However, this causes a deadlock as both jobs are running in the ordered executor and thus are both waiting on each other. The close eventually timesout which is why we see the logs as reported in the JIRA. This commit runs the close method in it's own ordered executor, thus preventing the two jobs blocking each other. You can merge this pull request into a Git repository by running: $ git pull https://github.com/mtaylor/activemq-artemis ARTEMIS-288-fix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/223.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #223 commit 26898e4663ce00468ec9cebf00c57d72658dd191 Author: Martyn Taylor Date: 2015-10-29T12:50:08Z ARTEMIS-288 Start close method in separate executor When server sends disconnect to the client, the ClientSession schedules a close task on it's ordered executor. Once the close method starts it's waits to check to see if all jobs in it's executor has completed. To do this it adds a job to it's ordered executor, once it is run it knows there is nothing more to do and thus is ready to close. However, this causes a deadlock as both jobs are running in the ordered executor and thus are both waiting on each other. The close eventually timesout which is why we see the logs as reported in the JIRA. This commit runs the close method in it's own ordered executor, thus preventing the two jobs blocking each other. > Disconnecting client results in log warnings > > > Key: ARTEMIS-288 > URL: https://issues.apache.org/jira/browse/ARTEMIS-288 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Martyn Taylor > > When the server sends a disconnect to a client. The client logs a bunch of > warning messages, and then an error. > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-2 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-18 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-4 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-13 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-14 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-11 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-12 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-7 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-17 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-9 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-19 > (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for > handler to complete processing > 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thr
[jira] [Commented] (AMQ-5876) improve performance of TextFileCertificateLoginModule when many entries are in the "textfiledn.user " file
[
https://issues.apache.org/jira/browse/AMQ-5876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980499#comment-14980499
]
ASF subversion and git services commented on AMQ-5876:
--
Commit 8d63083dfff064efadbe99a66deeedef829e519e in activemq's branch
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=8d63083 ]
https://issues.apache.org/jira/browse/AMQ-5876 - load groups properties into
per user set once also to avoid parse per login attempt
> improve performance of TextFileCertificateLoginModule when many entries are
> in the "textfiledn.user " file
> --
>
> Key: AMQ-5876
> URL: https://issues.apache.org/jira/browse/AMQ-5876
> Project: ActiveMQ
> Issue Type: Improvement
> Components: jaas, security
>Affects Versions: 5.11.1
>Reporter: Gary Tully
>Assignee: Gary Tully
> Labels: jaas
> Fix For: 5.12.0
>
>
> With a large number of entries ( 200,000 ) in the
> "org.apache.activemq.jaas.textfiledn.user" file the performance seemed to
> degrade.
> To demonstrate the performance difference;
> {code}
> 1) for 100 entries and calling initialize,login(),commit 10 times - Time
> taken is 73 miliseconds
> 2) for 200,000 entries and calling initialize,login(),commit 10 times - Time
> taken is 5020 miliseconds
> {code}
> Suggested improvements:
> - avoid loading the org.apache.activemq.jaas.textfiledn.user file each time
> - in PropertiesLoginModule.java, the file is only read when it changes, using
> the file modification time.
> - avoid iterating through the Properties object, using a Map instead to
> retrieve the userName
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ARTEMIS-286) Upgrade Netty to version 4.0.32.Final
[ https://issues.apache.org/jira/browse/ARTEMIS-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980405#comment-14980405 ] ASF GitHub Bot commented on ARTEMIS-286: Github user asfgit closed the pull request at: https://github.com/apache/activemq-artemis/pull/221 > Upgrade Netty to version 4.0.32.Final > - > > Key: ARTEMIS-286 > URL: https://issues.apache.org/jira/browse/ARTEMIS-286 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Andrea Cosentino >Priority: Minor > Fix For: 1.2.0 > > > Latest release is 4.0.32.Final, Artemis actually is using 4.0.30.Final -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-286) Upgrade Netty to version 4.0.32.Final
[ https://issues.apache.org/jira/browse/ARTEMIS-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980404#comment-14980404 ] ASF subversion and git services commented on ARTEMIS-286: - Commit cafeaab8de249a8d6a2031e3d4e9dccd8979b35b in activemq-artemis's branch refs/heads/master from [~ancosen] [ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=cafeaab ] ARTEMIS-286 Upgrade Netty to version 4.0.32.Final > Upgrade Netty to version 4.0.32.Final > - > > Key: ARTEMIS-286 > URL: https://issues.apache.org/jira/browse/ARTEMIS-286 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Andrea Cosentino >Priority: Minor > Fix For: 1.2.0 > > > Latest release is 4.0.32.Final, Artemis actually is using 4.0.30.Final -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-287) [Artemis Testsuite] PagingTest#testDeleteQueueRestart fails on slower machines
[
https://issues.apache.org/jira/browse/ARTEMIS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980400#comment-14980400
]
ASF GitHub Bot commented on ARTEMIS-287:
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/222
> [Artemis Testsuite] PagingTest#testDeleteQueueRestart fails on slower machines
> --
>
> Key: ARTEMIS-287
> URL: https://issues.apache.org/jira/browse/ARTEMIS-287
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Erich Duda
>
> {code}
> long timeout = System.currentTimeMillis() + 5000;
> // I want the buffer full to make sure there are pending messages on the
> server's side
> while (System.currentTimeMillis() < timeout && cons.getBufferSize() < 1000 &&
> cons2.getBufferSize() < 1000) {
> System.out.println("cons1 buffer = " + cons.getBufferSize() + ", cons2
> buffer = " + cons2.getBufferSize());
> Thread.sleep(100);
> }
> {code}
> On slower machines the 5 seconds timeout is too short.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ARTEMIS-286) Upgrade Netty to version 4.0.32.Final
[ https://issues.apache.org/jira/browse/ARTEMIS-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980403#comment-14980403 ] ASF GitHub Bot commented on ARTEMIS-286: Github user clebertsuconic commented on the pull request: https://github.com/apache/activemq-artemis/pull/221#issuecomment-152177436 @oscerd let us know how we can help you on contributing. IRC @ freenode is a good channel to talk real time... or the dev list > Upgrade Netty to version 4.0.32.Final > - > > Key: ARTEMIS-286 > URL: https://issues.apache.org/jira/browse/ARTEMIS-286 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Andrea Cosentino >Priority: Minor > Fix For: 1.2.0 > > > Latest release is 4.0.32.Final, Artemis actually is using 4.0.30.Final -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-287) [Artemis Testsuite] PagingTest#testDeleteQueueRestart fails on slower machines
[
https://issues.apache.org/jira/browse/ARTEMIS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980399#comment-14980399
]
ASF subversion and git services commented on ARTEMIS-287:
-
Commit 0007772b135d398f15a2e49dcf6e47af2c19a0aa in activemq-artemis's branch
refs/heads/master from [~eduda]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=0007772 ]
ARTEMIS-287 [Artemis Testsuite] PagingTest#testDeleteQueueRestart fails on
slower machines
> [Artemis Testsuite] PagingTest#testDeleteQueueRestart fails on slower machines
> --
>
> Key: ARTEMIS-287
> URL: https://issues.apache.org/jira/browse/ARTEMIS-287
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Erich Duda
>
> {code}
> long timeout = System.currentTimeMillis() + 5000;
> // I want the buffer full to make sure there are pending messages on the
> server's side
> while (System.currentTimeMillis() < timeout && cons.getBufferSize() < 1000 &&
> cons2.getBufferSize() < 1000) {
> System.out.println("cons1 buffer = " + cons.getBufferSize() + ", cons2
> buffer = " + cons2.getBufferSize());
> Thread.sleep(100);
> }
> {code}
> On slower machines the 5 seconds timeout is too short.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ARTEMIS-288) Disconnecting client results in log warnings
Martyn Taylor created ARTEMIS-288: - Summary: Disconnecting client results in log warnings Key: ARTEMIS-288 URL: https://issues.apache.org/jira/browse/ARTEMIS-288 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Martyn Taylor When the server sends a disconnect to a client. The client logs a bunch of warning messages, and then an error. 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-2 (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for handler to complete processing 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-18 (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for handler to complete processing 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-4 (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for handler to complete processing 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-13 (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for handler to complete processing 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-14 (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for handler to complete processing 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-11 (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for handler to complete processing 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-12 (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for handler to complete processing 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-7 (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for handler to complete processing 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-17 (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for handler to complete processing 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-9 (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for handler to complete processing 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-19 (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for handler to complete processing 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-10 (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for handler to complete processing 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-21 (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for handler to complete processing 11:18:54,630 WARN [org.apache.activemq.artemis.core.client] (Thread-22 (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for handler to complete processing 11:18:54,631 WARN [org.apache.activemq.artemis.core.client] (Thread-16 (ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for handler to complete processing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-287) [Artemis Testsuite] PagingTest#testDeleteQueueRestart fails on slower machines
[
https://issues.apache.org/jira/browse/ARTEMIS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980219#comment-14980219
]
ASF GitHub Bot commented on ARTEMIS-287:
GitHub user dudaerich opened a pull request:
https://github.com/apache/activemq-artemis/pull/222
ARTEMIS-287 PagingTest#testDeleteQueueRestart fails on slower machines
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dudaerich/activemq-artemis ARTEMIS-287
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/222.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #222
commit 0007772b135d398f15a2e49dcf6e47af2c19a0aa
Author: Erich Duda
Date: 2015-10-29T10:27:26Z
ARTEMIS-287 [Artemis Testsuite] PagingTest#testDeleteQueueRestart fails on
slower machines
> [Artemis Testsuite] PagingTest#testDeleteQueueRestart fails on slower machines
> --
>
> Key: ARTEMIS-287
> URL: https://issues.apache.org/jira/browse/ARTEMIS-287
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Erich Duda
>
> {code}
> long timeout = System.currentTimeMillis() + 5000;
> // I want the buffer full to make sure there are pending messages on the
> server's side
> while (System.currentTimeMillis() < timeout && cons.getBufferSize() < 1000 &&
> cons2.getBufferSize() < 1000) {
> System.out.println("cons1 buffer = " + cons.getBufferSize() + ", cons2
> buffer = " + cons2.getBufferSize());
> Thread.sleep(100);
> }
> {code}
> On slower machines the 5 seconds timeout is too short.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ARTEMIS-287) [Artemis Testsuite] PagingTest#testDeleteQueueRestart fails on slower machines
Erich Duda created ARTEMIS-287:
--
Summary: [Artemis Testsuite] PagingTest#testDeleteQueueRestart
fails on slower machines
Key: ARTEMIS-287
URL: https://issues.apache.org/jira/browse/ARTEMIS-287
Project: ActiveMQ Artemis
Issue Type: Bug
Reporter: Erich Duda
{code}
long timeout = System.currentTimeMillis() + 5000;
// I want the buffer full to make sure there are pending messages on the
server's side
while (System.currentTimeMillis() < timeout && cons.getBufferSize() < 1000 &&
cons2.getBufferSize() < 1000) {
System.out.println("cons1 buffer = " + cons.getBufferSize() + ", cons2
buffer = " + cons2.getBufferSize());
Thread.sleep(100);
}
{code}
On slower machines the 5 seconds timeout is too short.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
