Lucee 6 Internal DNS Lookup Issues

dev support
1

I am trying to upgrade our production version of Lucee to 6.0.0.585. When I turn live traffic on for a server with Lucee 6 on it, after about 60 seconds, cfhttp requests to internal DNS names are unable to resolve. I am unable to reproduce this using k6 load testing. The only way I have been able to create the problem is to unleash live traffic on it. If I switch back to Lucee 5, the cfhttp requests resolve fine. The initial requests resolve fine. Trying with four developers, we are unable to reproduce it. (How many developers does it take to test a web app?) Does anybody have any idea what might be going on?

Edit: I have tried two different servers and it’s the same for both servers.
Edit two: Changing the code to use the IP address allows it to resolve.

OS: Windows Server 2016 (10.0) 64bit
Java Version: 1.8.0_181 (Oracle Corporation) 64bit
Tomcat Version: Apache Tomcat/8.5.33
Lucee Version: Lucee 6.0.0.585

1 Like
2

We believe we’ve found the issue. By adding pooling="false" to our cfhttp requests, we can eliminate the issue. Is there any way to globally change the default for pooling to false? Pooling was introduced to cfhttp requests in 6.0.0.96. (<cfhttp> :: Lucee Documentation) Should I add a bug report for this issue?

3

Try this, from docs:

You can also assign default values for any tag’s attributes using this.tag.tagname.attribute in Application.cfc.

this.tag.cfhttp.username = "system";
this.tag.log.file = "my-custom-log.log";
this.tag.cflocation.addtoken = false;
2 Likes
4

Thanks Roberto!!! I’ll give it a try.

2 Likes
5

Adding this to my application.cfc doesn’t have the desired effect. DNS lookups are still getting blocked after about 70 requests: this.tag.cfhttp.pooling = false;