1. On a command prompt execute set | findstr JAVA_HOME and verify the result;
2. If something was reported maybe the JAVA_HOME environment variable is not set at system level, but at a different level like user level which is not visible from the KNet process that raised the exception;
3. Try to set JAVA_HOME at system level e.g. JAVA_HOME=C:\Program Files\Eclipse Adoptium\jdk-11.0.18.10-hotspot\;
4. Try to set JCOBRIDGE_JVMPath at system level e.g. JCOBRIDGE_JVMPath=C:\Program Files\Eclipse Adoptium\jdk-11.0.18.10-hotspot\.

[!IMPORTANT]

• One of JCOBRIDGE_JVMPath or JAVA_HOME environment variables or Windows registry (on Windows OSes) shall be available
• JCOBRIDGE_JVMPath environment variable takes precedence over JAVA_HOME and Windows registry: you can set JCOBRIDGE_JVMPath to C:\Program Files\Eclipse Adoptium\jdk-11.0.18.10-hotspot\bin\server\jvm.dll and avoid to override JVMPath in your code
• After first initialization steps, JVMPath takes precedence over JCOBRIDGE_JVMPath/JAVA_HOME environment variables or Windows registry

Intel CET and KNet

KNet uses an embedded JVM through JNet/JCOBridge, however JVM initialization is incompatible with CET because the code used to identify CPU try to modify the return address and this is considered from CET a violation: see this comment.

From .NET 9 preview 6, CET is enabled by default on supported hardware when the final stage produce an executable artifact, i.e. the csproj file contains <OutputType>Exe</OutputType>.

If the application, upon startup, fails with the error 0xc0000409 (subcode 0x30) it was compiled with CET enabled and it fails during JVM initialization.

To solve the issue there are four possible solutions:

1. use a .NET version, e.g. 8, that does not enable CET by default
2. Add the following snippet to disable CET on executable (templates available for KNet are ready made and solve this issue):

3. Use the dotnet app host, as reported in https://github.com/masesgroup/JCOBridgePublic/issues/7#issuecomment-2550031946, with a syntax like:

instead of the classic:

4. If you want to run the classic application execute the following command in an elevated shell:

then run:

Use the following to enable again CET:

Producer example

Below the reader can found two different version of producer examples.

Simple producer

A basic producer can be like the following one:

The example above can be found in the templates package. Its behavior is:

• during initialization prepares the properties,
• create a producer using the properties
• create ProducerRecord and send it
• print out the produced data and the resulting RecordMetadata

Producer with Callback

A producer with Callback can be like the following one. In this example the reader can highlight a slightly difference from the corresponding Java code. Surf JVM callbacks to go into detail in the callback management from JVM.

The example above can be found in the templates package. Its behavior is:

• during initialization prepares the properties
• create a producer using the properties
• create ProducerRecord and send it using the API Send with the attached Callback
• when the operation completed the Callback is called:
  • if an Exception was raised it will be printed out
  • otherwise the RecordMetadata is printed out
• print out the produced data and the resulting RecordMetadata

Consumer example

A basic consumer can be like the following one:

The example above can be found in the templates package. Its behavior is:

• during initialization prepares the properties,
• create a consumer using the properties
• subscribe and starts consume
• when data are received it logs to the console the information.