Details
-
Bug
-
Resolution: Fixed
-
Low
-
6.7.0
-
None
-
Severity 3 - Minor
-
Description
Issue Summary
The Bitbucket application logs (atlassian-bitbucket.log) contain a significant amount of lines like the following:
ERROR [https-jsse-nio-8201-exec-133] o.a.coyote.http11.Http11NioProtocol Error reading request, ignored java.lang.NullPointerException: null at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.getSslSupport(NioEndpoint.java:1392)
While this does not represent any particular issue with Bitbucket, it causes the log size to be significantly higher than usual and makes the logs harder to process for any potential issue investigation.
This problem is cause
Steps to Reproduce
No particular steps are needed, having Bitbucket running will cause this.
Expected Results
No errors are logged unless an actual problem is occurring.
Actual Results
The below exception is thrown in the atlassian-bitbucket.log file:
ERROR [https-jsse-nio-8201-exec-133] o.a.coyote.http11.Http11NioProtocol Error reading request, ignored java.lang.NullPointerException: null at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.getSslSupport(NioEndpoint.java:1392)
Workaround
If an upgrade is not possible, an option is to change the log level by setting the following in the bitbucket.properties and restart each node:
logging.logger.org.apache.coyote.http11.Http11NioProtocol=FATAL
However, this may hide other important errors.