Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

[via GitHub]

GitHub user ratoaq2 edited a discussion: java.lang.IllegalArgumentException: 
The `GraalVmProcessor` annotation processor is missing the required 
`log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options

Hi all,

I have a java 21 maven project which uses eclipse compiler 
org.codehaus.plexus:plexus-compiler-eclipse:2.15.0 and  has a log4j plugin 
using a Log4j2Plugins.dat file and configured the compiler with:
```

org.apache.maven.plugins
maven-compiler-plugin


generate-log4j-plugin-descriptor

compile

process-classes

only



org.apache.logging.log4j

log4j-core




org.apache.logging.log4j.core.config.plugins.processor.PluginProcessor





```

After upgrading from 2.24.3 to 2.25.0 now my compilation is failing with:

```
19:43:54  [INFO] --- compiler:3.14.0:compile (default-compile) @ common ---
19:43:55  [INFO] Recompiling the module because of changed source code.
19:43:55  [INFO] Compiling with eclipse [debug deprecation parameters target 
21] to target/classes
19:43:55  [INFO] -
19:43:55  [ERROR] COMPILATION ERROR : 
19:43:55  [INFO] -
19:43:55  [ERROR] /redacted//redacted/src/main/redacted/Redacted.java: 
Internal compiler error: java.lang.Exception: 
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor 
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` 
options.
19:43:55  The generation of GraalVM reflection metadata for your Log4j Plugins 
will be disabled. The generation of GraalVM reflection metadata for your Log4j 
Plugins will be disabled.
19:43:55  [ERROR] Unknown source: The `GraalVmProcessor` annotation processor 
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` 
options.
19:43:55  The generation of GraalVM reflection metadata for your Log4j Plugins 
will be disabled.
19:43:55  [INFO] 2 errors 
```

Is anyone facing similar issue? I tried to specify the graal processor with its 
arguments, but that doesn't work either.


GitHub link: https://github.com/apache/logging-log4j2/discussions/3755


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: [D] Log4net stopped sending logs to datadog agentless logging [logging-log4net]

[via GitHub]

GitHub user francolawpaybyphone added a comment to the discussion: Log4net 
stopped sending logs to datadog agentless logging

Yes we can consider updating to log4net 3.1.0
I could not reproduce the issue
I have also created a support ticket to Datadog

GitHub link: 
https://github.com/apache/logging-log4net/discussions/254#discussioncomment-13498714


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: [D] Log4net stopped sending logs to datadog agentless logging [logging-log4net]

[via GitHub]

GitHub user francolawpaybyphone added a comment to the discussion: Log4net 
stopped sending logs to datadog agentless logging

The problem was resolved by redeploying the application. APM metrics and the 
application were working fine at the time. Only logs were not sent.

GitHub link: 
https://github.com/apache/logging-log4net/discussions/254#discussioncomment-13498819


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: [D] Log4net stopped sending logs to datadog agentless logging [logging-log4net]

[via GitHub]

GitHub user francolawpaybyphone added a comment to the discussion: Log4net 
stopped sending logs to datadog agentless logging

Does log4net fail silently?

GitHub link: 
https://github.com/apache/logging-log4net/discussions/254#discussioncomment-13498828


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: Archiving Chainsaw and Flume GitHub repositories

[Ralph Goers]

I am actively working on Log4j-Audit at the moment. I am currently upgrading it 
to all the latest dependencies.  Once I commit that I will be adding in 
ElectronJS to solve the UI problem I have had with that. The upgrade only has 
one challenging aspect - The upgrade of JGit necessitates that I replace JSch 
with Apache Mina for SSH access to the Git repo. I have a need to use this to 
add audit logging to some services at work so I need to get this done asap.  I 
will probably have issues here doing a release as I have no idea if I can still 
publish the web site or perform a release given how the build process has 
changed for the other log4j projects.

I do have a task to upgrade Flume as well as add a fix for a problem that was 
reported. As you know we use Flume at my work and it needs to be upgraded. So I 
will be jumping back on this in the next couple of months.

I don’t work on Chainsaw and never have. I don’t know of anyone who plans to do 
any work on it so I do not object to archiving chainsaw.

I do have to apologize. While I try to follow the dev l& pmc lists I have had a 
terrible time following the email generated by GitHub. I currently have almost 
10,000 unread messages from GitHub for the logging project. My mailboxes for 
Maven are worse. I have 30,000 unread messages from Jira and 11,000 from 
GitHub. I’ve given up trying to keep up to date with Maven’s email.

Ralph

> On Jun 16, 2025, at 1:23 AM, Volkan Yazıcı  wrote:
> 
> Hey Ralph! In the last 6 months, I haven't noticed any progress regarding
> these projects. Though you might have changes ready locally, or I might
> have missed your activity. Would you mind updating us on your progress and
> plans, please?
> 
> On Wed, Jan 15, 2025 at 2:21 PM Ralph Goers 
> wrote:
> 
>> -1 on Flume
>> 
>> Despite you not seeing visible evidence I am still working on these. I am
>> actually fairly confident I will need to create releases of Flume in the
>> next 6 months.
>> 
>> Ralph
>> 
>>> On Jan 15, 2025, at 2:05 AM, Volkan Yazıcı  wrote:
>>> 
>>> Chainsaw and Flume projects have been moved to dormant state with PMC
>>> consensus. Yet their GitHub repositories (i.e., `logging-chainsaw` and
>>> `logging-flume*`) don't reflect this and they  weekly get flagged by
>> GitHub
>>> due to vulnerable dependencies. This is also confusing for users, since
>> the
>>> list of Logging Services dormant projects
>>>  and the GitHub repository
>>> statuses don't match.
>>> 
>>> *I suggest archiving¹ `logging-chainsaw` and `logging-flume*` GitHub
>>> repositories. Objections?*
>>> 
>>> ¹ When a GitHub project gets archived, it becomes read-only. This is a
>>> reversible operation; we can anytime unarchive these projects if PMC
>>> decides to start maintaining them again.
>> 
>> 

Re: [D] Log4net stopped sending logs to datadog agentless logging [logging-log4net]

[via GitHub]

GitHub user FreeAndNil added a comment to the discussion: Log4net stopped 
sending logs to datadog agentless logging

It depends how you define silently.
The app won't crash on logging errors.
See https://logging.apache.org/log4net/manual/faq.html#internal-debugging

GitHub link: 
https://github.com/apache/logging-log4net/discussions/254#discussioncomment-13499184


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: Archiving Chainsaw and Flume GitHub repositories

[Ralph Goers]

I just looked at my Maven emails. It looks like they migrated all their Jira 
issues into GitHub issues or something which is why I had so many emails.

Ralph

> On Jun 17, 2025, at 9:01 AM, Ralph Goers  wrote:
> 
> I am actively working on Log4j-Audit at the moment. I am currently upgrading 
> it to all the latest dependencies.  Once I commit that I will be adding in 
> ElectronJS to solve the UI problem I have had with that. The upgrade only has 
> one challenging aspect - The upgrade of JGit necessitates that I replace JSch 
> with Apache Mina for SSH access to the Git repo. I have a need to use this to 
> add audit logging to some services at work so I need to get this done asap.  
> I will probably have issues here doing a release as I have no idea if I can 
> still publish the web site or perform a release given how the build process 
> has changed for the other log4j projects.
> 
> I do have a task to upgrade Flume as well as add a fix for a problem that was 
> reported. As you know we use Flume at my work and it needs to be upgraded. So 
> I will be jumping back on this in the next couple of months.
> 
> I don’t work on Chainsaw and never have. I don’t know of anyone who plans to 
> do any work on it so I do not object to archiving chainsaw.
> 
> I do have to apologize. While I try to follow the dev l& pmc lists I have had 
> a terrible time following the email generated by GitHub. I currently have 
> almost 10,000 unread messages from GitHub for the logging project. My 
> mailboxes for Maven are worse. I have 30,000 unread messages from Jira and 
> 11,000 from GitHub. I’ve given up trying to keep up to date with Maven’s 
> email.
> 
> Ralph
> 
>> On Jun 16, 2025, at 1:23 AM, Volkan Yazıcı  wrote:
>> 
>> Hey Ralph! In the last 6 months, I haven't noticed any progress regarding
>> these projects. Though you might have changes ready locally, or I might
>> have missed your activity. Would you mind updating us on your progress and
>> plans, please?
>> 
>> On Wed, Jan 15, 2025 at 2:21 PM Ralph Goers 
>> wrote:
>> 
>>> -1 on Flume
>>> 
>>> Despite you not seeing visible evidence I am still working on these. I am
>>> actually fairly confident I will need to create releases of Flume in the
>>> next 6 months.
>>> 
>>> Ralph
>>> 
 On Jan 15, 2025, at 2:05 AM, Volkan Yazıcı  wrote:
 
 Chainsaw and Flume projects have been moved to dormant state with PMC
 consensus. Yet their GitHub repositories (i.e., `logging-chainsaw` and
 `logging-flume*`) don't reflect this and they  weekly get flagged by
>>> GitHub
 due to vulnerable dependencies. This is also confusing for users, since
>>> the
 list of Logging Services dormant projects
  and the GitHub repository
 statuses don't match.
 
 *I suggest archiving¹ `logging-chainsaw` and `logging-flume*` GitHub
 repositories. Objections?*
 
 ¹ When a GitHub project gets archived, it becomes read-only. This is a
 reversible operation; we can anytime unarchive these projects if PMC
 decides to start maintaining them again.
>>> 
>>> 
>