[jira] [Commented] (ARTEMIS-297) Handle exceptions during server stop

2015-11-05 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14991884#comment-14991884
 ] 

ASF GitHub Bot commented on ARTEMIS-297:


Github user asfgit closed the pull request at:

https://github.com/apache/activemq-artemis/pull/237


> Handle exceptions during server stop
> 
>
> Key: ARTEMIS-297
> URL: https://issues.apache.org/jira/browse/ARTEMIS-297
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Martyn Taylor
>
> The server stop method is quite brittle.  If any component throws an 
> exception during shutdown, the exception is thrown and the method exits.  
> Instead the stop method on the server should be able to handle such 
> exceptions and continue shutting down all components and eventually stop the 
> ExecutorServices.  Failure to do so can lead to leaking threads.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARTEMIS-299) Improve performance of TextFileCertificateLoginModule when many entries in user file

2015-11-05 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14991843#comment-14991843
 ] 

ASF GitHub Bot commented on ARTEMIS-299:


GitHub user jbertram opened a pull request:

https://github.com/apache/activemq-artemis/pull/239

ARTEMIS-299 file-based login module performance

This is based on improvements made in ActiveMQ 5.x. See more at
https://issues.apache.org/jira/browse/AMQ-5876.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-299

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/239.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 #239


commit c51009dddc213875fc301afe9ea2d2564bf55ff3
Author: jbertram 
Date:   2015-11-04T22:38:40Z

ARTEMIS-299 file-based login module performance

This is based on improvements made in ActiveMQ 5.x. See more at
https://issues.apache.org/jira/browse/AMQ-5876.




> Improve performance of TextFileCertificateLoginModule when many entries in 
> user file
> 
>
> Key: ARTEMIS-299
> URL: https://issues.apache.org/jira/browse/ARTEMIS-299
> 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] [Created] (ARTEMIS-300) Make JAAS properties login module default and deprecate "basic"

2015-11-05 Thread Justin Bertram (JIRA) 
Justin Bertram created ARTEMIS-300:
--

 Summary: Make JAAS properties login module default and deprecate 
"basic"
 Key: ARTEMIS-300
 URL: https://issues.apache.org/jira/browse/ARTEMIS-300
 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] [Comment Edited] (AMQ-5934) ActiveMQ durable topic subscribers not able to receive new messages after running for awhile

2015-11-05 Thread Devesh Arora (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMQ-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14991745#comment-14991745
 ] 

Devesh Arora edited comment on AMQ-5934 at 11/5/15 3:12 PM:


[~gtully] thank you very much for your feedback - you're absolutely right.  I 
wasn't sure if it was intentional or not to have multiple threads access that 
map. Now that I know, I'm going to dig a little further to figure out which 
threads are trying to access it. 


was (Author: darora@gmail.com):
[~gtully] thank you very much for your feedback - you're absolutely right. I'm 
going to dig a little further to figure out which threads are trying to access 
this map. 

> ActiveMQ durable topic subscribers not able to receive new messages after 
> running for awhile
> 
>
> Key: AMQ-5934
> URL: https://issues.apache.org/jira/browse/AMQ-5934
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.10.2, 5.11.1
> Environment: ActiveMQ 5.10.2 broker and a topic subscriber with 
> ActiveMQ 5.10 client libraries.
>Reporter: Eric X
>Priority: Critical
> Attachments: AMQ-5934.patch, activemq.dump
>
>
> We have set up an environment which uses ActiveMQ 5.10.2 as broker and a test 
> durable topic subscriber that connects to the broker using tcp protocol.  The 
> client connection string as follows:
> failover:(tcp://host1:61617?keepAlive=true=false,tcp://host1:61617?keepAlive=true=false)?randomize=false=500=2000=false=false
> At first, we started five test clients (durable topic subscribers) with 
> aforementioned connection string and make sure every subscriber is connected 
> to the broker.  After that, we use a test client to publish 100 messages 
> to the topic that five clients subscribed.  After running for a few hours, 
> two of these five clients were hung (stopped receiving messages from the 
> broker).  In these two clients, there are 636786 and 93915 messages in 
> pending queue, 1000 messages in dispatched queue.  The other three received 
> all the messages from topic.  We have been able to consistently reproduce the 
> issue.   These stale clients appears connected to the broker but do not 
> receive any new messages after they were hung.
> Can you someone look into this issue?  It is very important for us.  We have 
> tried various configurations including jms.prefetchPolicy.topicPrefetch=1 but 
> none of them are working.
> Here is the activemq conf file (activemq.xml) for this issue.
>  
>xmlns="http://www.springframework.org/schema/beans;
>   xmlns:amq="http://activemq.apache.org/schema/core;
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>   xsi:schemaLocation="http://www.springframework.org/schema/beans 
> http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
>   http://activemq.apache.org/schema/core 
> http://activemq.apache.org/schema/core/activemq-core.xsd;>
> 
>  class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> 
> file:${activemq.base}/conf/credentials.properties 
>   
>  
> 
> http://activemq.apache.org/schema/core; 
> advisorySupport="false" useJmx="true" brokerName="dev.masterbroker-1" 
> dataDirectory="${activemq.data}" >
> 
> 
> 
> 
>   
> 
> 
>  
> 
>  
>   
> 
>   
> 
>write="admins,users,guests" admin="admins" />
>admin="users" />
>write="guests,users" admin="guests,users" />
>   
>write="admins,users,guests" admin="admins" />
>admin="users" />
>write="guests,users" admin="guests,users" />
>   
>read="guests,users" write="guests,users" admin="guests,users"/>
> 
> 
>   
>   write="tempDestinationAdmins" admin="tempDestinationAdmins"/>
>   
>   
> 
>   
>sendToDlqIfMaxRetriesExceeded="false">
>   
>   
>   
>   
>maximumRedeliveries="-1" redeliveryDelay="1" />
>   
>   
>   
>initialRedeliveryDelay="5000" redeliveryDelay="1" />
>   
>   
>   
>
>
> 
> 
> 
> 
> 
> 
> 
> 
>  journalMaxFileLength="64mb"
>

[jira] [Updated] (AMQ-6035) Add an option to apply Virtual Destination changes immediately

2015-11-05 Thread Christopher L. Shannon (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMQ-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christopher L. Shannon updated AMQ-6035:

Fix Version/s: 5.13.0

> Add an option to apply Virtual Destination changes immediately
> --
>
> Key: AMQ-6035
> URL: https://issues.apache.org/jira/browse/AMQ-6035
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: Broker
>Reporter: Christopher L. Shannon
>Assignee: Christopher L. Shannon
>Priority: Minor
> Fix For: 5.13.0
>
>
> Normally when using the JavaRuntimeConfigurationBroker to apply updates to 
> virtual destinations, the changes don't apply until a new connection or 
> destination is added.  This usually works but sometimes it would be useful to 
> have the option to apply the changes immediately so existing destinations are 
> changed without having to wait for a new destination or connection.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-6035) Add an option to apply Virtual Destination changes immediately

2015-11-05 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMQ-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14991658#comment-14991658
 ] 

ASF subversion and git services commented on AMQ-6035:
--

Commit 5db9af8b24cea9ab9460abd1c06221e1f08d6d48 in activemq's branch 
refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=5db9af8 ]

https://issues.apache.org/jira/browse/AMQ-6035

Adding a flag to be able to specificy when to apply changes immediately
after updating the virtual destinations using the Java runtime plugin.


> Add an option to apply Virtual Destination changes immediately
> --
>
> Key: AMQ-6035
> URL: https://issues.apache.org/jira/browse/AMQ-6035
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: Broker
>Reporter: Christopher L. Shannon
>Assignee: Christopher L. Shannon
>Priority: Minor
> Fix For: 5.13.0
>
>
> Normally when using the JavaRuntimeConfigurationBroker to apply updates to 
> virtual destinations, the changes don't apply until a new connection or 
> destination is added.  This usually works but sometimes it would be useful to 
> have the option to apply the changes immediately so existing destinations are 
> changed without having to wait for a new destination or connection.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMQ-6035) Add an option to apply Virtual Destination changes immediately

2015-11-05 Thread Christopher L. Shannon (JIRA) 
Christopher L. Shannon created AMQ-6035:
---

 Summary: Add an option to apply Virtual Destination changes 
immediately
 Key: AMQ-6035
 URL: https://issues.apache.org/jira/browse/AMQ-6035
 Project: ActiveMQ
  Issue Type: Improvement
  Components: Broker
Reporter: Christopher L. Shannon
Assignee: Christopher L. Shannon
Priority: Minor


Normally when using the JavaRuntimeConfigurationBroker to apply updates to 
virtual destinations, the changes don't apply until a new connection or 
destination is added.  This usually works but sometimes it would be useful to 
have the option to apply the changes immediately so existing destinations are 
changed without having to wait for a new destination or connection.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AMQ-6035) Add an option to apply Virtual Destination changes immediately

2015-11-05 Thread Christopher L. Shannon (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMQ-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christopher L. Shannon resolved AMQ-6035.
-
Resolution: Fixed

> Add an option to apply Virtual Destination changes immediately
> --
>
> Key: AMQ-6035
> URL: https://issues.apache.org/jira/browse/AMQ-6035
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: Broker
>Reporter: Christopher L. Shannon
>Assignee: Christopher L. Shannon
>Priority: Minor
> Fix For: 5.13.0
>
>
> Normally when using the JavaRuntimeConfigurationBroker to apply updates to 
> virtual destinations, the changes don't apply until a new connection or 
> destination is added.  This usually works but sometimes it would be useful to 
> have the option to apply the changes immediately so existing destinations are 
> changed without having to wait for a new destination or connection.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)