I have installed the latest version of Lucee on a production server (Win 2019) and all my applications are working fine.
Now I have made a copy of the production server as a development environment.
Lucee runs as well as most of the applications. One application is getting the following error:
Generic Connector Communication Error:
Please check and adjust your setup:
Ensure that Tomcat is running on given host and port.
If this is a timeout error consider adjusting IIS timeout by changing executionTimeout attribute in web.config (see manual).
I was able to find the location of the error. Namely, at that point a large struct (more than 4000 elements) is assigned to another struct. Like this:
If I comment out the line, then everything runs fine except that all the texts are missing in the application.
Does anyone have an idea why this works in Prod and not in the “identical” Dev environment?
I would be very grateful for a helpful tip. I have already spent far too much time trying to find the error without a result so far.
As @andreas suggests, unless its a literally spliced virtual machine on identical resources, its not identical.
I would set the execution time way higher, by a factor of 10 and see what happens. If you have everything defaulted, at the top of the page(s) that are calling the code, put cfrequesttimeout=9000 or some non production value and see if it works.
Usually older processors with all the Intel mitigations tend to run a bit sluggish on any OS that has implemented them.
If that isnt it look at FWDN / NETBIOS / HOSTNAMES in your code and patch your host file accordingly.
Look at the firewall, if its not production, and its in a Dev sandbox, DROP the firewall.
disable IPv6
Check DNS revolvers and hostname.
Update when needed. Even dev boxes need code updates.
The cfrequesttimeout is set to 3600. But the error occurs after 3 seconds. The log from the BonCode Connector says nothing about an error.
According to the debugging timers, the dev environment is many times faster than the prod environment. So I don’t think it has anything to do with the performance of the hardware. But who knows…
I found a solution in the meantime. The session memory was set to cookie in the admin. I set it back to Memory and suddenly the error is gone. What remains strange is that this setting works on Live and not on Dev. But there is enough memory, the setting is default, so I leave it like that now.
I sporadically have the same error. The only way to dismiss the error is clearing the site cookies from the browser. Still cannot understand why happens.