Error when trying to edit thread?

NESMASTER14NESMASTER14
in Site Suggestions & Feedback


I've tried waiting/refreshing/closing/ the page but I keep on getting this:

 


Server Error

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


JRun closed connection.



 

Comments

  • NewUser123456789NewUser123456789
    What thread/



    and try again
  • NESMASTER14NESMASTER14

    Originally posted by: Paul



    What thread/



    and try again



    My Color Dreams thread:



    http://nintendoage.com/forum/messageview.cfm?catid=31&threadid=89537



    still isn't working
  • NewUser123456789NewUser123456789
    works for me... Odd.



    Have you tried from another computer or another browser?
  • B.A.B.A.
    I have been getting that error a lot lately, especially from my phone. Try getting into the thread from another method, like clicking on the sub-forum first or finding it through the threads you have posted in.
  • NintendoAge ModeratorNintendoAge Moderator
    I've been seeing that error more and more just by clicking the "latest posts" button at the top. Happens when things appear under heavy load. Dain replied about that specific problem a while back and instantly fixed it. Still crops up once and a while.



    Latest posts link:

    http://www.nintendoage.com/forum/index.cfm?FuseAction=latestposts.cfm



    My bookmark:

    http://www.nintendoage.com/forum/latestposts.cfm?
  • sully_51sully_51
    I get it all the time if I use the back button on my browser. At least a few times every time I'm on the site.
  • MogMog
    I get that JRun closed connection error all the time, seems to happen when the page is taking a long time to load. Not sure if its because of the long load time, or that error is what is causing what seems to be a long load time.



    When that happens I just click back and/or refresh and it normally works right after that.
  • DainDain
    This error message happens for a few reasons:



    1. The site is under heavier than normal load and the request has timed out. We time-out requests pretty quickly to keep the site from bogging down too much.



    2. There aren't enough open request threads to handle the request. I've been trying to balance open request threads numbers and request queue times to find a balance (until we have to cluster servers, which is probably the next step).



    Things we can do to help reduce these:



    1. Stop uploading massive image files that are 3-4 MB each. Just use a photo service if you don't know how to resize images. Granted, next update we do this automatically so it may not be such an issue.



    2. Offloading all files to a CDN, which may happen soon as well. We offloaded core web files like JS and CSS files, but the next step is to completely offload all binaries to Amazon S3 or similar.
Sign In or Register to comment.