Skip to main content
Inspiring
March 4, 2011
Question

Application server is busy error

  • March 4, 2011
  • 1 reply
  • 1175 views

We're intermittently getting the following error (CF9 9,0,0,251028 standalone, Linux SUSE):

Server Error

The server encountered an internal error and was unable to complete your request.

Application server is busy. Either there are too many concurrent requests or the server still is starting up.

The error occurs in all of our applications running on the server, including the CF admin interface. A page refresh resolves it temporarily.

We had this issue on another server and found that disabling J2EE session variables did the trick. That's not an option on this server as we have external authentication services that use the J2EE session token format.

We can create it pretty consistently with requests that include StructDelete and StructClear on the session object. Wondering if the combination of those functions and J2EE session variables is a cause?

    This topic has been closed for replies.

    1 reply

    Participating Frequently
    May 14, 2011

    We just had a similar issue on linux, CF9.0.1 64 bit.   I was porting a CF8 app to CF9 and suddenly all of those "Application server is busy" errors started popping up.

    What was weird was that requests would alternate with that message and then working fine.

    After a ton of detective work, I narrowed our problem down to CFCACHE.

    Under CF9 Linux, the use of the old deprecated "timeout" param in CFCACHE completely screws up the server (at least ours...).   It gets in a funny state where it times out half the requests.  This was officially deprecated in CF7, but it did work fine in CF8, so we had a few of them survive in my code.

    Removed them all, and so far not a single message.

    Do you have any <cfcache timeout = "#DateAdd("h", "-3", Now() )#"> in your code by any chance?

    rhaddanAuthor
    Inspiring
    May 18, 2011

    It turned out that it was caused by clearing the client struct in our session end/logout process. Removing that functionality resolved the problem.