Developers can file a bug report at bugreport.java.com. When submitting a bug report choose a relevant Product, Category, Subcategory, Java Version and Operating System. Provide a clear description of the bug. Providing a test case could help us to find a solution more quickly.
Before submitting a new bug, please search in bugs.java.com to make sure that the same bug has not been reported already.
You can search for existing reports in bugs.java.com, either by keyword or bug id.
If you believe you have found a security vulnerability in Java please report the issue through Oracle's Security Vulnerability reporting process.
Java SE Subscribers, those using Oracle Cloud Infrastructure, those using Java to run supported Oracle products and customers using legacy Oracle Java SE products e.g Java SE Advanced, should file a Service Request which will connect you directly with Java SE Support specialists.
Bug submitted through bugreport.java.com will not be prioritized even if the issue is submitted by Oracle Customers
More information you provide help us to emulate the issue which could help us to find a solution quickly
When an issue has been submitted successfully, a record gets created in the Java Incidents Database. After an initial triage process, it may be transferred to be an issue in the JDK project. When such a transfer occurs, an issue gets created in the Java Bug System (JBS) and a bug id, JDK-#######, will be emailed to you.
Any bug report which is abusive will be deleted. Bug reports that are unclear or incomplete should not be submitted and may be deleted.
An Oracle engineer will contact you if additional information is required to proceed with the analysis of the bug report/enhancement.
Once the submitted report is reviewed and moved across to the JDK Project in the Java Bug System (JBS), you will receive a bug reference number which resembles JDK-#######. You can search for the bug using either JDK ID or Keywords through either https://bugs.java.com/ or https://bugs.openjdk.org.
File a new incident with the subject line "Additional information to JDK-#######'. Replace JDK-####### with the reference number received when the report is filed.
You cannot submit an attachment along with the bug - however consider using an image hosting service for screenshots(png, jpeg).
Oracle provides support for Oracle JDK releases. Oracle will evaluate all issues against the corresponding Oracle JDK release. Oracle will not attempt to replicate issues against other vendors' OpenJDK binaries but we will submit a copy of your report to the OpenJDK bug tracking system.
Issues against OpenJDK source code can be reported to the OpenJDK mailing lists.
The bugs are marked Resolved/Incomplete means the bug requires additional information from the submitter in order to pursue with the investigation. After 14 days, the bug will be marked as Closed/Incomplete.
Closed/Incomplete bugs can be reopened by anyone if additional information is provided.
Issues that require a new build will be resolved in newer versions of the JDK first and backported to earlier releases when appropriate. In some cases, you may be able to validate the fix in newer JDK releases. Backporting to older releases is only done for critical or customer reported issues.
Refer to 'How to contribute' page at http://openjdk.java.net/contribute/.
Submitting a test case is not required but doing so can greatly improve our chances of understanding and addressing the issue.
It depends - while we'd like to help you start on the path towards the resolution of an issue that might affect you, please keep in mind that no one is obliged to fix an issue that you report. If instead you'd like to explore commercial support options, please see the Oracle Java SE Advanced & Suite Products site.
Please see the answer to "How do I provide additional information to a bug?".
Not all bugs submitted do end up in the database. In some cases, bugs are not included in the Bug Database for security reasons.