Thanks for the response Stig!!
Right - I had some conflicting entries in my maven pom.xml file due to
which it was picking up kafka 3.8.1 instead of 4.0.0. Resolved it now.
On Thu, Aug 21, 2025 at 2:23 PM Stig Rohde Døssing
wrote:
> You can also see this from these lines of the stack trace
>
You can also see this from these lines of the stack trace
java.base/javax.security.auth.Subject.getSubject(Subject.java:277)
org.apache.kafka.common.security.authenticator.SaslClientCallbackHandler.handle(SaslClientCallbackHandler.java:58)
In Kafka 4.0.0, that line in the callback handler isn't c
Your stack trace suggests that you aren't actually using Kafka 4.0.0.
The relevant code in 4.0.0 is here
https://github.com/apache/kafka/blob/4.0.0/clients/src/main/java/org/apache/kafka/common/security/authenticator/SaslClientAuthenticator.java#L221
As you can see, the line number doesn't match
Are there any issues with running the kafka 4.0.0 client on graalVM JDK 24?
My Java codebase uses GraalVM JDK 24 and I continue to get the following
error:
Caused by: org.apache.kafka.common.errors.SaslAuthenticationException:
Failed to configure SaslClientAuthenticator
Caused by: java.lang.Unsupp
Ok. I see issue with kafka client 4.0.0 as well. When I call kafkaconsumer
partitionFor API and also during Producer send.
Will try with kafka client 3.9.1 to see if it helps.
On Thu, 21 Aug, 2025, 00:03 Stig Rohde Døssing,
wrote:
> Subra,
>
> This should be fixed with
> https://issues.apache.o
Subra,
This should be fixed with https://issues.apache.org/jira/browse/KAFKA-17078.
Den ons. 20. aug. 2025 kl. 19.43 skrev Subra I :
> I understand that this was slated to fixed. as per this KIP:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1006%3A+Remove+SecurityManager+Support
>
>
I understand that this was slated to fixed. as per this KIP:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-1006%3A+Remove+SecurityManager+Support
Has this been fixed in kafka 4.0.0 client? Basically, being able to handle
removal of SecurityManager in JDK.
On Wed, Aug 20, 2025 at 7:22 PM S
Hello All,
We have a codebase on Java where we create a kafka producer/consumer to
talk to kafka brokers. We support TCP/SSL/SASL modes of operation for kafka.
We are upgrading our environment to JDK 24. And I see that is causing our
SASL functionalities to break.
I am using kafka client version
Just wanted to provide a short status since it's been a bit:
Luke got the last bits merged, so 3.9 is tested against Java 23.
There's a PR to move trunk to testing against Java 24 at
https://github.com/apache/kafka/pull/19514. It was blocked for a while
waiting for Gradle to release, and now it's
The person doing the PR to update the Jenkinsfile should include these
changes, which were in the PR for trunk that updated Github Actions to run
Java 23
https://github.com/apache/kafka/commit/76a9df47ca6088361fe707a2946827f7558d9f71
Den tors. 3. apr. 2025 kl. 20.17 skrev Stig Rohde Døssing <
sti
Hi Stig,
Thanks for the investigation.
I'll take a look.
Thanks.
Luke
On Fri, Apr 4, 2025 at 2:24 AM Stig Rohde Døssing
wrote:
> The person doing the PR to update the Jenkinsfile should include these
> changes, which were in the PR for trunk that updated Github Actions to run
> Java 23
>
>
> h
Looking in the build log, I see this
Loading trusted files from base branch 3.9 at
90ee2d2b3499b7e1eff99bc63bf66aba9d7ff99c rather than
f4cd8d5d664a62b280c0d2ea1bc731069443ba87
Obtained Jenkinsfile from 90ee2d2b3499b7e1eff99bc63bf66aba9d7ff99c
‘Jenkinsfile’ has been modified in an untrusted revisi
Hi Luke,
I took a look at getting 3.9 to run Java 23 on CI in this PR
https://github.com/apache/kafka/pull/19311 which is just 3.9 plus all the
other backport PRs, plus a few extra backports and changes to get Java 23
to build locally. I was planning to raise PRs for these bits individually
once I
Hi all,
Just keep in mind that *Gradle version 8.14 *(currently under development)
will support *Java 24*:
- https://docs.gradle.org/8.13/userguide/compatibility.html
- https://github.com/gradle/gradle/issues/32290#issuecomment-2741096604
- https://github.com/gradle/gradle/issues/32289#i
Hi Stig and all,
For backporting the change to 3.9, if there's no objections, I think we can
start to merge them tomorrow.
For the Java 24 testing, it's fine we ship 3.9 without Java 24 test if
gradle release is delayed since this is also the state of what Kafka v4.0
is.
So we should firstly test
Hi,
Keeping our fingers crossed for this backport to make it into 3.9.
We are using Kafka client as a 3rd, and 4th party dependency (through
Confluent Parallel Consumer - @astubbs), in a collection of Helidon MP
4.1.6 microservices.
When do you estimate would we know for sure whether it will be
Thanks. I'll wait for that PR then. Since it's blocked by Gradle, and the
plan is for Gradle to release a new version on April 7th (see
https://github.com/gradle/gradle/issues/32289#issuecomment-2741056207),
maybe the way to go is to aim to test with Java 23 on 3.9 for now? Once we
can test with Ja
hi Stig
> Does anyone know where the corresponding CI script
files are located in 3.9?
https://github.com/apache/kafka/blob/3.9/Jenkinsfile#L165
> I noticed that trunk isn't currently testing against Java 24. I'll try to
make a PR to fix that, which will probably require another bump of
Spotbugs
Chia-Ping, I think we should aim for Java 24 support, since 23 reaches end
of life in a month or so.
Here are PRs for 4 of the changes linked at
https://issues.apache.org/jira/browse/KAFKA-17638
Scala upgrade https://github.com/apache/kafka/pull/19307
Compiler warning 1 https://github.com/apache/
hi Stig
We should run CI under Java 23 if we want to make 3.9 support Java 23
officially, so +1 to backport them
Best,
Chia-Ping
> Mickael Maison 於 2025年3月28日 下午6:43 寫道：
>
> Hi,
>
> I'm also supportive of backporting this change to the 3.9 branch.
>
> Thanks,
> Mickael
>
>
>
>> On Fri,
Hi,
I'm also supportive of backporting this change to the 3.9 branch.
Thanks,
Mickael
On Fri, Mar 28, 2025 at 10:16 AM Stig Rohde Døssing
wrote:
>
> Pulling in a discussion from the PR thread:
>
> > There were other PRs that were part of Java 23 support generally, should
> these also be backp
Pulling in a discussion from the PR thread:
> There were other PRs that were part of Java 23 support generally, should
these also be backported? https://issues.apache.org/jira/browse/KAFKA-17638
Greg, thanks for letting me know about these, I was not aware.
I think most likely these changes aren
Hi All,
I am still strongly in support of backporting this patch as I stated in the
earlier discussion thread.
Thank you Stig, Anton, Danish, Mateusz, Manfred, Monica, Istvan, Vincent,
Clement, Anshu, Foivos, Drakgoku, Severin, Ozan, Georgios, and Guillaume,
members of our extended community who
Hi Stig,
Thanks for bringing this to us.
I'm +1 for backporting to 3.9 branch since there's no workaround for Java
24.
Thanks.
Luke
On Tue, Mar 18, 2025 at 1:14 AM Stig Rohde Døssing
wrote:
> Thanks Ismail,
>
> I've opened https://github.com/apache/kafka/pull/19221 just to get any
> test
> f
Thanks Ismail,
I've opened https://github.com/apache/kafka/pull/19221 just to get any test
failures out of the way in case it is decided to do this backport.
I'm hoping people will weigh in with their concerns in this thread if they
don't like the idea of backporting this change.
Den man. 17. ma
Hi Stig,
Kafka 4.0 is likely to be released in a day or two. Even so, I think it
makes sense to revive the backporting thread given the lack of workaround
for Java 24.
Ismael
On Mon, Mar 17, 2025 at 7:44 AM Stig Rohde Døssing
wrote:
> Hi,
>
> Some months ago, a reflective shim was added in
> h
26 matches
Mail list logo
