[jira] [Commented] (AMQCPP-619) Support for SSL wilcard certificate
[ https://issues.apache.org/jira/browse/AMQCPP-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711007#comment-16711007 ] Alvin Lin commented on AMQCPP-619: -- On a redhat 7 machine I actually had to add the "void verifyServerCert(const std::string& serverName);" declaration back into the "OpenSSLSocket.h" header file for things to compile. Not sure if it's just me not knowing how to compile c++ project, but just FYI. > Support for SSL wilcard certificate > --- > > Key: AMQCPP-619 > URL: https://issues.apache.org/jira/browse/AMQCPP-619 > Project: ActiveMQ C++ Client > Issue Type: New Feature >Affects Versions: 3.9.4 >Reporter: Francois Godin >Assignee: Timothy Bish >Priority: Major > Attachments: amqcpp-619.patch, sslCertificateWildcard.patch > > > SSL certificate can contain wildcard in the hostname. For example, the > certificate URL "*.proxy.app.com" should match the following address: > * 1.proxy.app.com > * 2.proxy.app.com > Sadly, ActiveMQ-CPP simply compare the two values and thus does not accept > such certificates. > The Openssl page https://wiki.openssl.org/index.php/Hostname_validation > describe some possible implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQCPP-619) Support for SSL wilcard certificate
[ https://issues.apache.org/jira/browse/AMQCPP-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709724#comment-16709724 ] Alvin Lin commented on AMQCPP-619: -- I tested the patch provided by Francois and it works. But the patch only work with openssl 1.0.2+. I found out about this because I was testing on OSX EL Capitan which has openssl 0.9.8 installed by default and I was getting error stating "symbol not found: SSL_get0_param". > Support for SSL wilcard certificate > --- > > Key: AMQCPP-619 > URL: https://issues.apache.org/jira/browse/AMQCPP-619 > Project: ActiveMQ C++ Client > Issue Type: New Feature >Affects Versions: 3.9.4 >Reporter: Francois Godin >Assignee: Timothy Bish >Priority: Major > Attachments: sslCertificateWildcard.patch > > > SSL certificate can contain wildcard in the hostname. For example, the > certificate URL "*.proxy.app.com" should match the following address: > * 1.proxy.app.com > * 2.proxy.app.com > Sadly, ActiveMQ-CPP simply compare the two values and thus does not accept > such certificates. > The Openssl page https://wiki.openssl.org/index.php/Hostname_validation > describe some possible implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQCPP-619) Support for SSL wilcard certificate
[ https://issues.apache.org/jira/browse/AMQCPP-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709562#comment-16709562 ] Alvin Lin commented on AMQCPP-619: -- Would it be possible to to get this one in? AmazonMQ uses wildcard cert, so this patch would be super helpful. > Support for SSL wilcard certificate > --- > > Key: AMQCPP-619 > URL: https://issues.apache.org/jira/browse/AMQCPP-619 > Project: ActiveMQ C++ Client > Issue Type: New Feature >Affects Versions: 3.9.4 >Reporter: Francois Godin >Assignee: Timothy Bish >Priority: Major > Attachments: sslCertificateWildcard.patch > > > SSL certificate can contain wildcard in the hostname. For example, the > certificate URL "*.proxy.app.com" should match the following address: > * 1.proxy.app.com > * 2.proxy.app.com > Sadly, ActiveMQ-CPP simply compare the two values and thus does not accept > such certificates. > The Openssl page https://wiki.openssl.org/index.php/Hostname_validation > describe some possible implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-7082) KahaDB index, recover free pages in parallel with start
[ https://issues.apache.org/jira/browse/AMQ-7082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676687#comment-16676687 ] Alvin Lin commented on AMQ-7082: [~cshannon] I do believe the issue is kind of critical (thus warrants 5.15.8 update soon) as it will lead to many mysterious behavior. > KahaDB index, recover free pages in parallel with start > --- > > Key: AMQ-7082 > URL: https://issues.apache.org/jira/browse/AMQ-7082 > Project: ActiveMQ > Issue Type: Bug > Components: KahaDB >Affects Versions: 5.15.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 5.16.0, 5.15.7 > > > AMQ-6590 fixes free page loss through recovery. The recover process can be > timely, which prevents fast failover, doing recovery on shutdown is > preferable, but it is still not ideal b/c it will hold onto the kahadb lock. > It also can stall shutdown unexpectedly. > AMQ-7080 is going to tackle checkpointing the free list. This should help > avoid the need for recovery but it may still be necessary. If the perf hit is > significant this may need to be optional. > There will still be the need to walk the index to find the free list. > It is possible to run with no free list and grow, and we can do that while we > recover the free list in parallel, then merge the two at a safe point. This > we can do at startup. > In cases where the disk is the bottleneck this won't help much, but it will > help failover and it will help shutdown, with a bit of luck the recovery will > complete before we stop. > > Initially I thought this would be too complex, but if we concede some growth > while we recover, ie: start with an empty free list, it is should be straight > forward to merge with a recovered one. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (AMQ-6764) Add ended statement to Audit log for JMX ops
[ https://issues.apache.org/jira/browse/AMQ-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564199#comment-16564199 ] Alvin Lin edited comment on AMQ-6764 at 7/31/18 7:01 PM: - I just happen to stumble upon this issue. We probably need to change the audit logging for web console too right? https://github.com/apache/activemq/blob/master/activemq-web/src/main/java/org/apache/activemq/web/AuditFilter.java#L36 The code above still expects value of "true" to turn on audit logging for web console; if I in 5.16.0 I configure "org.apache.activemq.audit" to be "entry" then the audit logging would be turned off for web console even though it should remain on. was (Author: alvinlin123): I just happen to stumble upon this issue. We probably need to change the audit logging for web console too right? https://github.com/apache/activemq/blob/master/activemq-web/src/main/java/org/apache/activemq/web/AuditFilter.java#L36 The code above still expects value of "true" to turn on audit logging for web console. > Add ended statement to Audit log for JMX ops > > > Key: AMQ-6764 > URL: https://issues.apache.org/jira/browse/AMQ-6764 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Affects Versions: 5.14.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 5.16.0 > > > AMQ-3100 introduced an audit log. It is boolean enabled or disabled. > This enhancement allows four values for the system property: > "org.apache.activemq.audit" > true|entry,exit,all > - true|entry: log each called op (existing behaviour) > - exit: log the ending of each called op > - all: - log both the entry and exit (called and ended) log statements -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-6764) Add ended statement to Audit log for JMX ops
[ https://issues.apache.org/jira/browse/AMQ-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564199#comment-16564199 ] Alvin Lin commented on AMQ-6764: I just happen to stumble upon this issue. We probably need to change the audit logging for web console too right? https://github.com/apache/activemq/blob/master/activemq-web/src/main/java/org/apache/activemq/web/AuditFilter.java#L36 The code above still expects value of "true" to turn on audit logging for web console. > Add ended statement to Audit log for JMX ops > > > Key: AMQ-6764 > URL: https://issues.apache.org/jira/browse/AMQ-6764 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Affects Versions: 5.14.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 5.16.0 > > > AMQ-3100 introduced an audit log. It is boolean enabled or disabled. > This enhancement allows four values for the system property: > "org.apache.activemq.audit" > true|entry,exit,all > - true|entry: log each called op (existing behaviour) > - exit: log the ending of each called op > - all: - log both the entry and exit (called and ended) log statements -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-7012) Misleading error in org.apache.activemq.transport.stomp.ProtocolConverter
[
https://issues.apache.org/jira/browse/AMQ-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16550494#comment-16550494
]
Alvin Lin commented on AMQ-7012:
Ah, thanks for taking care of this. I was going submit a pull request myself.
Thanks again!
> Misleading error in org.apache.activemq.transport.stomp.ProtocolConverter
> -
>
> Key: AMQ-7012
> URL: https://issues.apache.org/jira/browse/AMQ-7012
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.15.4
>Reporter: Alvin Lin
>Priority: Major
> Fix For: 5.15.5
>
>
> From time to time I see the following log line for STOMP:
>
> {{2018-07-17 07:31:22,204 | WARN | Exception occurred processing:
> -> org.apache.activemq.transport.stomp.ProtocolException: No subscription
> matched. | org.apache.activemq.transport.stomp.ProtocolConverter | ActiveMQ
> NIO Worker 1186}}
>
>
> The misleading part is "", the unknown is suppose to be the STOMP's
> action word (SEND, SUBSCRIBE etc).
> The problem seems to be
> {code:java}
> org.apache.activemq.transport.stomp.ProtocolConverter.safeGetAction(){code}
> that is comparing the STOMP action word with constants defined in
> {code:java}
> org.apache.activemq.transport.stomp.ProtocolConverter.Stomp.Commands{code}
> But for subscribe and unsubscribe the constants are defined as "SUB" and
> "UNSUB" which does not match the actual STOMP action verbs.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMQ-7012) Misleading error in org.apache.activemq.transport.stomp.ProtocolConverter
Alvin Lin created AMQ-7012:
--
Summary: Misleading error in
org.apache.activemq.transport.stomp.ProtocolConverter
Key: AMQ-7012
URL: https://issues.apache.org/jira/browse/AMQ-7012
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.15.4
Reporter: Alvin Lin
>From time to time I see the following log line for STOMP:
{{2018-07-17 07:31:22,204 | WARN | Exception occurred processing: ->
org.apache.activemq.transport.stomp.ProtocolException: No subscription matched.
| org.apache.activemq.transport.stomp.ProtocolConverter | ActiveMQ NIO Worker
1186}}
The misleading part is "", the unknown is suppose to be the STOMP's
action word (SEND, SUBSCRIBE etc).
The problem seems to be
{code:java}
org.apache.activemq.transport.stomp.ProtocolConverter.safeGetAction(){code}
that is comparing the STOMP action word with constants defined in
{code:java}
org.apache.activemq.transport.stomp.ProtocolConverter.Stomp.Commands{code}
But for subscribe and unsubscribe the constants are defined as "SUB" and
"UNSUB" which does not match the actual STOMP action verbs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMQ-6930) bin/activemq should allow stdout/stderr to some file instead of /dev/null for daemon mode
[ https://issues.apache.org/jira/browse/AMQ-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434971#comment-16434971 ] Alvin Lin commented on AMQ-6930: There is actually one more thing regarding this change. We may need to add documentation on the things to be aware of when setting ACTIVEMQ_OUT. Since ActiveMQ by default configures a console appender for log, so when an user configures ACTIVEMQ_OUT all the logs logged to activemq.log will also be logged to $ACTIVEMQ_OUT. So maybe we want to document this and mention about they can disable the ConsoleAppender in log4j.properties; also, the document should probably mention about using logrotate to rotate $ACTIVEMQ_OUT and that logrotate should use "copy truncate". I am more than happy to contribute to the documentation if I can get some lead on the source of the ActiveMQ website and the documentation release process; we definitely don't want to expose the documentation for ACTIVEMQ_OUT before it's release :) > bin/activemq should allow stdout/stderr to some file instead of /dev/null for > daemon mode > - > > Key: AMQ-6930 > URL: https://issues.apache.org/jira/browse/AMQ-6930 > Project: ActiveMQ > Issue Type: Wish >Affects Versions: 5.15.0, 5.15.1, 5.15.2, 5.15.3 >Reporter: Alvin Lin >Priority: Major > Fix For: 5.16.0, 5.15.4 > > > if I do "bin/activemq start" the ActiveMQ process is started with > stdout/stdin redirected to /dev/null. > This makes it hard to debug issue like out of memory error because we can't > see any log, for example, when the JVM flag "ExitOnOutOfMemoryError" is > turned on. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMQ-6930) bin/activemq should allow stdout/stderr to some file instead of /dev/null for daemon mode
[ https://issues.apache.org/jira/browse/AMQ-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alvin Lin updated AMQ-6930: --- Summary: bin/activemq should allow stdout/stderr to some file instead of /dev/null for daemon mode (was: bin/activemq should not redirect stdout/stderr to /dev/null for daemon mode) > bin/activemq should allow stdout/stderr to some file instead of /dev/null for > daemon mode > - > > Key: AMQ-6930 > URL: https://issues.apache.org/jira/browse/AMQ-6930 > Project: ActiveMQ > Issue Type: Wish >Affects Versions: 5.15.0, 5.15.1, 5.15.2, 5.15.3 >Reporter: Alvin Lin >Priority: Major > > if I do "bin/activemq start" the ActiveMQ process is started with > stdout/stdin redirected to /dev/null. > This makes it hard to debug issue like out of memory error because we can't > see any log, for example, when the JVM flag "ExitOnOutOfMemoryError" is > turned on. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-6930) bin/activemq should not redirect stdout/stderr to /dev/null for daemon mode
[ https://issues.apache.org/jira/browse/AMQ-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402434#comment-16402434 ] Alvin Lin commented on AMQ-6930: Ah, I see. May I ask the reason behind the intention? The use case I am thinking about is that troubleshooting in a production machine for JVM related problems. JVM prints some log to stdout/stderr when some fatal error occur (like out of memory error), those log will not appear in the broker logs. It may not be feasible to start ActiveMQ in console mode in production environment (e.g. developer don't have access to production environment). Having the stdout/stderr content log somewhere speeds up troubleshooting process. System like Tomcat actually re-directs stdout/stderr to catalina.out, so I think ActiveMQ should probably do the same? Maybe the title of this issue is too strict, it probably should have been "bin/activemq should allow stdout/stderr to be redirected to some file for daemon mode" so that we can do something like "bin/activemq start -out /var/logs/activemq.out"? Would this be something worth considering? > bin/activemq should not redirect stdout/stderr to /dev/null for daemon mode > --- > > Key: AMQ-6930 > URL: https://issues.apache.org/jira/browse/AMQ-6930 > Project: ActiveMQ > Issue Type: Wish >Affects Versions: 5.15.0, 5.15.1, 5.15.2, 5.15.3 >Reporter: Alvin Lin >Priority: Major > > if I do "bin/activemq start" the ActiveMQ process is started with > stdout/stdin redirected to /dev/null. > This makes it hard to debug issue like out of memory error because we can't > see any log, for example, when the JVM flag "ExitOnOutOfMemoryError" is > turned on. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (AMQ-6930) bin/activemq should not redirect stdout/stderr to /dev/null for daemon mode
[ https://issues.apache.org/jira/browse/AMQ-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alvin Lin reopened AMQ-6930: > bin/activemq should not redirect stdout/stderr to /dev/null for daemon mode > --- > > Key: AMQ-6930 > URL: https://issues.apache.org/jira/browse/AMQ-6930 > Project: ActiveMQ > Issue Type: Wish >Affects Versions: 5.15.0, 5.15.1, 5.15.2, 5.15.3 >Reporter: Alvin Lin >Priority: Major > > if I do "bin/activemq start" the ActiveMQ process is started with > stdout/stdin redirected to /dev/null. > This makes it hard to debug issue like out of memory error because we can't > see any log, for example, when the JVM flag "ExitOnOutOfMemoryError" is > turned on. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMQ-6930) bin/activemq should not redirect stdout/stderr to /dev/null for daemon mode
Alvin Lin created AMQ-6930: -- Summary: bin/activemq should not redirect stdout/stderr to /dev/null for daemon mode Key: AMQ-6930 URL: https://issues.apache.org/jira/browse/AMQ-6930 Project: ActiveMQ Issue Type: Wish Affects Versions: 5.15.3, 5.15.2, 5.15.1, 5.15.0 Reporter: Alvin Lin if I do "bin/activemq start" the ActiveMQ process is started with stdout/stdin redirected to /dev/null. This makes it hard to debug issue like out of memory error because we can't see any log, for example, when the JVM flag "ExitOnOutOfMemoryError" is turned on. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-6908) Inconsistent authorization in web console
[ https://issues.apache.org/jira/browse/AMQ-6908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402364#comment-16402364 ] Alvin Lin commented on AMQ-6908: I submitted a pull request to fix this issue https://github.com/apache/activemq/pull/280 > Inconsistent authorization in web console > - > > Key: AMQ-6908 > URL: https://issues.apache.org/jira/browse/AMQ-6908 > Project: ActiveMQ > Issue Type: Bug > Components: webconsole >Affects Versions: 5.15.0, 5.15.1, 5.15.2, 5.15.3 >Reporter: Alvin Lin >Priority: Major > > Looking at org.apache.activemq.web.WebClient#createWebClient we can actually > configure the connectionFactory in webconsle-embedded.xml to use the > credential in the HTTP Authorization header to connect to the core ActiveMQ > broker by setting the username and password to null. > But when I do that, the browse in console feature stops working if I have > authentication enabled, because org.apache.activemq.web.QueueBrowseQuery > requires the given connectionFactory to be configured with non-null username > and password. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMQ-6908) Inconsistent authorization in web console
Alvin Lin created AMQ-6908: -- Summary: Inconsistent authorization in web console Key: AMQ-6908 URL: https://issues.apache.org/jira/browse/AMQ-6908 Project: ActiveMQ Issue Type: Bug Components: webconsole Affects Versions: 5.15.3, 5.15.2, 5.15.1, 5.15.0 Reporter: Alvin Lin Looking at org.apache.activemq.web.WebClient#createWebClient we can actually configure the connectionFactory in webconsle-embedded.xml to use the credential in the HTTP Authorization header to connect to the core ActiveMQ broker by setting the username and password to null. But when I do that, the browse in console feature stops working if I have authentication enabled, because org.apache.activemq.web.QueueBrowseQuery requires the given connectionFactory to be configured with non-null username and password. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMQ-6782) Document about cursorMemoryHighWaterMark is misleading
Alvin Lin created AMQ-6782: -- Summary: Document about cursorMemoryHighWaterMark is misleading Key: AMQ-6782 URL: https://issues.apache.org/jira/browse/AMQ-6782 Project: ActiveMQ Issue Type: Bug Components: Documentation Affects Versions: 5.15.0 Reporter: Alvin Lin In http://activemq.apache.org/per-destination-policies.html the description for "cursorMemoryHighWaterMark" is kind of misleading; the description about that the threshold will apply to "the destination's memoryLimit (when defined) " made me think that it applies to TopicSubscription as well. I thought if I configure a topic with memoryLimit of 100MB and system memory limit of 1GB, then TopicSubscription (or more specifically the FilePendingMessageCurosr) uses cursorMemoryHighWaterMark against 100MB. But through testing, code reading, and http://blog.christianposta.com/activemq/activemq-understanding-memory-usage I found out the hard way this is not the case; only queues will use cursorMemoryHighWaterMark against the per destination memory limit. My suggestion is to add additional notes that the configured cursorMemoryHighWaterMark applies only to system memory in the case of topic. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMQ-6569) activemq.sh deletes wrong .stop file
[ https://issues.apache.org/jira/browse/AMQ-6569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alvin Lin updated AMQ-6569: --- Description: This commit https://github.com/apache/activemq/commit/aeb93e4a2455dff169da302fb19f7fa55d21a0c0#diff-b4401da9a3207c3555ce67fda6d6ce25L526 "reverted" the code in the script to delete "$PIDFILE.stop", so currently it's trying to delete "pid.stop" which doesn't get created anymore. was: This commit https://github.com/apache/activemq/commit/aeb93e4a2455dff169da302fb19f7fa55d21a0c0#diff-b4401da9a3207c3555ce67fda6d6ce25L526 "reverted" the code in the script to delete "$PIDFILE.stop", so currently it's trying to delete "pid.stop" which ins non-existing. > activemq.sh deletes wrong .stop file > > > Key: AMQ-6569 > URL: https://issues.apache.org/jira/browse/AMQ-6569 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.14.3 >Reporter: Alvin Lin >Priority: Minor > > This commit > https://github.com/apache/activemq/commit/aeb93e4a2455dff169da302fb19f7fa55d21a0c0#diff-b4401da9a3207c3555ce67fda6d6ce25L526 > > "reverted" the code in the script to delete "$PIDFILE.stop", so currently > it's trying to delete "pid.stop" which doesn't get created anymore. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMQ-6569) activemq.sh deletes wrong .stop file
[
https://issues.apache.org/jira/browse/AMQ-6569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alvin Lin updated AMQ-6569:
---
Description: This commit
https://github.com/apache/activemq/commit/aeb93e4a2455dff169da302fb19f7fa55d21a0c0#diff-b4401da9a3207c3555ce67fda6d6ce25L526
"reverted" the code in the script to delete "${PIDFILE}.stop", so currently
it's trying to delete "pid.stop" which ins non-existing. (was: This commit
https://github.com/apache/activemq/commit/aeb93e4a2455dff169da302fb19f7fa55d21a0c0#diff-b4401da9a3207c3555ce67fda6d6ce25L526
"reverted" the code script to delete "${PIDFILE}.stop", so currently it's
trying to delete "pid.stop" which ins non-existing. )
> activemq.sh deletes wrong .stop file
>
>
> Key: AMQ-6569
> URL: https://issues.apache.org/jira/browse/AMQ-6569
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.14.3
>Reporter: Alvin Lin
>Priority: Minor
>
> This commit
> https://github.com/apache/activemq/commit/aeb93e4a2455dff169da302fb19f7fa55d21a0c0#diff-b4401da9a3207c3555ce67fda6d6ce25L526
> "reverted" the code in the script to delete "${PIDFILE}.stop", so currently
> it's trying to delete "pid.stop" which ins non-existing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMQ-6569) activemq.sh deletes wrong .stop file
[
https://issues.apache.org/jira/browse/AMQ-6569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alvin Lin updated AMQ-6569:
---
Description:
This commit
https://github.com/apache/activemq/commit/aeb93e4a2455dff169da302fb19f7fa55d21a0c0#diff-b4401da9a3207c3555ce67fda6d6ce25L526
"reverted" the code in the script to delete "\${PIDFILE}.stop", so currently
it's trying to delete "pid.stop" which ins non-existing.
was:
This commit
https://github.com/apache/activemq/commit/aeb93e4a2455dff169da302fb19f7fa55d21a0c0#diff-b4401da9a3207c3555ce67fda6d6ce25L526
"reverted" the code in the script to delete "${PIDFILE}.stop", so currently
it's trying to delete "pid.stop" which ins non-existing.
> activemq.sh deletes wrong .stop file
>
>
> Key: AMQ-6569
> URL: https://issues.apache.org/jira/browse/AMQ-6569
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.14.3
>Reporter: Alvin Lin
>Priority: Minor
>
> This commit
> https://github.com/apache/activemq/commit/aeb93e4a2455dff169da302fb19f7fa55d21a0c0#diff-b4401da9a3207c3555ce67fda6d6ce25L526
>
> "reverted" the code in the script to delete "\${PIDFILE}.stop", so currently
> it's trying to delete "pid.stop" which ins non-existing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMQ-6569) activemq.sh deletes wrong .stop file
[
https://issues.apache.org/jira/browse/AMQ-6569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alvin Lin updated AMQ-6569:
---
Description:
This commit
https://github.com/apache/activemq/commit/aeb93e4a2455dff169da302fb19f7fa55d21a0c0#diff-b4401da9a3207c3555ce67fda6d6ce25L526
"reverted" the code in the script to delete "${PIDFILE}.stop", so currently
it's trying to delete "pid.stop" which ins non-existing.
was:This commit
https://github.com/apache/activemq/commit/aeb93e4a2455dff169da302fb19f7fa55d21a0c0#diff-b4401da9a3207c3555ce67fda6d6ce25L526
"reverted" the code in the script to delete "${PIDFILE}.stop", so currently
it's trying to delete "pid.stop" which ins non-existing.
> activemq.sh deletes wrong .stop file
>
>
> Key: AMQ-6569
> URL: https://issues.apache.org/jira/browse/AMQ-6569
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.14.3
>Reporter: Alvin Lin
>Priority: Minor
>
> This commit
> https://github.com/apache/activemq/commit/aeb93e4a2455dff169da302fb19f7fa55d21a0c0#diff-b4401da9a3207c3555ce67fda6d6ce25L526
>
> "reverted" the code in the script to delete "${PIDFILE}.stop", so currently
> it's trying to delete "pid.stop" which ins non-existing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMQ-6569) activemq.sh deletes wrong .stop file
[
https://issues.apache.org/jira/browse/AMQ-6569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alvin Lin updated AMQ-6569:
---
Description:
This commit
https://github.com/apache/activemq/commit/aeb93e4a2455dff169da302fb19f7fa55d21a0c0#diff-b4401da9a3207c3555ce67fda6d6ce25L526
"reverted" the code in the script to delete "$PIDFILE.stop", so currently it's
trying to delete "pid.stop" which ins non-existing.
was:
This commit
https://github.com/apache/activemq/commit/aeb93e4a2455dff169da302fb19f7fa55d21a0c0#diff-b4401da9a3207c3555ce67fda6d6ce25L526
"reverted" the code in the script to delete "\${PIDFILE}.stop", so currently
it's trying to delete "pid.stop" which ins non-existing.
> activemq.sh deletes wrong .stop file
>
>
> Key: AMQ-6569
> URL: https://issues.apache.org/jira/browse/AMQ-6569
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.14.3
>Reporter: Alvin Lin
>Priority: Minor
>
> This commit
> https://github.com/apache/activemq/commit/aeb93e4a2455dff169da302fb19f7fa55d21a0c0#diff-b4401da9a3207c3555ce67fda6d6ce25L526
>
> "reverted" the code in the script to delete "$PIDFILE.stop", so currently
> it's trying to delete "pid.stop" which ins non-existing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMQ-6569) activemq.sh deletes wrong .stop file
Alvin Lin created AMQ-6569:
--
Summary: activemq.sh deletes wrong .stop file
Key: AMQ-6569
URL: https://issues.apache.org/jira/browse/AMQ-6569
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.14.3
Reporter: Alvin Lin
Priority: Minor
This commit
https://github.com/apache/activemq/commit/aeb93e4a2455dff169da302fb19f7fa55d21a0c0#diff-b4401da9a3207c3555ce67fda6d6ce25L526
"reverted" the code script to delete "${PIDFILE}.stop", so currently it's
trying to delete "pid.stop" which ins non-existing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
