Requests take too long due to reverse DNS #234
Closed
Comments
I see you point but this is currently not possible. The reason why a reverse DNS lookup happens is that the hostname can be configured in a policy file to restrict the access only from certain hosts. In the policy file you can set either the IP or the hostname. In order to keep backwards compatibility the check against the hostname can not be removed by default but I could imagine to introduce a property |
I agree with your proposal, thanks |
rhuss
added a commit
that referenced
this issue
Jan 23, 2016
During a restrictor check by default the hostname is determined which might cause a reverse DNS lookup. In order to avoid this (e.g. because there is nor restriction on the hostname), this configuration property can be set to `false`. For backwards compatibility it is set to `true` but will change to `false` in Jolokia 2.0
Fixed in 1.3.3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi. I am using jolokia 1.1.2 but I think this applies to latest HEAD as well:
When I issue curl requests from localhost, everything works fine.
When I connect from remote machine, each response has a noticable delay of ~5 seconds. I made a thread dump and it looks like address.getHostName() in JolokiaHttpHandler is taking most of that time - seems like a request for reverse DNS is made there. Is there a way to avoid this?
The text was updated successfully, but these errors were encountered: