Developers can file a bug report at bugreport.java.com. Click here to go to the bug submission form and start filling the bug report. On the next page choose a relevant Product/Category and then select the appropriate Subcategory, Release, and Operating System. Provide a clear description of the bug and a test case that helps to investigate the issue.
Before submitting a new bug, please search to make sure that the same bug has not been reported already.
You can search for existing reports on bugs.java.com.
A good test case to demonstrate the bug is required. Additionally, provide the platform information of where you have seen the bug (e.g. Operating System, Java Version, etc.), environmental information (e.g. CLASSPATH, PATH, etc.), command line options tried (e.g. -Xint for a compiler bug), and JDK version where the bug exists. More information can be found here.
For regressions, also include the JDK version and build number, where the bug does not exist. Letting us know the version where the bug exists and the version where it does not exist will allow us to narrow down where the bug may have been introduced.
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-8YYYYYY, will be sent 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. A bug's life cycle is explained in this blog.
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-XXXXXXX. You can search for the bug using either JDK ID or Keywords through either https://bugs.java.com/ or https://bugs.openjdk.java.net.
In exceptional circumstances, for example when the bug is made confidential, you will not get an automatic notification. However, an Oracle engineer may get in touch with you.
File a new incident with the subject line "Additional information to JDK-XXXXXXX'. Replace XXXXXXX with the reference number received when the report is filed. We are working on a system where you will be able to provide additional information to the existing bug.
You cannot submit an attachment along with the bug at this time. However, these attachments can be shared when an Oracle engineer is in touch with you.
One can express an interest in an existing bug on the Oracle Community Forum or through one of the relevant OpenJDK mailing lists. We are working on a system where you will be able to provide additional information or express interest on existing bug reports.
OpenJDK is not a product, so it's not listed as such. Depending on the area you'd like to report the issue in, you would typically pick the appropriate Java Platform, Standard Edition release from the bug submission form.
No. Users without an account in JBS can use bugreport.java.com to submit an issue.
Resolved/Incomplete means the bug requires additional information from you in order to pursue with the investigation. Kindly provide the additional information as is requested in the bug. See point 6 for instructions on how to provide additional information.
Closed/Incomplete means the bug required additional information, but as we did not receive the additional information requested, the bug has been closed. The bug can be reopened when you (or someone else) provides additional information.
Oracle does not release debug bundles. However, an enthusiast can build his/her own fast debug bundles using the use OpenJDK source. Refer to README-builds.html included in the source repository for instructions.
Yes, one should be able verify a fix when the fix is available in an Early Access build posted on http://jdk.java.net/.
Refer to 'How to contribute' page at http://openjdk.java.net/contribute/.
The bug that you have found needs to be reproducible so that when the bug is fixed, the test case can be run again to demonstrate that the bug no longer exists. We could write a test case based on your written description. However, we have found that the bug is often not seen, at least right away, and this results in a fair amount of back and forth communication with the submitter in order to get the test case to reproduce the bug.
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 options here.
Please see the answer to "How do I provide additional information to a bug?".
An issue that's in progress of being addressed will have its Status set accordingly.
Many bug requests are received, and each of them has to be screened and reviewed before it can be included in the Bug Database. Not all bugs submitted do end up in the database. Some bugs don't show up in the database for some time because of delays in processing. In some cases, bugs are not included in the Bug Database for security reasons.