[jira] [Resolved] (AMQ-6159) In-Memory JobScheduler handles cron repeats incorrectly

[ https://issues.apache.org/jira/browse/AMQ-6159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-6159. --- Resolution: Fixed > In-Memory JobScheduler handles cron repeats incorrectly >

[jira] [Commented] (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:comment-tabpanel=15133070#comment-15133070 ] Timothy Bish commented on AMQ-6157: --- I see, you are using the failover transport bits with the JMS Bridge.

[jira] [Created] (AMQ-6159) In-Memory JobScheduler handles cron repeats incorrectly

Timothy Bish created AMQ-6159: - Summary: In-Memory JobScheduler handles cron repeats incorrectly Key: AMQ-6159 URL: https://issues.apache.org/jira/browse/AMQ-6159 Project: ActiveMQ Issue Type:

[jira] [Commented] (AMQ-6159) In-Memory JobScheduler handles cron repeats incorrectly

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

[jira] [Commented] (ARTEMIS-376) NPE occurs when backup handover to live

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

[jira] [Commented] (ARTEMIS-376) NPE occurs when backup handover to live

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

[jira] [Commented] (AMQ-6148) When use LDAP auth, Activemq should not always connect to ldap service to do authentication

[ https://issues.apache.org/jira/browse/AMQ-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133329#comment-15133329 ] JIE CHEN commented on AMQ-6148: --- Hi Justin, It looks like another project instead of a plugin in ActiveMQ,

[jira] [Commented] (AMQ-6148) When use LDAP auth, Activemq should not always connect to ldap service to do authentication

[ https://issues.apache.org/jira/browse/AMQ-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133467#comment-15133467 ] Justin Bertram commented on AMQ-6148: - That's correct. ActiveMQ Artemis is not a plugin to ActiveMQ but

[jira] [Commented] (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:comment-tabpanel=15133392#comment-15133392 ] Timothy Bish commented on AMQ-6157: --- I did some trivial testing and cannot reproduce this using the latest

[jira] [Commented] (ARTEMIS-385) Race between topology update and connection creation

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

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

Erik Domstad created AMQ-6157: - Summary: Thread leak when failover fails to connect at startup Key: AMQ-6157 URL: https://issues.apache.org/jira/browse/AMQ-6157 Project: ActiveMQ Issue Type: Bug

[jira] [Created] (ARTEMIS-386) fix shebang on artemis scripts

Abhijith Prabhakar created ARTEMIS-386: -- Summary: fix shebang on artemis scripts Key: ARTEMIS-386 URL: https://issues.apache.org/jira/browse/ARTEMIS-386 Project: ActiveMQ Artemis Issue

[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=15132407#comment-15132407 ] Ger Lawlor commented on AMQ-6156: - Hi Timothy, That does not explain then why some threads connect and

[jira] [Commented] (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:comment-tabpanel=15132405#comment-15132405 ] Timothy Bish commented on AMQ-6157: --- This seems to be the result of you not closing failed connections.

[jira] [Created] (AMQ-6158) Computing message size for a durable subscription is very slow

Christopher L. Shannon created AMQ-6158: --- Summary: Computing message size for a durable subscription is very slow Key: AMQ-6158 URL: https://issues.apache.org/jira/browse/AMQ-6158 Project:

[jira] [Commented] (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:comment-tabpanel=15132333#comment-15132333 ] Erik commented on AMQ-6157: --- Attached by ActiveMQ configuration and full dump from jstack > Thread leak when

[jira] [Updated] (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 updated AMQ-6157: -- Attachment: tomee.xml > Thread leak when failover fails to connect at startup >

[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=15132399#comment-15132399 ] Timothy Bish commented on AMQ-6156: --- This looks normal for any connect attempt that fails, the connection

[jira] [Updated] (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 updated AMQ-6157: -- Attachment: broker-config.xml > Thread leak when failover fails to connect at startup >

[jira] [Updated] (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 updated AMQ-6157: -- Attachment: jstack.txt > Thread leak when failover fails to connect at startup >

[jira] [Issue Comment Deleted] (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 updated AMQ-6157: -- Comment: was deleted (was: Active MQ configuration) > Thread leak when failover fails to connect at startup >

[jira] [Commented] (AMQ-6036) Too trivial check in SubQueueSelectorCacheBroker.hasWildcards

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

[jira] [Updated] (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 updated AMQ-6157: -- Attachment: broker-config.xml Active MQ configuration > Thread leak when failover fails to connect at startup >

[jira] [Commented] (ARTEMIS-385) Race between topology update and connection creation

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

[jira] [Commented] (AMQ-6036) Too trivial check in SubQueueSelectorCacheBroker.hasWildcards

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

[jira] [Commented] (AMQ-6036) Too trivial check in SubQueueSelectorCacheBroker.hasWildcards

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

[jira] [Commented] (AMQ-6036) Too trivial check in SubQueueSelectorCacheBroker.hasWildcards

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

[jira] [Commented] (ARTEMIS-385) Race between topology update and connection creation

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

[jira] [Commented] (ARTEMIS-385) Race between topology update and connection creation

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

[jira] [Commented] (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:comment-tabpanel=15132472#comment-15132472 ] Erik commented on AMQ-6157: --- At this point I haven't deployed any of my code, only a clean installation of Tomee

[jira] [Resolved] (AMQ-6158) Computing message size for a durable subscription is very slow

[ https://issues.apache.org/jira/browse/AMQ-6158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon resolved AMQ-6158. - Resolution: Fixed Fix Version/s: 5.13.2 5.14.0 Patch

[jira] [Commented] (ARTEMIS-385) Race between topology update and connection creation

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

[jira] [Commented] (ARTEMIS-385) Race between topology update and connection creation

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

[jira] [Commented] (ARTEMIS-380) Cluster Topology is wrong after update restart.

[ https://issues.apache.org/jira/browse/ARTEMIS-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15132471#comment-15132471 ] Justin Bertram commented on ARTEMIS-380: Thanks for additional clarification on the use-case, but

[jira] [Commented] (ARTEMIS-385) Race between topology update and connection creation

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

[jira] [Commented] (AMQ-6036) Too trivial check in SubQueueSelectorCacheBroker.hasWildcards

[ https://issues.apache.org/jira/browse/AMQ-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15132489#comment-15132489 ] Patrik Dudits commented on AMQ-6036: PR has been updated - added headers, rebased, and fixed one more

[jira] [Resolved] (AMQ-6036) Too trivial check in SubQueueSelectorCacheBroker.hasWildcards

[ https://issues.apache.org/jira/browse/AMQ-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon resolved AMQ-6036. - Resolution: Fixed Patch applied to master, thanks. > Too trivial check in

[jira] [Closed] (AMQ-6140) 2016-01-24 13:02:01,501 | WARN | Exception occurred processing: CONNECT accept-version:1.0,1.1 heart-beat:10000,30000

[ https://issues.apache.org/jira/browse/AMQ-6140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-6140. - Resolution: Not A Problem >From the error given this is the case of multiple client connect attempts with

[jira] [Closed] (AMQ-6155) Spurious InvalidDestinationException publishing to a temp queue from a new connection

[ https://issues.apache.org/jira/browse/AMQ-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-6155. - Resolution: Not A Problem Things appear to be working as designed. There is a workaround for the use case

[jira] [Commented] (ARTEMIS-376) NPE occurs when backup handover to live

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

[jira] [Updated] (ARTEMIS-376) NPE occurs when backup handover to live

[ https://issues.apache.org/jira/browse/ARTEMIS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-376: --- Fix Version/s: 1.3.0 > NPE occurs when backup handover to live >

[jira] [Commented] (ARTEMIS-376) NPE occurs when backup handover to live

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

[jira] [Commented] (ARTEMIS-376) NPE occurs when backup handover to live

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

[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=15133014#comment-15133014 ] Timothy Bish commented on AMQ-6147: --- Should also test with the new option