Integrated: 8305763 : Parsing a URI with an underscore goes through a silent exception, negatively impacting performance
Dhamoder Nalla
duke at openjdk.org
Wed Jun 7 09:53:08 UTC 2023
On Tue, 11 Apr 2023 18:00:05 GMT, Dhamoder Nalla <duke at openjdk.org> wrote:
> Issue 8305763 : Using underscores in the name for a URI triggers a silent exception in the java standard library, which consumes 5% of the CPU.
>
> Exception:
> java.net.URISyntaxException: Illegal character in hostname at index N: xyz1_abcd.com
> at java.base/java.net.URI$Parser.fail(URI.java:2943)
> at java.base/java.net.URI$Parser.parseHostname(URI.java:3487)
> at java.base/java.net.URI$Parser.parseServer(URI.java:3329)
>
> This exception is silent and does not produce any messages, except for ODP profiler, there is no other evidence that it’s happening (the stack trace above was printed after changes to Java library). The reason for this is because of how the URI creation is implemented in the java.net.URI class. There are two paths for creating a valid URI, and one of them goes through an exception.
>
> We can see that if parseServer fails, there is still a way the authority gets assigned and we don’t throw an exception from the method. This means, not being able to parse the server is ok and the exception is silenced. In our case, the server parsing fails because we find an illegal character, as only alphanumeric and dash characters are allowed.
This pull request has now been integrated.
Changeset: 749d4801
Author: Dhamoder Nalla <dhanalla at microsoft.com>
Committer: Daniel Fuchs <dfuchs at openjdk.org>
URL: https://git.openjdk.org/jdk/commit/749d4801937ac145f945765f0ba0980bbccf384f
Stats: 29 lines in 1 file changed: 20 ins; 0 del; 9 mod
8305763: Parsing a URI with an underscore goes through a silent exception, negatively impacting performance
Reviewed-by: dfuchs
-------------
PR: https://git.openjdk.org/jdk/pull/13430
More information about the net-dev
mailing list