The value in the default log4j2.properties file and which is reflected in the doc, is aimed at the more general/operational 'identified messages with IDs' about the journal. Those do indeed live under org.apache.activemq.artemis.journal, as shown when you linked to them earlier.
The journals implementation classes and related implementation-detail loggers exist separately, and those classes have .core. in their hierarchy (either historic, or more probably just meaning 'core' in the central/main sense rather than anything to do with e.g the CORE protocol...I used AMQP for example when I verified that TRACE for org.apache.activemq.artemis.core.journal.impl resulted in journal logging). On Fri, 19 May 2023 at 15:03, Doug Whitfield <dwhitfi...@perforce.com.invalid> wrote: > > Thanks Robbie! > > I see these now in TRACE: > org.apache.activemq.artemis.core.journal.impl.JournalImpl > > But the documentation says org.apache.activemq.artemis.journal > > Is the documentation wrong or does it just not apply to CORE? It is very > confusing, either way. > > From: Robbie Gemmell <robbie.gemm...@gmail.com> > Date: Friday, 19 May 2023 at 06:15 > To: users@activemq.apache.org <users@activemq.apache.org> > Subject: Re: No Journal logging > I'd guess the perf command sends non-persistent messages by default, > and so you arent really using the journal there and thus wont see > journal logging. > > I see a load of logging if I enable TRACE on e.g > org.apache.activemq.artemis.core.journal.impl and send persistent > messages. > > On Thu, 18 May 2023 at 17:35, Doug Whitfield > <dwhitfi...@perforce.com.invalid> wrote: > > > > Thanks Robbie. > > > > I am still a bit confused. Maybe some background would be helpful. > > Currently, I am using the following command: > > artemis perf client --message-count 100 > > > > I would expect to see something moving to the journal, and I would expect > > to see that logged. Even setting > > org.apache.activemq.artemis.core.journal.impl and > > org.apache.activemq.artemis.core.persistence.impl.journal to TRACE I don’t > > see anything different. > > > > Originally, we were troubleshooting a performance issue, and wanted to see > > NIO vs ASYNCIO. We have gotten to a point though were we do not believe the > > issue is storage and rather it is flowControl. I think we probably have the > > logging we need for that. However, in the future, if we needed to > > troubleshoot the journal, and get higher logging, how would we do that? I > > think you are saying we just aren’t seeing it because we aren’t hitting the > > narrow set of issues that are actually logged, but I want to be sure that > > is the correct interpretation. > > > > > > From: Robbie Gemmell <robbie.gemm...@gmail.com> > > Date: Thursday, 18 May 2023 at 10:13 > > To: users@activemq.apache.org <users@activemq.apache.org> > > Subject: Re: No Journal logging > > Those files are specifically for the 'identified messages' with IDs, > > as contained in them. You will only see anything for them if a > > situation arises to emit such a log message. That logger config is > > there to ensure those remain enabled by default even if adjusting with > > the wider config. > > > > If you are looking for more general implementation-detail style > > logging about the journal, perhaps try hierarchies like > > org.apache.activemq.artemis.core.journal.impl and > > org.apache.activemq.artemis.core.persistence.impl.journal or others > > around there. > > > > On Thu, 18 May 2023 at 15:24, Doug Whitfield > > <dwhitfi...@perforce.com.invalid> wrote: > > > > > > I found the path at > > > https://github.com/apache/activemq-artemis/tree/main/artemis-journal/src/main/java/org/apache/activemq/artemis/journal > > > but question remains, why are we logging nothing? > > > > > > From: Doug Whitfield <dwhitfi...@perforce.com.INVALID> > > > Date: Thursday, 18 May 2023 at 08:57 > > > To: users@activemq.apache.org <users@activemq.apache.org> > > > Subject: No Journal logging > > > We have the below config. I see at > > > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Factivemq.apache.org%2Fcomponents%2Fartemis%2Fdocumentation%2F&data=05%7C01%7Cdwhitfield%40perforce.com%7C562785de2662461985c008db585a4700%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638200917014959800%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=L3vSAuP927e1%2Fk9i6AgjLkM8Krt4iQ4%2Fac%2BaqLqiR8E%3D&reserved=0<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Factivemq.apache.org%2Fcomponents%2Fartemis%2Fdocumentation%2F&data=05%7C01%7Cdwhitfield%40perforce.com%7C562785de2662461985c008db585a4700%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638200917014959800%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=L3vSAuP927e1%2Fk9i6AgjLkM8Krt4iQ4%2Fac%2BaqLqiR8E%3D&reserved=0><https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Factivemq.apache.org%2Fcomponents%2Fartemis%2Fdocumentation%2F&data=05%7C01%7Cdwhitfield%40perforce.com%7C562785de2662461985c008db585a4700%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638200917014959800%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=L3vSAuP927e1%2Fk9i6AgjLkM8Krt4iQ4%2Fac%2BaqLqiR8E%3D&reserved=0><https://activemq.apache.org/components/artemis/documentation/> > > > that this is correct. I can see at > > > https://github.com/apache/activemq-artemis/tree/main/artemis-server/src/main/java/org/apache/activemq/artemis/core > > > that org.apache.activemq.artemis.core.server exists. However, I don’t see > > > see a journal, jms, or utils directory. > > > > > > How do we log the journal? > > > > > > # Log4J 2 configuration > > > > > > > > > # Monitor config file every X seconds for updates > > > > > > monitorInterval = 5 > > > > > > > > > rootLogger = INFO, console, log_file > > > > > > > > > logger.activemq.name=org.apache.activemq > > > > > > logger.activemq.level=INFO > > > > > > > > > logger.artemis_server.name=org.apache.activemq.artemis.core.server > > > > > > logger.artemis_server.level=DEBUG > > > > > > > > > logger.artemis_journal.name=org.apache.activemq.artemis.journal > > > > > > logger.artemis_journal.level=DEBUG > > > > > > > > > logger.artemis_jms.name=org.apache.activemq.artemis.jms > > > > > > logger.artemis_jms.level=DEBUG > > > > > > > > > logger.artemis_utils.name=org.apache.activemq.artemis.utils > > > > > > logger.artemis_utils.level=INFO > > > > > > > > > # CriticalAnalyzer: If you have issues with the CriticalAnalyzer, setting > > > this to TRACE would give > > > > > > # you extra troubleshooting info, but do not use TRACE regularly as it > > > would incur extra CPU usage. > > > > > > logger.critical_analyzer.name=org.apache.activemq.artemis.utils.critical > > > > > > logger.critical_analyzer.level=INFO > > > > > > > > > # Audit loggers: to enable change levels from OFF to INFO > > > > > > logger.audit_base = OFF, audit_log_file > > > > > > logger.audit_base.name = org.apache.activemq.audit.base > > > > > > logger.audit_base.additivity = false > > > > > > > > > logger.audit_resource = OFF, audit_log_file > > > > > > logger.audit_resource.name = org.apache.activemq.audit.resource > > > > > > logger.audit_resource.additivity = false > > > > > > > > > logger.audit_message = INFO, audit_log_file > > > > > > logger.audit_message.name = org.apache.activemq.audit.message > > > > > > logger.audit_message.additivity = false > > > > > > > > > # Jetty logger levels > > > > > > logger.jetty.name=org.eclipse.jetty > > > > > > logger.jetty.level=WARN > > > > > > > > > # Quorum related logger levels > > > > > > logger.curator.name=org.apache.curator > > > > > > logger.curator.level=WARN > > > > > > logger.zookeeper.name=org.apache.zookeeper > > > > > > logger.zookeeper.level=ERROR > > > > > > > > > > > > # Console appender > > > > > > appender.console.type=Console > > > > > > appender.console.name=console > > > > > > appender.console.layout.type=PatternLayout > > > > > > appender.console.layout.pattern=%d %-5level [%logger] %msg%n > > > > > > > > > # 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{yyyy-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{yyyy-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 > > > > > > > > > > > > This e-mail may contain information that is privileged or confidential. > > > If you are not the intended recipient, please delete the e-mail and any > > > attachments and notify us immediately. > > > > > > > > > This e-mail may contain information that is privileged or confidential. > > > If you are not the intended recipient, please delete the e-mail and any > > > attachments and notify us immediately. > > > > > > > > > CAUTION: This email originated from outside of the organization. Do not > > click on links or open attachments unless you recognize the sender and know > > the content is safe. > > > > > > This e-mail may contain information that is privileged or confidential. If > > you are not the intended recipient, please delete the e-mail and any > > attachments and notify us immediately. > > > > > CAUTION: This email originated from outside of the organization. Do not click > on links or open attachments unless you recognize the sender and know the > content is safe. > > > This e-mail may contain information that is privileged or confidential. If > you are not the intended recipient, please delete the e-mail and any > attachments and notify us immediately. >
