Before submitting a bug report, consider the following recommendations:
Collect as much relevant data as possible. For example, generate a thread
dump in the case of a deadlock, or locate the core file (where applicable) and
hs_err file in the case of a crash. In every case, it is important
to document the environment and the actions performed just before the problem
happened. See Collect Data for a Bug Report.
Where applicable, try to restore the original state and reproduce the problem using the documented steps. This helps to determine if the problem is reproducible or an intermittent issue.
If the issue is reproducible, try to narrow down the problem. In some cases, a bug can be demonstrated with a small standalone test case. Bugs that are demonstrated by small test cases will typically be easy to diagnose as compared to test cases that consist of a large complex application.
Search the Java Bug Database to see if this issue or a similar issue was reported. If the issue has already been reported, then the bug report might have further information, such as the following:
If the issue was already fixed, then the release in which it was fixed is given.
A workaround for the issue.
Comments in the evaluation that explain, in further detail, the circumstances that cause the issue to happen.
If you conclude that the issue was not already reported, then report it at Report a Bug or Request a Feature.
Before reporting an issue, verify that the environment where the problem happens is a supported configuration. See Oracle JDK 8 and JRE 8 Certified System Configurations.
In addition to the system configurations, check the list of supported locales. See JDK 8 and JRE 8 Supported Locales.
In the case of Oracle Solaris, check the recommended patch cluster for the operating system release to ensure that the recommended patches are installed.
