Azure / Azure/azure-functions-java-worker

Unexpected JDK warning message: OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.

Open
#782 0 comments 0 reactions 1 assignee View on GitHub

@YunchuWang is already working on this.

Since Oct 8, 2024.

area:java-functions Enhancement pending release
Dominant language
Java
Stars
103
Forks
74
Avg merge
4d 8h
Merged PRs (30d)
2

Description

worker.config.json specify -noverify parameter as JVM arguments.
https://github.com/Azure/azure-functions-java-worker/blob/687d37389b8c2fc82259a39cecf94a2bfae23ed8/worker.config.json
image

This option make noisy records on traces table with warning level.
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.

https://bugs.openjdk.org/browse/JDK-8230630?page=com.atlassian.jira.plugin.system.issuetabpanels%3Achangehistory-tabpanel

Investigative information
  • Timestamp: N/A
  • Function App name: N/A
  • Function name(s) (as appropriate): N/A
  • Invocation ID: N/A
  • Region: N/A
Repro steps

Check traces log on startup

image

Expected behavior

Disable JDK warning message(s)

Actual behavior

There are 2 JDK warnings on start up

  • OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.

  • OpenJDK 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended

I think first message can be disabled by removing -noverify JVM arguments. But there is no configurable way for Azure Functions Java Worker.

Known workarounds

I think we can ignore this message by configuring logLevel of Host.Function.Console category.

https://learn.microsoft.com/en-us/azure/azure-functions/configure-monitoring?tabs=v2#configure-categories

Related information

Provide any related information

  • Programming language used Java|17
  • Links to source
  • Bindings used

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.