[jira] [Closed] (ARTEMIS-4531) Limit logfile output by default
[
https://issues.apache.org/jira/browse/ARTEMIS-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geert Schuring closed ARTEMIS-4531.
---
Resolution: Won't Fix
Suggested solution does not work as intended, and we don't want to introduce
more changes to log file handling in a minor release.
> Limit logfile output by default
> ---
>
> Key: ARTEMIS-4531
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4531
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 2.31.2
>Reporter: Geert Schuring
>Priority: Minor
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The logging config does not limit the amount of rolled-over logfiles that are
> stored, causing a minor resource leak. The system will (eventually) run out
> of disk space without manual intervention.
> The relevant config in etc/log4j2.properties currently looks like this:
> {code:java}
> # Log file appender
> appender.log_file.type = RollingFile
> appender.log_file.name = log_file
> appender.log_file.fileName = ${sys:artemis.instance}/log/artemis.log
> appender.log_file.filePattern =
> ${sys:artemis.instance}/log/artemis.log.%d{-MM-dd}
> appender.log_file.layout.type = PatternLayout
> appender.log_file.layout.pattern = %d %-5level [%logger] %msg%n
> appender.log_file.policies.type = Policies
> appender.log_file.policies.cron.type = CronTriggeringPolicy
> appender.log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.log_file.policies.cron.evaluateOnStartup = true
> # Audit log file appender
> appender.audit_log_file.type = RollingFile
> appender.audit_log_file.name = audit_log_file
> appender.audit_log_file.fileName = ${sys:artemis.instance}/log/audit.log
> appender.audit_log_file.filePattern =
> ${sys:artemis.instance}/log/audit.log.%d{-MM-dd}
> appender.audit_log_file.layout.type = PatternLayout
> appender.audit_log_file.layout.pattern = %d [AUDIT](%t) %msg%n
> appender.audit_log_file.policies.type = Policies
> appender.audit_log_file.policies.cron.type = CronTriggeringPolicy
> appender.audit_log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.audit_log_file.policies.cron.evaluateOnStartup = true{code}
> This results in a new log file every day if there is any logging output.
> These files are never deleted and keep accumulating.
> After setting a limit of 5 files it looks like this:
> {code:java}
> # Log file appender
> appender.log_file.type = RollingFile
> appender.log_file.name = log_file
> appender.log_file.fileName = ${sys:artemis.instance}/log/artemis.log
> appender.log_file.filePattern =
> ${sys:artemis.instance}/log/artemis.log.%d{-MM-dd}
> appender.log_file.layout.type = PatternLayout
> appender.log_file.layout.pattern = %d %-5level [%logger] %msg%n
> appender.log_file.policies.type = Policies
> appender.log_file.policies.cron.type = CronTriggeringPolicy
> appender.log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.log_file.policies.cron.evaluateOnStartup = true
> appender.log_file.strategy.type = DefaultRolloverStrategy
> appender.log_file.strategy.max = 5
> # Audit log file appender
> appender.audit_log_file.type = RollingFile
> appender.audit_log_file.name = audit_log_file
> appender.audit_log_file.fileName = ${sys:artemis.instance}/log/audit.log
> appender.audit_log_file.filePattern =
> ${sys:artemis.instance}/log/audit.log.%d{-MM-dd}
> appender.audit_log_file.layout.type = PatternLayout
> appender.audit_log_file.layout.pattern = %d [AUDIT](%t) %msg%n
> appender.audit_log_file.policies.type = Policies
> appender.audit_log_file.policies.cron.type = CronTriggeringPolicy
> appender.audit_log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.audit_log_file.policies.cron.evaluateOnStartup = true
> appender.audit_log_file.strategy.type = DefaultRolloverStrategy
> appender.audit_log_file.strategy.max = 5 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-4531) Limit logfile output by default
[
https://issues.apache.org/jira/browse/ARTEMIS-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799063#comment-17799063
]
Geert Schuring edited comment on ARTEMIS-4531 at 12/20/23 3:24 PM:
---
TLDR: Doesn't work as intended. Lets close the PR and close this issue.
I've commented on the PR:
[https://github.com/apache/activemq-artemis/pull/4718#issuecomment-1864656817]
was (Author: cathodion):
TLDR: Doesn't work as intended. Lets delete the PR and close this issue.
I've commented on the PR:
[https://github.com/apache/activemq-artemis/pull/4718#issuecomment-1864656817]
> Limit logfile output by default
> ---
>
> Key: ARTEMIS-4531
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4531
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 2.31.2
>Reporter: Geert Schuring
>Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The logging config does not limit the amount of rolled-over logfiles that are
> stored, causing a minor resource leak. The system will (eventually) run out
> of disk space without manual intervention.
> The relevant config in etc/log4j2.properties currently looks like this:
> {code:java}
> # Log file appender
> appender.log_file.type = RollingFile
> appender.log_file.name = log_file
> appender.log_file.fileName = ${sys:artemis.instance}/log/artemis.log
> appender.log_file.filePattern =
> ${sys:artemis.instance}/log/artemis.log.%d{-MM-dd}
> appender.log_file.layout.type = PatternLayout
> appender.log_file.layout.pattern = %d %-5level [%logger] %msg%n
> appender.log_file.policies.type = Policies
> appender.log_file.policies.cron.type = CronTriggeringPolicy
> appender.log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.log_file.policies.cron.evaluateOnStartup = true
> # Audit log file appender
> appender.audit_log_file.type = RollingFile
> appender.audit_log_file.name = audit_log_file
> appender.audit_log_file.fileName = ${sys:artemis.instance}/log/audit.log
> appender.audit_log_file.filePattern =
> ${sys:artemis.instance}/log/audit.log.%d{-MM-dd}
> appender.audit_log_file.layout.type = PatternLayout
> appender.audit_log_file.layout.pattern = %d [AUDIT](%t) %msg%n
> appender.audit_log_file.policies.type = Policies
> appender.audit_log_file.policies.cron.type = CronTriggeringPolicy
> appender.audit_log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.audit_log_file.policies.cron.evaluateOnStartup = true{code}
> This results in a new log file every day if there is any logging output.
> These files are never deleted and keep accumulating.
> After setting a limit of 5 files it looks like this:
> {code:java}
> # Log file appender
> appender.log_file.type = RollingFile
> appender.log_file.name = log_file
> appender.log_file.fileName = ${sys:artemis.instance}/log/artemis.log
> appender.log_file.filePattern =
> ${sys:artemis.instance}/log/artemis.log.%d{-MM-dd}
> appender.log_file.layout.type = PatternLayout
> appender.log_file.layout.pattern = %d %-5level [%logger] %msg%n
> appender.log_file.policies.type = Policies
> appender.log_file.policies.cron.type = CronTriggeringPolicy
> appender.log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.log_file.policies.cron.evaluateOnStartup = true
> appender.log_file.strategy.type = DefaultRolloverStrategy
> appender.log_file.strategy.max = 5
> # Audit log file appender
> appender.audit_log_file.type = RollingFile
> appender.audit_log_file.name = audit_log_file
> appender.audit_log_file.fileName = ${sys:artemis.instance}/log/audit.log
> appender.audit_log_file.filePattern =
> ${sys:artemis.instance}/log/audit.log.%d{-MM-dd}
> appender.audit_log_file.layout.type = PatternLayout
> appender.audit_log_file.layout.pattern = %d [AUDIT](%t) %msg%n
> appender.audit_log_file.policies.type = Policies
> appender.audit_log_file.policies.cron.type = CronTriggeringPolicy
> appender.audit_log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.audit_log_file.policies.cron.evaluateOnStartup = true
> appender.audit_log_file.strategy.type = DefaultRolloverStrategy
> appender.audit_log_file.strategy.max = 5 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4531) Limit logfile output by default
[
https://issues.apache.org/jira/browse/ARTEMIS-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799063#comment-17799063
]
Geert Schuring commented on ARTEMIS-4531:
-
TLDR: Doesn't work as intended. Lets delete the PR and close this issue.
I've commented on the PR:
[https://github.com/apache/activemq-artemis/pull/4718#issuecomment-1864656817]
> Limit logfile output by default
> ---
>
> Key: ARTEMIS-4531
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4531
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 2.31.2
>Reporter: Geert Schuring
>Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The logging config does not limit the amount of rolled-over logfiles that are
> stored, causing a minor resource leak. The system will (eventually) run out
> of disk space without manual intervention.
> The relevant config in etc/log4j2.properties currently looks like this:
> {code:java}
> # Log file appender
> appender.log_file.type = RollingFile
> appender.log_file.name = log_file
> appender.log_file.fileName = ${sys:artemis.instance}/log/artemis.log
> appender.log_file.filePattern =
> ${sys:artemis.instance}/log/artemis.log.%d{-MM-dd}
> appender.log_file.layout.type = PatternLayout
> appender.log_file.layout.pattern = %d %-5level [%logger] %msg%n
> appender.log_file.policies.type = Policies
> appender.log_file.policies.cron.type = CronTriggeringPolicy
> appender.log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.log_file.policies.cron.evaluateOnStartup = true
> # Audit log file appender
> appender.audit_log_file.type = RollingFile
> appender.audit_log_file.name = audit_log_file
> appender.audit_log_file.fileName = ${sys:artemis.instance}/log/audit.log
> appender.audit_log_file.filePattern =
> ${sys:artemis.instance}/log/audit.log.%d{-MM-dd}
> appender.audit_log_file.layout.type = PatternLayout
> appender.audit_log_file.layout.pattern = %d [AUDIT](%t) %msg%n
> appender.audit_log_file.policies.type = Policies
> appender.audit_log_file.policies.cron.type = CronTriggeringPolicy
> appender.audit_log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.audit_log_file.policies.cron.evaluateOnStartup = true{code}
> This results in a new log file every day if there is any logging output.
> These files are never deleted and keep accumulating.
> After setting a limit of 5 files it looks like this:
> {code:java}
> # Log file appender
> appender.log_file.type = RollingFile
> appender.log_file.name = log_file
> appender.log_file.fileName = ${sys:artemis.instance}/log/artemis.log
> appender.log_file.filePattern =
> ${sys:artemis.instance}/log/artemis.log.%d{-MM-dd}
> appender.log_file.layout.type = PatternLayout
> appender.log_file.layout.pattern = %d %-5level [%logger] %msg%n
> appender.log_file.policies.type = Policies
> appender.log_file.policies.cron.type = CronTriggeringPolicy
> appender.log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.log_file.policies.cron.evaluateOnStartup = true
> appender.log_file.strategy.type = DefaultRolloverStrategy
> appender.log_file.strategy.max = 5
> # Audit log file appender
> appender.audit_log_file.type = RollingFile
> appender.audit_log_file.name = audit_log_file
> appender.audit_log_file.fileName = ${sys:artemis.instance}/log/audit.log
> appender.audit_log_file.filePattern =
> ${sys:artemis.instance}/log/audit.log.%d{-MM-dd}
> appender.audit_log_file.layout.type = PatternLayout
> appender.audit_log_file.layout.pattern = %d [AUDIT](%t) %msg%n
> appender.audit_log_file.policies.type = Policies
> appender.audit_log_file.policies.cron.type = CronTriggeringPolicy
> appender.audit_log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.audit_log_file.policies.cron.evaluateOnStartup = true
> appender.audit_log_file.strategy.type = DefaultRolloverStrategy
> appender.audit_log_file.strategy.max = 5 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4531) Limit logfile output by default
[
https://issues.apache.org/jira/browse/ARTEMIS-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798893#comment-17798893
]
Geert Schuring commented on ARTEMIS-4531:
-
I'm seeing strange behaviour duing some more tests and I'm no longer sure this
works as intended. Lets put this on hold until I've done more tests.
> Limit logfile output by default
> ---
>
> Key: ARTEMIS-4531
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4531
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 2.31.2
>Reporter: Geert Schuring
>Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The logging config does not limit the amount of rolled-over logfiles that are
> stored, causing a minor resource leak. The system will (eventually) run out
> of disk space without manual intervention.
> The relevant config in etc/log4j2.properties currently looks like this:
> {code:java}
> # Log file appender
> appender.log_file.type = RollingFile
> appender.log_file.name = log_file
> appender.log_file.fileName = ${sys:artemis.instance}/log/artemis.log
> appender.log_file.filePattern =
> ${sys:artemis.instance}/log/artemis.log.%d{-MM-dd}
> appender.log_file.layout.type = PatternLayout
> appender.log_file.layout.pattern = %d %-5level [%logger] %msg%n
> appender.log_file.policies.type = Policies
> appender.log_file.policies.cron.type = CronTriggeringPolicy
> appender.log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.log_file.policies.cron.evaluateOnStartup = true
> # Audit log file appender
> appender.audit_log_file.type = RollingFile
> appender.audit_log_file.name = audit_log_file
> appender.audit_log_file.fileName = ${sys:artemis.instance}/log/audit.log
> appender.audit_log_file.filePattern =
> ${sys:artemis.instance}/log/audit.log.%d{-MM-dd}
> appender.audit_log_file.layout.type = PatternLayout
> appender.audit_log_file.layout.pattern = %d [AUDIT](%t) %msg%n
> appender.audit_log_file.policies.type = Policies
> appender.audit_log_file.policies.cron.type = CronTriggeringPolicy
> appender.audit_log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.audit_log_file.policies.cron.evaluateOnStartup = true{code}
> This results in a new log file every day if there is any logging output.
> These files are never deleted and keep accumulating.
> After setting a limit of 5 files it looks like this:
> {code:java}
> # Log file appender
> appender.log_file.type = RollingFile
> appender.log_file.name = log_file
> appender.log_file.fileName = ${sys:artemis.instance}/log/artemis.log
> appender.log_file.filePattern =
> ${sys:artemis.instance}/log/artemis.log.%d{-MM-dd}
> appender.log_file.layout.type = PatternLayout
> appender.log_file.layout.pattern = %d %-5level [%logger] %msg%n
> appender.log_file.policies.type = Policies
> appender.log_file.policies.cron.type = CronTriggeringPolicy
> appender.log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.log_file.policies.cron.evaluateOnStartup = true
> appender.log_file.strategy.type = DefaultRolloverStrategy
> appender.log_file.strategy.max = 5
> # Audit log file appender
> appender.audit_log_file.type = RollingFile
> appender.audit_log_file.name = audit_log_file
> appender.audit_log_file.fileName = ${sys:artemis.instance}/log/audit.log
> appender.audit_log_file.filePattern =
> ${sys:artemis.instance}/log/audit.log.%d{-MM-dd}
> appender.audit_log_file.layout.type = PatternLayout
> appender.audit_log_file.layout.pattern = %d [AUDIT](%t) %msg%n
> appender.audit_log_file.policies.type = Policies
> appender.audit_log_file.policies.cron.type = CronTriggeringPolicy
> appender.audit_log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.audit_log_file.policies.cron.evaluateOnStartup = true
> appender.audit_log_file.strategy.type = DefaultRolloverStrategy
> appender.audit_log_file.strategy.max = 5 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4531) Limit logfile output by default
[
https://issues.apache.org/jira/browse/ARTEMIS-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798650#comment-17798650
]
Geert Schuring commented on ARTEMIS-4531:
-
Created the pull request: https://github.com/apache/activemq-artemis/pull/4718
> Limit logfile output by default
> ---
>
> Key: ARTEMIS-4531
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4531
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 2.31.2
>Reporter: Geert Schuring
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The logging config does not limit the amount of rolled-over logfiles that are
> stored, causing a minor resource leak. The system will (eventually) run out
> of disk space without manual intervention.
> The relevant config in etc/log4j2.properties currently looks like this:
> {code:java}
> # Log file appender
> appender.log_file.type = RollingFile
> appender.log_file.name = log_file
> appender.log_file.fileName = ${sys:artemis.instance}/log/artemis.log
> appender.log_file.filePattern =
> ${sys:artemis.instance}/log/artemis.log.%d{-MM-dd}
> appender.log_file.layout.type = PatternLayout
> appender.log_file.layout.pattern = %d %-5level [%logger] %msg%n
> appender.log_file.policies.type = Policies
> appender.log_file.policies.cron.type = CronTriggeringPolicy
> appender.log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.log_file.policies.cron.evaluateOnStartup = true
> # Audit log file appender
> appender.audit_log_file.type = RollingFile
> appender.audit_log_file.name = audit_log_file
> appender.audit_log_file.fileName = ${sys:artemis.instance}/log/audit.log
> appender.audit_log_file.filePattern =
> ${sys:artemis.instance}/log/audit.log.%d{-MM-dd}
> appender.audit_log_file.layout.type = PatternLayout
> appender.audit_log_file.layout.pattern = %d [AUDIT](%t) %msg%n
> appender.audit_log_file.policies.type = Policies
> appender.audit_log_file.policies.cron.type = CronTriggeringPolicy
> appender.audit_log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.audit_log_file.policies.cron.evaluateOnStartup = true{code}
> This results in a new log file every day if there is any logging output.
> These files are never deleted and keep accumulating.
> After setting a limit of 5 files it looks like this:
> {code:java}
> # Log file appender
> appender.log_file.type = RollingFile
> appender.log_file.name = log_file
> appender.log_file.fileName = ${sys:artemis.instance}/log/artemis.log
> appender.log_file.filePattern =
> ${sys:artemis.instance}/log/artemis.log.%d{-MM-dd}
> appender.log_file.layout.type = PatternLayout
> appender.log_file.layout.pattern = %d %-5level [%logger] %msg%n
> appender.log_file.policies.type = Policies
> appender.log_file.policies.cron.type = CronTriggeringPolicy
> appender.log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.log_file.policies.cron.evaluateOnStartup = true
> appender.log_file.strategy.type = DefaultRolloverStrategy
> appender.log_file.strategy.max = 5
> # Audit log file appender
> appender.audit_log_file.type = RollingFile
> appender.audit_log_file.name = audit_log_file
> appender.audit_log_file.fileName = ${sys:artemis.instance}/log/audit.log
> appender.audit_log_file.filePattern =
> ${sys:artemis.instance}/log/audit.log.%d{-MM-dd}
> appender.audit_log_file.layout.type = PatternLayout
> appender.audit_log_file.layout.pattern = %d [AUDIT](%t) %msg%n
> appender.audit_log_file.policies.type = Policies
> appender.audit_log_file.policies.cron.type = CronTriggeringPolicy
> appender.audit_log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.audit_log_file.policies.cron.evaluateOnStartup = true
> appender.audit_log_file.strategy.type = DefaultRolloverStrategy
> appender.audit_log_file.strategy.max = 5 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] (ARTEMIS-4531) Limit logfile output by default
[ https://issues.apache.org/jira/browse/ARTEMIS-4531 ]
Geert Schuring deleted comment on ARTEMIS-4531:
-
was (Author: cathodion):
I've created the pullrequest, but 5 minutes later I see one of my servers
writing more then the configured amount of log files... so lets hold off on
this change for a sec while I do some more testing just to be sure.
> Limit logfile output by default
> ---
>
> Key: ARTEMIS-4531
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4531
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 2.31.2
>Reporter: Geert Schuring
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The logging config does not limit the amount of rolled-over logfiles that are
> stored, causing a minor resource leak. The system will (eventually) run out
> of disk space without manual intervention.
> The relevant config in etc/log4j2.properties currently looks like this:
> {code:java}
> # Log file appender
> appender.log_file.type = RollingFile
> appender.log_file.name = log_file
> appender.log_file.fileName = ${sys:artemis.instance}/log/artemis.log
> appender.log_file.filePattern =
> ${sys:artemis.instance}/log/artemis.log.%d{-MM-dd}
> appender.log_file.layout.type = PatternLayout
> appender.log_file.layout.pattern = %d %-5level [%logger] %msg%n
> appender.log_file.policies.type = Policies
> appender.log_file.policies.cron.type = CronTriggeringPolicy
> appender.log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.log_file.policies.cron.evaluateOnStartup = true
> # Audit log file appender
> appender.audit_log_file.type = RollingFile
> appender.audit_log_file.name = audit_log_file
> appender.audit_log_file.fileName = ${sys:artemis.instance}/log/audit.log
> appender.audit_log_file.filePattern =
> ${sys:artemis.instance}/log/audit.log.%d{-MM-dd}
> appender.audit_log_file.layout.type = PatternLayout
> appender.audit_log_file.layout.pattern = %d [AUDIT](%t) %msg%n
> appender.audit_log_file.policies.type = Policies
> appender.audit_log_file.policies.cron.type = CronTriggeringPolicy
> appender.audit_log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.audit_log_file.policies.cron.evaluateOnStartup = true{code}
> This results in a new log file every day if there is any logging output.
> These files are never deleted and keep accumulating.
> After setting a limit of 5 files it looks like this:
> {code:java}
> # Log file appender
> appender.log_file.type = RollingFile
> appender.log_file.name = log_file
> appender.log_file.fileName = ${sys:artemis.instance}/log/artemis.log
> appender.log_file.filePattern =
> ${sys:artemis.instance}/log/artemis.log.%d{-MM-dd}
> appender.log_file.layout.type = PatternLayout
> appender.log_file.layout.pattern = %d %-5level [%logger] %msg%n
> appender.log_file.policies.type = Policies
> appender.log_file.policies.cron.type = CronTriggeringPolicy
> appender.log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.log_file.policies.cron.evaluateOnStartup = true
> appender.log_file.strategy.type = DefaultRolloverStrategy
> appender.log_file.strategy.max = 5
> # Audit log file appender
> appender.audit_log_file.type = RollingFile
> appender.audit_log_file.name = audit_log_file
> appender.audit_log_file.fileName = ${sys:artemis.instance}/log/audit.log
> appender.audit_log_file.filePattern =
> ${sys:artemis.instance}/log/audit.log.%d{-MM-dd}
> appender.audit_log_file.layout.type = PatternLayout
> appender.audit_log_file.layout.pattern = %d [AUDIT](%t) %msg%n
> appender.audit_log_file.policies.type = Policies
> appender.audit_log_file.policies.cron.type = CronTriggeringPolicy
> appender.audit_log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.audit_log_file.policies.cron.evaluateOnStartup = true
> appender.audit_log_file.strategy.type = DefaultRolloverStrategy
> appender.audit_log_file.strategy.max = 5 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4531) Limit logfile output by default
[
https://issues.apache.org/jira/browse/ARTEMIS-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798642#comment-17798642
]
Geert Schuring commented on ARTEMIS-4531:
-
I've created the pullrequest, but 5 minutes later I see one of my servers
writing more then the configured amount of log files... so lets hold off on
this change for a sec while I do some more testing just to be sure.
> Limit logfile output by default
> ---
>
> Key: ARTEMIS-4531
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4531
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 2.31.2
>Reporter: Geert Schuring
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The logging config does not limit the amount of rolled-over logfiles that are
> stored, causing a minor resource leak. The system will (eventually) run out
> of disk space without manual intervention.
> The relevant config in etc/log4j2.properties currently looks like this:
> {code:java}
> # Log file appender
> appender.log_file.type = RollingFile
> appender.log_file.name = log_file
> appender.log_file.fileName = ${sys:artemis.instance}/log/artemis.log
> appender.log_file.filePattern =
> ${sys:artemis.instance}/log/artemis.log.%d{-MM-dd}
> appender.log_file.layout.type = PatternLayout
> appender.log_file.layout.pattern = %d %-5level [%logger] %msg%n
> appender.log_file.policies.type = Policies
> appender.log_file.policies.cron.type = CronTriggeringPolicy
> appender.log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.log_file.policies.cron.evaluateOnStartup = true
> # Audit log file appender
> appender.audit_log_file.type = RollingFile
> appender.audit_log_file.name = audit_log_file
> appender.audit_log_file.fileName = ${sys:artemis.instance}/log/audit.log
> appender.audit_log_file.filePattern =
> ${sys:artemis.instance}/log/audit.log.%d{-MM-dd}
> appender.audit_log_file.layout.type = PatternLayout
> appender.audit_log_file.layout.pattern = %d [AUDIT](%t) %msg%n
> appender.audit_log_file.policies.type = Policies
> appender.audit_log_file.policies.cron.type = CronTriggeringPolicy
> appender.audit_log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.audit_log_file.policies.cron.evaluateOnStartup = true{code}
> This results in a new log file every day if there is any logging output.
> These files are never deleted and keep accumulating.
> After setting a limit of 5 files it looks like this:
> {code:java}
> # Log file appender
> appender.log_file.type = RollingFile
> appender.log_file.name = log_file
> appender.log_file.fileName = ${sys:artemis.instance}/log/artemis.log
> appender.log_file.filePattern =
> ${sys:artemis.instance}/log/artemis.log.%d{-MM-dd}
> appender.log_file.layout.type = PatternLayout
> appender.log_file.layout.pattern = %d %-5level [%logger] %msg%n
> appender.log_file.policies.type = Policies
> appender.log_file.policies.cron.type = CronTriggeringPolicy
> appender.log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.log_file.policies.cron.evaluateOnStartup = true
> appender.log_file.strategy.type = DefaultRolloverStrategy
> appender.log_file.strategy.max = 5
> # Audit log file appender
> appender.audit_log_file.type = RollingFile
> appender.audit_log_file.name = audit_log_file
> appender.audit_log_file.fileName = ${sys:artemis.instance}/log/audit.log
> appender.audit_log_file.filePattern =
> ${sys:artemis.instance}/log/audit.log.%d{-MM-dd}
> appender.audit_log_file.layout.type = PatternLayout
> appender.audit_log_file.layout.pattern = %d [AUDIT](%t) %msg%n
> appender.audit_log_file.policies.type = Policies
> appender.audit_log_file.policies.cron.type = CronTriggeringPolicy
> appender.audit_log_file.policies.cron.schedule = 0 0 0 * * ?
> appender.audit_log_file.policies.cron.evaluateOnStartup = true
> appender.audit_log_file.strategy.type = DefaultRolloverStrategy
> appender.audit_log_file.strategy.max = 5 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARTEMIS-4531) There is no limit to logfile output
Geert Schuring created ARTEMIS-4531:
---
Summary: There is no limit to logfile output
Key: ARTEMIS-4531
URL: https://issues.apache.org/jira/browse/ARTEMIS-4531
Project: ActiveMQ Artemis
Issue Type: Bug
Components: Broker
Affects Versions: 2.31.2
Reporter: Geert Schuring
The logging config does not limit the amount of rolled-over logfiles that are
stored, causing a minor resource leak. The system will (eventually) run out of
disk space without manual intervention.
The relevant config in etc/log4j2.properties currently looks like this:
{code:java}
# Log file appender
appender.log_file.type = RollingFile
appender.log_file.name = log_file
appender.log_file.fileName = ${sys:artemis.instance}/log/artemis.log
appender.log_file.filePattern =
${sys:artemis.instance}/log/artemis.log.%d{-MM-dd}
appender.log_file.layout.type = PatternLayout
appender.log_file.layout.pattern = %d %-5level [%logger] %msg%n
appender.log_file.policies.type = Policies
appender.log_file.policies.cron.type = CronTriggeringPolicy
appender.log_file.policies.cron.schedule = 0 0 0 * * ?
appender.log_file.policies.cron.evaluateOnStartup = true
# Audit log file appender
appender.audit_log_file.type = RollingFile
appender.audit_log_file.name = audit_log_file
appender.audit_log_file.fileName = ${sys:artemis.instance}/log/audit.log
appender.audit_log_file.filePattern =
${sys:artemis.instance}/log/audit.log.%d{-MM-dd}
appender.audit_log_file.layout.type = PatternLayout
appender.audit_log_file.layout.pattern = %d [AUDIT](%t) %msg%n
appender.audit_log_file.policies.type = Policies
appender.audit_log_file.policies.cron.type = CronTriggeringPolicy
appender.audit_log_file.policies.cron.schedule = 0 0 0 * * ?
appender.audit_log_file.policies.cron.evaluateOnStartup = true{code}
This results in a new log file every day if there is any logging output. These
files are never deleted and keep accumulating.
After setting a limit of 5 files it looks like this:
{code:java}
# Log file appender
appender.log_file.type = RollingFile
appender.log_file.name = log_file
appender.log_file.fileName = ${sys:artemis.instance}/log/artemis.log
appender.log_file.filePattern =
${sys:artemis.instance}/log/artemis.log.%d{-MM-dd}
appender.log_file.layout.type = PatternLayout
appender.log_file.layout.pattern = %d %-5level [%logger] %msg%n
appender.log_file.policies.type = Policies
appender.log_file.policies.cron.type = CronTriggeringPolicy
appender.log_file.policies.cron.schedule = 0 0 0 * * ?
appender.log_file.policies.cron.evaluateOnStartup = true
appender.log_file.strategy.type = DefaultRolloverStrategy
appender.log_file.strategy.max = 5
# Audit log file appender
appender.audit_log_file.type = RollingFile
appender.audit_log_file.name = audit_log_file
appender.audit_log_file.fileName = ${sys:artemis.instance}/log/audit.log
appender.audit_log_file.filePattern =
${sys:artemis.instance}/log/audit.log.%d{-MM-dd}
appender.audit_log_file.layout.type = PatternLayout
appender.audit_log_file.layout.pattern = %d [AUDIT](%t) %msg%n
appender.audit_log_file.policies.type = Policies
appender.audit_log_file.policies.cron.type = CronTriggeringPolicy
appender.audit_log_file.policies.cron.schedule = 0 0 0 * * ?
appender.audit_log_file.policies.cron.evaluateOnStartup = true
appender.audit_log_file.strategy.type = DefaultRolloverStrategy
appender.audit_log_file.strategy.max = 5 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4483) Log.warn messages with AMQP during regular closing of AMQP clients.
[ https://issues.apache.org/jira/browse/ARTEMIS-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796338#comment-17796338 ] Geert Schuring commented on ARTEMIS-4483: - I was about to log this issue, so thanks for fixing it! > Log.warn messages with AMQP during regular closing of AMQP clients. > --- > > Key: ARTEMIS-4483 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4483 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.31.2 >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Fix For: 2.32.0 > > Time Spent: 20m > Remaining Estimate: 0h > > As I was fixing ARTEMIS-4476, I realized why regular closes in AMQP are > throwing log.warn in the log for cleaning up sessions and even invalid > connections at certain points. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4381) resource-limit-settings max-connections should be called max-sessions
[
https://issues.apache.org/jira/browse/ARTEMIS-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geert Schuring updated ARTEMIS-4381:
Description:
The configuration setting "max-connections" should be called "max-sessions"
since it limits the amounts of sessions and not the connections.
[https://activemq.apache.org/components/artemis/documentation/latest/resource-limits.html#configuring-limits-via-resource-limit-settings]
After having limited the 'connections' using this setting I get the following
error even though this user has only 1 connection to the broker: (it does try
to create more then 1 sessions)
{quote}{{AMQ229110: Too many sessions for user 'user'}}
{quote}
was:
The configuration setting "max-connections" should be called "max-sessions"
since it limits the amounts of sessions and not the connections.
[https://activemq.apache.org/components/artemis/documentation/latest/resource-limits.html#configuring-limits-via-resource-limit-settings]
> resource-limit-settings max-connections should be called max-sessions
> -
>
> Key: ARTEMIS-4381
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4381
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.28.0
>Reporter: Geert Schuring
>Priority: Major
>
> The configuration setting "max-connections" should be called "max-sessions"
> since it limits the amounts of sessions and not the connections.
>
> [https://activemq.apache.org/components/artemis/documentation/latest/resource-limits.html#configuring-limits-via-resource-limit-settings]
> After having limited the 'connections' using this setting I get the following
> error even though this user has only 1 connection to the broker: (it does try
> to create more then 1 sessions)
> {quote}{{AMQ229110: Too many sessions for user 'user'}}
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARTEMIS-4381) resource-limit-settings max-connections should be called max-sessions
Geert Schuring created ARTEMIS-4381: --- Summary: resource-limit-settings max-connections should be called max-sessions Key: ARTEMIS-4381 URL: https://issues.apache.org/jira/browse/ARTEMIS-4381 Project: ActiveMQ Artemis Issue Type: Bug Components: Broker Affects Versions: 2.28.0 Reporter: Geert Schuring The configuration setting "max-connections" should be called "max-sessions" since it limits the amounts of sessions and not the connections. [https://activemq.apache.org/components/artemis/documentation/latest/resource-limits.html#configuring-limits-via-resource-limit-settings] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-4379) Multiple Failover Failback example missing
[ https://issues.apache.org/jira/browse/ARTEMIS-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geert Schuring closed ARTEMIS-4379. --- This isssue is an unintended clone of another identical issue. This one should be deleted. > Multiple Failover Failback example missing > -- > > Key: ARTEMIS-4379 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4379 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.28.0 >Reporter: Geert Schuring >Priority: Major > Labels: examples, failback > > The code for example "Multiple Failover Failback" is the exact same as > "Multiple Failover" while it should show how to make sure clients revert back > to the master broker as soon as it comes back online. > Compare these two: > # > [https://raw.githubusercontent.com/apache/activemq-artemis/main/examples/features/ha/multiple-failover/src/main/java/org/apache/activemq/artemis/jms/example/MultipleFailoverExample.java] > # > [https://raw.githubusercontent.com/apache/activemq-artemis/main/examples/features/ha/multiple-failover-failback/src/main/java/org/apache/activemq/artemis/jms/example/MultipleFailoverFailbackExample.java] > There's not meaningfull difference between them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4379) Multiple Failover Failback example missing
[ https://issues.apache.org/jira/browse/ARTEMIS-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geert Schuring resolved ARTEMIS-4379. - Fix Version/s: (was: 2.30.0) Resolution: Duplicate > Multiple Failover Failback example missing > -- > > Key: ARTEMIS-4379 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4379 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.28.0 >Reporter: Geert Schuring >Priority: Major > Labels: examples, failback > > The code for example "Multiple Failover Failback" is the exact same as > "Multiple Failover" while it should show how to make sure clients revert back > to the master broker as soon as it comes back online. > Compare these two: > # > [https://raw.githubusercontent.com/apache/activemq-artemis/main/examples/features/ha/multiple-failover/src/main/java/org/apache/activemq/artemis/jms/example/MultipleFailoverExample.java] > # > [https://raw.githubusercontent.com/apache/activemq-artemis/main/examples/features/ha/multiple-failover-failback/src/main/java/org/apache/activemq/artemis/jms/example/MultipleFailoverFailbackExample.java] > There's not meaningfull difference between them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4380) Multiple Failover Failback example missing
[ https://issues.apache.org/jira/browse/ARTEMIS-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geert Schuring updated ARTEMIS-4380: Description: The code for example "Multiple Failover Failback" is the exact same as "Multiple Failover" while it should show how to make sure clients revert back to the master broker as soon as it comes back online. Compare these two: # [https://raw.githubusercontent.com/apache/activemq-artemis/main/examples/features/ha/multiple-failover/src/main/java/org/apache/activemq/artemis/jms/example/MultipleFailoverExample.java] # [https://raw.githubusercontent.com/apache/activemq-artemis/main/examples/features/ha/multiple-failover-failback/src/main/java/org/apache/activemq/artemis/jms/example/MultipleFailoverFailbackExample.java] There's no meaningfull difference between them, unless I'm misunderstanding something. In any case, the axample does not tell me how to achieve failback. was: The code for example "Multiple Failover Failback" is the exact same as "Multiple Failover" while it should show how to make sure clients revert back to the master broker as soon as it comes back online. Compare these two: # [https://raw.githubusercontent.com/apache/activemq-artemis/main/examples/features/ha/multiple-failover/src/main/java/org/apache/activemq/artemis/jms/example/MultipleFailoverExample.java] # [https://raw.githubusercontent.com/apache/activemq-artemis/main/examples/features/ha/multiple-failover-failback/src/main/java/org/apache/activemq/artemis/jms/example/MultipleFailoverFailbackExample.java] There's not meaningfull difference between them. > Multiple Failover Failback example missing > -- > > Key: ARTEMIS-4380 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4380 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.28.0 >Reporter: Geert Schuring >Priority: Major > Labels: examples, failback > Fix For: 2.30.0 > > > The code for example "Multiple Failover Failback" is the exact same as > "Multiple Failover" while it should show how to make sure clients revert back > to the master broker as soon as it comes back online. > Compare these two: > # > [https://raw.githubusercontent.com/apache/activemq-artemis/main/examples/features/ha/multiple-failover/src/main/java/org/apache/activemq/artemis/jms/example/MultipleFailoverExample.java] > # > [https://raw.githubusercontent.com/apache/activemq-artemis/main/examples/features/ha/multiple-failover-failback/src/main/java/org/apache/activemq/artemis/jms/example/MultipleFailoverFailbackExample.java] > There's no meaningfull difference between them, unless I'm misunderstanding > something. In any case, the axample does not tell me how to achieve failback. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4380) Multiple Failover Failback example missing
Geert Schuring created ARTEMIS-4380: --- Summary: Multiple Failover Failback example missing Key: ARTEMIS-4380 URL: https://issues.apache.org/jira/browse/ARTEMIS-4380 Project: ActiveMQ Artemis Issue Type: Bug Affects Versions: 2.28.0 Reporter: Geert Schuring Fix For: 2.30.0 The code for example "Multiple Failover Failback" is the exact same as "Multiple Failover" while it should show how to make sure clients revert back to the master broker as soon as it comes back online. Compare these two: # [https://raw.githubusercontent.com/apache/activemq-artemis/main/examples/features/ha/multiple-failover/src/main/java/org/apache/activemq/artemis/jms/example/MultipleFailoverExample.java] # [https://raw.githubusercontent.com/apache/activemq-artemis/main/examples/features/ha/multiple-failover-failback/src/main/java/org/apache/activemq/artemis/jms/example/MultipleFailoverFailbackExample.java] There's not meaningfull difference between them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-4219) Publish official docker image
[ https://issues.apache.org/jira/browse/ARTEMIS-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17734209#comment-17734209 ] Geert Schuring edited comment on ARTEMIS-4219 at 6/19/23 2:11 PM: -- Totally agree. After searching for a long time I still feel like "there must be an official image that I'm missing here right?" I do not consider this a trivial issue, but rather a major one. was (Author: cathodion): Totally agree. After searching for a long time I still feel like "there must be an official image that I'm missing here right?" > Publish official docker image > -- > > Key: ARTEMIS-4219 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4219 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Reporter: Eddú Meléndez >Priority: Trivial > > It would be great to have an official docker image which can be used to write > integration tests with Testcontainers. Also, with approaches such as Quarkus > DevServices and Micronaut Test-resources, built on top of Testcontainers > would help to have a broker up and running in dev mode with no configuration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4219) Publish official docker image
[ https://issues.apache.org/jira/browse/ARTEMIS-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17734209#comment-17734209 ] Geert Schuring commented on ARTEMIS-4219: - Totally agree. After searching for a long time I still feel like "there must be an official image that I'm missing here right?" > Publish official docker image > -- > > Key: ARTEMIS-4219 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4219 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Reporter: Eddú Meléndez >Priority: Trivial > > It would be great to have an official docker image which can be used to write > integration tests with Testcontainers. Also, with approaches such as Quarkus > DevServices and Micronaut Test-resources, built on top of Testcontainers > would help to have a broker up and running in dev mode with no configuration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4318) Architecture documentation links to depricated library "Airline"
Geert Schuring created ARTEMIS-4318: --- Summary: Architecture documentation links to depricated library "Airline" Key: ARTEMIS-4318 URL: https://issues.apache.org/jira/browse/ARTEMIS-4318 Project: ActiveMQ Artemis Issue Type: Bug Affects Versions: 2.28.0 Reporter: Geert Schuring Fix For: 2.29.0 There's a link on this page (under "Stand-alone Broker") to a project called "Airline" which is depricated: https://activemq.apache.org/components/artemis/documentation/latest/architecture.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4316) Example HTML does not render correctly
Geert Schuring created ARTEMIS-4316: --- Summary: Example HTML does not render correctly Key: ARTEMIS-4316 URL: https://issues.apache.org/jira/browse/ARTEMIS-4316 Project: ActiveMQ Artemis Issue Type: Bug Affects Versions: 2.28.0 Reporter: Geert Schuring Fix For: 2.29.0 Attachments: image-2023-06-16-10-43-45-924.png The HTML files in the examples do not render correctly. Especially the code parts. For example, the Readme in the CDI example: apache-artemis-2.28.0/examples/features/standard/cdi/readme.html !image-2023-06-16-10-43-45-924.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4311) Strange typo propagated throughout the codebase: "Mesasge"
Geert Schuring created ARTEMIS-4311: --- Summary: Strange typo propagated throughout the codebase: "Mesasge" Key: ARTEMIS-4311 URL: https://issues.apache.org/jira/browse/ARTEMIS-4311 Project: ActiveMQ Artemis Issue Type: Bug Affects Versions: 2.28.0 Reporter: Geert Schuring Fix For: 2.29.0 Somehow the same typo appears in 23 files. See [https://github.com/search?q=repo%3Aapache%2Factivemq-artemis%20mesasge=code] Nothing major, but a bit cringe to see this in the config of every broker I create :) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9126) Jolokia throws exception during startup
[
https://issues.apache.org/jira/browse/AMQ-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17626186#comment-17626186
]
Geert Schuring commented on AMQ-9126:
-
[~jbonofre] Thanks for the feedback! Quick reponses like this are what makes it
worth-while to halt my work for a minute and report things I think might be
worth reporting.
[~Sreeni] No problem man. No offense taken. I rather see people responding than
ignoring to my reports. :)
> Jolokia throws exception during startup
> ---
>
> Key: AMQ-9126
> URL: https://issues.apache.org/jira/browse/AMQ-9126
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 5.17.2
> Environment: Windows 10
> Java 11
>Reporter: Geert Schuring
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 5.18.0, 5.17.3
>
>
> During startup of a freshly downloaded activemq-5.17.2 for windows the
> jolokia agent scrambles up the path of the jolokia-access.xml file, fails to
> open it, and throws an exception:
> {code:java}
> C:\Tools\Brokers\apache-activemq-5.17.2>bin\activemq start
> Java Runtime: AdoptOpenJDK 11.0.7 C:\Tools\Java\jdk-11.0.7.10-hotspot
> Heap sizes: current=1048576k free=1040894k max=1048576k
> JVM args: -Dcom.sun.management.jmxremote -Xms1G -Xmx1G
> -Djava.util.logging.config.file=logging.properties
> -Djava.security.auth.login.config=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\conf\login.config
>
> -Dactivemq.classpath=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\conf;C:\Tools\Brokers\apache-activemq-5.17.2\bin\../conf;C:\Tools\Brokers\apache-activemq-5.17.2\bin\../conf;
> -Dactivemq.home=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..
> -Dactivemq.base=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..
> -Dactivemq.conf=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\conf
> -Dactivemq.data=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data
> -Djava.io.tmpdir=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data\tmp
> Extensions classpath:
>
> [C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\lib,C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\lib\camel,C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\lib\optional,C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\lib\web,C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\lib\extra]
> ACTIVEMQ_HOME: C:\Tools\Brokers\apache-activemq-5.17.2\bin\..
> ACTIVEMQ_BASE: C:\Tools\Brokers\apache-activemq-5.17.2\bin\..
> ACTIVEMQ_CONF: C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\conf
> ACTIVEMQ_DATA: C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data
> Loading message broker from: xbean:activemq.xml
> INFO | Using Persistence Adapter:
> KahaDBPersistenceAdapter[C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data\kahadb]
> INFO |
> PListStore:[C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data\localhost\tmp_storage]
> started
> INFO | Apache ActiveMQ 5.17.2 (localhost,
> ID:DESKTOP-ENEPHES-56664-1666030664750-0:1) is starting
> INFO | Listening for connections at:
> tcp://DESKTOP-ENEPHES:61616?maximumConnections=1000=104857600
> INFO | Connector openwire started
> INFO | Listening for connections at:
> amqp://DESKTOP-ENEPHES:5672?maximumConnections=1000=104857600
> INFO | Connector amqp started
> INFO | Listening for connections at:
> stomp://DESKTOP-ENEPHES:61613?maximumConnections=1000=104857600
> INFO | Connector stomp started
> INFO | Listening for connections at:
> mqtt://DESKTOP-ENEPHES:1883?maximumConnections=1000=104857600
> INFO | Connector mqtt started
> INFO | Starting Jetty server
> INFO | Creating Jetty connector
> WARN |
> ServletContext@o.e.j.s.ServletContextHandler@58437801{/,null,STARTING} has
> uncovered http methods for path: /
> INFO | Listening for connections at
> ws://DESKTOP-ENEPHES:61614?maximumConnections=1000=104857600
> INFO | Connector ws started
> INFO | Apache ActiveMQ 5.17.2 (localhost,
> ID:DESKTOP-ENEPHES-56664-1666030664750-0:1) started
> INFO | For help or more information please see: http://activemq.apache.org
> WARN | Store limit is 102400 mb (current store usage is 0 mb). The data
> directory: C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data\kahadb only
> has 95573 mb of usable space. - resetting to maximum available disk space:
> 95573 mb
> INFO | ActiveMQ WebConsole available at http://127.0.0.1:8161/
> INFO | ActiveMQ Jolokia REST API available at
> http://127.0.0.1:8161/api/jolokia/
> WARN | jolokia-agent: Error while accessing access restrictor at
> file:C:ToolsBrokersapache-activemq-5.17.2bin..conf/jolokia-access.xml.
> Denying all access to MBeans for security reasons. Exception:
> java.io.FileNotFoundException:
> C:ToolsBrokersapache-activemq-5.17.2bin..conf\jolokia-access.xml (Het systeem
> kan het opgegeven pad niet vinden)
> {code}
> It seems to have
[jira] [Commented] (AMQ-9126) Jolokia throws exception during startup
[
https://issues.apache.org/jira/browse/AMQ-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625742#comment-17625742
]
Geert Schuring commented on AMQ-9126:
-
[~Sreeni] You're missing the point of my bug report. Users should not have to
start googling solutions to know problems in the latest version of any product.
We/they should solve the problem at the core. I'm reporting it because I'm
guessing it might have eluded the developers attention.
> Jolokia throws exception during startup
> ---
>
> Key: AMQ-9126
> URL: https://issues.apache.org/jira/browse/AMQ-9126
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 5.17.2
> Environment: Windows 10
> Java 11
>Reporter: Geert Schuring
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 5.18.0, 5.17.3
>
>
> During startup of a freshly downloaded activemq-5.17.2 for windows the
> jolokia agent scrambles up the path of the jolokia-access.xml file, fails to
> open it, and throws an exception:
> {code:java}
> C:\Tools\Brokers\apache-activemq-5.17.2>bin\activemq start
> Java Runtime: AdoptOpenJDK 11.0.7 C:\Tools\Java\jdk-11.0.7.10-hotspot
> Heap sizes: current=1048576k free=1040894k max=1048576k
> JVM args: -Dcom.sun.management.jmxremote -Xms1G -Xmx1G
> -Djava.util.logging.config.file=logging.properties
> -Djava.security.auth.login.config=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\conf\login.config
>
> -Dactivemq.classpath=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\conf;C:\Tools\Brokers\apache-activemq-5.17.2\bin\../conf;C:\Tools\Brokers\apache-activemq-5.17.2\bin\../conf;
> -Dactivemq.home=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..
> -Dactivemq.base=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..
> -Dactivemq.conf=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\conf
> -Dactivemq.data=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data
> -Djava.io.tmpdir=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data\tmp
> Extensions classpath:
>
> [C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\lib,C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\lib\camel,C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\lib\optional,C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\lib\web,C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\lib\extra]
> ACTIVEMQ_HOME: C:\Tools\Brokers\apache-activemq-5.17.2\bin\..
> ACTIVEMQ_BASE: C:\Tools\Brokers\apache-activemq-5.17.2\bin\..
> ACTIVEMQ_CONF: C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\conf
> ACTIVEMQ_DATA: C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data
> Loading message broker from: xbean:activemq.xml
> INFO | Using Persistence Adapter:
> KahaDBPersistenceAdapter[C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data\kahadb]
> INFO |
> PListStore:[C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data\localhost\tmp_storage]
> started
> INFO | Apache ActiveMQ 5.17.2 (localhost,
> ID:DESKTOP-ENEPHES-56664-1666030664750-0:1) is starting
> INFO | Listening for connections at:
> tcp://DESKTOP-ENEPHES:61616?maximumConnections=1000=104857600
> INFO | Connector openwire started
> INFO | Listening for connections at:
> amqp://DESKTOP-ENEPHES:5672?maximumConnections=1000=104857600
> INFO | Connector amqp started
> INFO | Listening for connections at:
> stomp://DESKTOP-ENEPHES:61613?maximumConnections=1000=104857600
> INFO | Connector stomp started
> INFO | Listening for connections at:
> mqtt://DESKTOP-ENEPHES:1883?maximumConnections=1000=104857600
> INFO | Connector mqtt started
> INFO | Starting Jetty server
> INFO | Creating Jetty connector
> WARN |
> ServletContext@o.e.j.s.ServletContextHandler@58437801{/,null,STARTING} has
> uncovered http methods for path: /
> INFO | Listening for connections at
> ws://DESKTOP-ENEPHES:61614?maximumConnections=1000=104857600
> INFO | Connector ws started
> INFO | Apache ActiveMQ 5.17.2 (localhost,
> ID:DESKTOP-ENEPHES-56664-1666030664750-0:1) started
> INFO | For help or more information please see: http://activemq.apache.org
> WARN | Store limit is 102400 mb (current store usage is 0 mb). The data
> directory: C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data\kahadb only
> has 95573 mb of usable space. - resetting to maximum available disk space:
> 95573 mb
> INFO | ActiveMQ WebConsole available at http://127.0.0.1:8161/
> INFO | ActiveMQ Jolokia REST API available at
> http://127.0.0.1:8161/api/jolokia/
> WARN | jolokia-agent: Error while accessing access restrictor at
> file:C:ToolsBrokersapache-activemq-5.17.2bin..conf/jolokia-access.xml.
> Denying all access to MBeans for security reasons. Exception:
> java.io.FileNotFoundException:
> C:ToolsBrokersapache-activemq-5.17.2bin..conf\jolokia-access.xml (Het systeem
> kan het opgegeven pad niet vinden)
> {code}
> It seems to
[jira] [Updated] (AMQ-9126) Jolokia throws exception during startup
[
https://issues.apache.org/jira/browse/AMQ-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geert Schuring updated AMQ-9126:
Description:
During startup of a freshly downloaded activemq-5.17.2 for windows the jolokia
agent scrambles up the path of the jolokia-access.xml file, fails to open it,
and throws an exception:
{code:java}
C:\Tools\Brokers\apache-activemq-5.17.2>bin\activemq start
Java Runtime: AdoptOpenJDK 11.0.7 C:\Tools\Java\jdk-11.0.7.10-hotspot
Heap sizes: current=1048576k free=1040894k max=1048576k
JVM args: -Dcom.sun.management.jmxremote -Xms1G -Xmx1G
-Djava.util.logging.config.file=logging.properties
-Djava.security.auth.login.config=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\conf\login.config
-Dactivemq.classpath=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\conf;C:\Tools\Brokers\apache-activemq-5.17.2\bin\../conf;C:\Tools\Brokers\apache-activemq-5.17.2\bin\../conf;
-Dactivemq.home=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..
-Dactivemq.base=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..
-Dactivemq.conf=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\conf
-Dactivemq.data=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data
-Djava.io.tmpdir=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data\tmp
Extensions classpath:
[C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\lib,C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\lib\camel,C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\lib\optional,C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\lib\web,C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\lib\extra]
ACTIVEMQ_HOME: C:\Tools\Brokers\apache-activemq-5.17.2\bin\..
ACTIVEMQ_BASE: C:\Tools\Brokers\apache-activemq-5.17.2\bin\..
ACTIVEMQ_CONF: C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\conf
ACTIVEMQ_DATA: C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data
Loading message broker from: xbean:activemq.xml
INFO | Using Persistence Adapter:
KahaDBPersistenceAdapter[C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data\kahadb]
INFO |
PListStore:[C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data\localhost\tmp_storage]
started
INFO | Apache ActiveMQ 5.17.2 (localhost,
ID:DESKTOP-ENEPHES-56664-1666030664750-0:1) is starting
INFO | Listening for connections at:
tcp://DESKTOP-ENEPHES:61616?maximumConnections=1000=104857600
INFO | Connector openwire started
INFO | Listening for connections at:
amqp://DESKTOP-ENEPHES:5672?maximumConnections=1000=104857600
INFO | Connector amqp started
INFO | Listening for connections at:
stomp://DESKTOP-ENEPHES:61613?maximumConnections=1000=104857600
INFO | Connector stomp started
INFO | Listening for connections at:
mqtt://DESKTOP-ENEPHES:1883?maximumConnections=1000=104857600
INFO | Connector mqtt started
INFO | Starting Jetty server
INFO | Creating Jetty connector
WARN | ServletContext@o.e.j.s.ServletContextHandler@58437801{/,null,STARTING}
has uncovered http methods for path: /
INFO | Listening for connections at
ws://DESKTOP-ENEPHES:61614?maximumConnections=1000=104857600
INFO | Connector ws started
INFO | Apache ActiveMQ 5.17.2 (localhost,
ID:DESKTOP-ENEPHES-56664-1666030664750-0:1) started
INFO | For help or more information please see: http://activemq.apache.org
WARN | Store limit is 102400 mb (current store usage is 0 mb). The data
directory: C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data\kahadb only has
95573 mb of usable space. - resetting to maximum available disk space: 95573 mb
INFO | ActiveMQ WebConsole available at http://127.0.0.1:8161/
INFO | ActiveMQ Jolokia REST API available at
http://127.0.0.1:8161/api/jolokia/
WARN | jolokia-agent: Error while accessing access restrictor at
file:C:ToolsBrokersapache-activemq-5.17.2bin..conf/jolokia-access.xml. Denying
all access to MBeans for security reasons. Exception:
java.io.FileNotFoundException:
C:ToolsBrokersapache-activemq-5.17.2bin..conf\jolokia-access.xml (Het systeem
kan het opgegeven pad niet vinden)
{code}
It seems to have removed the slashes from the base path somehow.
No files have been changed after unpacking the zip distribution.
was:
During startup of a freshly downloaded activemq-5.17.2 for windows the jolokia
agent scrambles up the path of the jolokia-access.xml file, fails to open it,
and throws an exception:
{code:java}
C:\Tools\Brokers\apache-activemq-5.17.2>bin\activemq start
Java Runtime: AdoptOpenJDK 11.0.7 C:\Tools\Java\jdk-11.0.7.10-hotspot
Heap sizes: current=1048576k free=1040894k max=1048576k
JVM args: -Dcom.sun.management.jmxremote -Xms1G -Xmx1G
-Djava.util.logging.config.file=logging.properties
-Djava.security.auth.login.config=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\conf\login.config
-Dactivemq.classpath=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\conf;C:\Tools\Brokers\apache-activemq-5.17.2\bin\../conf;C:\Tools\Brokers\apache-activemq-5.17.2\bin\../conf;
[jira] [Updated] (AMQ-9126) Jolokia throws exception during startup
[
https://issues.apache.org/jira/browse/AMQ-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geert Schuring updated AMQ-9126:
Description:
During startup of a freshly downloaded activemq-5.17.2 for windows the jolokia
agent scrambles up the path of the jolokia-access.xml file, fails to open it,
and throws an exception:
{code:java}
C:\Tools\Brokers\apache-activemq-5.17.2>bin\activemq start
Java Runtime: AdoptOpenJDK 11.0.7 C:\Tools\Java\jdk-11.0.7.10-hotspot
Heap sizes: current=1048576k free=1040894k max=1048576k
JVM args: -Dcom.sun.management.jmxremote -Xms1G -Xmx1G
-Djava.util.logging.config.file=logging.properties
-Djava.security.auth.login.config=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\conf\login.config
-Dactivemq.classpath=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\conf;C:\Tools\Brokers\apache-activemq-5.17.2\bin\../conf;C:\Tools\Brokers\apache-activemq-5.17.2\bin\../conf;
-Dactivemq.home=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..
-Dactivemq.base=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..
-Dactivemq.conf=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\conf
-Dactivemq.data=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data
-Djava.io.tmpdir=C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data\tmp
Extensions classpath:
[C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\lib,C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\lib\camel,C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\lib\optional,C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\lib\web,C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\lib\extra]
ACTIVEMQ_HOME: C:\Tools\Brokers\apache-activemq-5.17.2\bin\..
ACTIVEMQ_BASE: C:\Tools\Brokers\apache-activemq-5.17.2\bin\..
ACTIVEMQ_CONF: C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\conf
ACTIVEMQ_DATA: C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data
Loading message broker from: xbean:activemq.xml
INFO | Using Persistence Adapter:
KahaDBPersistenceAdapter[C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data\kahadb]
INFO |
PListStore:[C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data\localhost\tmp_storage]
started
INFO | Apache ActiveMQ 5.17.2 (localhost,
ID:DESKTOP-ENEPHES-56664-1666030664750-0:1) is starting
INFO | Listening for connections at:
tcp://DESKTOP-ENEPHES:61616?maximumConnections=1000=104857600
INFO | Connector openwire started
INFO | Listening for connections at:
amqp://DESKTOP-ENEPHES:5672?maximumConnections=1000=104857600
INFO | Connector amqp started
INFO | Listening for connections at:
stomp://DESKTOP-ENEPHES:61613?maximumConnections=1000=104857600
INFO | Connector stomp started
INFO | Listening for connections at:
mqtt://DESKTOP-ENEPHES:1883?maximumConnections=1000=104857600
INFO | Connector mqtt started
INFO | Starting Jetty server
INFO | Creating Jetty connector
WARN | ServletContext@o.e.j.s.ServletContextHandler@58437801{/,null,STARTING}
has uncovered http methods for path: /
INFO | Listening for connections at
ws://DESKTOP-ENEPHES:61614?maximumConnections=1000=104857600
INFO | Connector ws started
INFO | Apache ActiveMQ 5.17.2 (localhost,
ID:DESKTOP-ENEPHES-56664-1666030664750-0:1) started
INFO | For help or more information please see: http://activemq.apache.org
WARN | Store limit is 102400 mb (current store usage is 0 mb). The data
directory: C:\Tools\Brokers\apache-activemq-5.17.2\bin\..\data\kahadb only has
95573 mb of usable space. - resetting to maximum available disk space: 95573 mb
INFO | ActiveMQ WebConsole available at http://127.0.0.1:8161/
INFO | ActiveMQ Jolokia REST API available at
http://127.0.0.1:8161/api/jolokia/
WARN | jolokia-agent: Error while accessing access restrictor at
file:C:ToolsBrokersapache-activemq-5.17.2bin..conf/jolokia-access.xml. Denying
all access to MBeans for security reasons. Exception:
java.io.FileNotFoundException:
C:ToolsBrokersapache-activemq-5.17.2bin..conf\jolokia-access.xml (Het systeem
kan het opgegeven pad niet vinden)
java.io.FileNotFoundException:
C:ToolsBrokersapache-activemq-5.17.2bin..conf\jolokia-access.xml (Het systeem
kan het opgegeven pad niet vinden)
{code}
It seems to have removed the slashes from the base path somehow.
No files have been changed after unpacking the zip distribution.
was:
During startup of a freshly downloaded activemq-5.17.2 for windows the jolokia
agent scrambles up the path of the jolokia-access.xml file, fails to open it,
and throws an exception:
{{ WARN | jolokia-agent: Error while accessing access restrictor at
file:C:ToolsBrokersapache-activemq-5.17.2bin..conf/jolokia-access.xml. Denying
all access to MBeans for security reasons. Exception:
java.io.FileNotFoundException:
C:ToolsBrokersapache-activemq-5.17.2bin..conf\jolokia-access.xml (Het systeem
kan het opgegeven pad niet vinden)}}
{{java.io.FileNotFoundException:
C:ToolsBrokersapache-activemq-5.17.2bin..conf\jolokia-access.xml (Het systeem
kan het opgegeven pad niet vinden)}}
[jira] [Created] (AMQ-9126) Jolokia throws exception during startup
Geert Schuring created AMQ-9126:
---
Summary: Jolokia throws exception during startup
Key: AMQ-9126
URL: https://issues.apache.org/jira/browse/AMQ-9126
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.17.2
Environment: Windows 10
Java 11
Reporter: Geert Schuring
Fix For: 5.18.0, 5.17.3
During startup of a freshly downloaded activemq-5.17.2 for windows the jolokia
agent scrambles up the path of the jolokia-access.xml file, fails to open it,
and throws an exception:
{{ WARN | jolokia-agent: Error while accessing access restrictor at
file:C:ToolsBrokersapache-activemq-5.17.2bin..conf/jolokia-access.xml. Denying
all access to MBeans for security reasons. Exception:
java.io.FileNotFoundException:
C:ToolsBrokersapache-activemq-5.17.2bin..conf\jolokia-access.xml (Het systeem
kan het opgegeven pad niet vinden)}}
{{java.io.FileNotFoundException:
C:ToolsBrokersapache-activemq-5.17.2bin..conf\jolokia-access.xml (Het systeem
kan het opgegeven pad niet vinden)}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-8093) Illegal reflective access by IntrospectionSupport
[ https://issues.apache.org/jira/browse/AMQ-8093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490887#comment-17490887 ] Geert Schuring commented on AMQ-8093: - Im running version 5.16.3 and still get this warning. Is there any version of ActiveMQ 5 Client where this is solved? > Illegal reflective access by IntrospectionSupport > - > > Key: AMQ-8093 > URL: https://issues.apache.org/jira/browse/AMQ-8093 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, JMS client >Affects Versions: 5.15.13 > Environment: Java 11 >Reporter: John C >Assignee: Jean-Baptiste Onofré >Priority: Major > > This warning occurred when we try to connect to ActiveMQ using SSL in a > springboot application: > > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by > org.apache.activemq.util.IntrospectionSupport > (file:/C:/Users/user/.m2/repository/org/apache/activemq/activemq-client/5.15.13/activemq-client-5.15.13.jar) > to method sun.security.ssl.SSLSocketImpl.setHost(java.lang.String) > WARNING: Please consider reporting this to the maintainers of > org.apache.activemq.util.IntrospectionSupport > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > > > > WARNING: Illegal reflective access by > org.apache.activemq.util.IntrospectionSupport > (file:/C:/Users/user/.m2/repository/org/apache/activemq/activemq-client/5.15.13/activemq-client-5.15.13.jar) > to method sun.security.ssl.SSLSocketImpl.setHost(java.lang.String) at > org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:181) > at > org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155) > at > org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:140) > at > org.apache.activemq.transport.tcp.SslTransport.(SslTransport.java:81) > at > org.apache.activemq.transport.tcp.SslTransportFactory.createTransport(SslTransportFactory.java:122) > at > org.apache.activemq.transport.TransportFactory.doConnect(TransportFactory.java:120) > at > org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:65) > at > org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:331) -- This message was sent by Atlassian Jira (v8.20.1#820001)
