NAML error on finished app but not testing app

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

NAML error on finished app but not testing app

DavidJCobb

I am currently unable to access the forums on Reaching Perfection due to a 500 Server Error. Here's the first part of the stack trace(?) on the error page; I didn't include the later portions because they seemed to show the same information, but were a lot longer.

Error 500

NAML exception in customized site: org.postgresql.util.PSQLException: FATAL: sorry, too many clients already
	in has_property(nabble:topic.naml:168) - <n.if.has_property name="page_title"> - public void nabble.view.web.template.NodeNamespace.has_property(nabble.naml.compiler.IPrintWriter,nabble.naml.compiler.Interpreter)
	in if(nabble:app.naml:207) - <n.if.has_property name="page_title"> - public static void nabble.naml.namespaces.BasicNamespace._if(nabble.naml.compiler.IPrintWriter,nabble.naml.compiler.Interpreter)
	in app_title_contents(nabble:app.naml:201) - <n.page_node.app_title_contents/>
	in page_node(nabble:app.naml:201) - <n.page_node.app_title_contents/> - public void nabble.view.web.template.NodePageNamespace.page_node(nabble.naml.compiler.IPrintWriter,nabble.naml.compiler.ScopedInterpreter)
	in trim(nabble:utilities.naml:1042) - <n.trim.text/> - public static void nabble.naml.namespaces.BasicNamespace.trim(nabble.naml.compiler.IPrintWriter,nabble.naml.compiler.Interpreter)
	in regex_replace_all(nabble:utilities.naml:1041) - <n.regex_replace_all. pattern="\s+" replacement=" "> - public static void nabble.naml.namespaces.BasicNamespace.regex_replace_all(nabble.naml.compiler.IPrintWriter,nabble.naml.compiler.Interpreter)
	in compress(nabble:app.naml:200) - <n.compress.>
	in app_title(nabble:view_topics.naml:13) - <n.app_title/>
	in topics_table_stylesheet(nabble:view_topics.naml:14) - <n.topics_table_stylesheet/>
	in head(nabble:app.naml:69) - <n.head/>
	in put_in_head(nabble:utilities.naml:21) - <n.put_in_head.head/> - public void nabble.view.web.template.HtmlNamespace.put_in_head(nabble.naml.compiler.IPrintWriter,nabble.naml.compiler.Interpreter)
	in comment(custom_tweak:tweaks:151) - <n.comment.>
	in nabble_html(nabble:utilities.naml:18) - <n.nabble_html> - public void nabble.view.web.template.ServletNamespace.nabble_html(nabble.naml.compiler.IPrintWriter,nabble.naml.compiler.ScopedInterpreter)
	in html_impl(nabble:utilities.naml:4) - <n.html_impl>
	in html(nabble:app.naml:88) - <n.html>
	in do(nabble:utilities.naml:977) - <n.as_node_page.do/>
	in as_node_page(nabble:utilities.naml:977) - <n.as_node_page.do/> - public void nabble.view.web.template.NodeNamespace.as_node_page(nabble.naml.compiler.IPrintWriter,nabble.naml.compiler.ScopedInterpreter)
	in do(nabble:utilities.naml:982) - <n.get_node_from_request_parameter.do/>
	in get_node_from_request_parameter(nabble:utilities.naml:982) - <n.get_node_from_request_parameter.do/> - public void nabble.view.web.template.ServletNamespace.get_node_from_request_parameter(nabble.naml.compiler.IPrintWriter,nabble.naml.compiler.ScopedInterpreter) throws java.io.IOException,javax.servlet.ServletException,nabble.naml.namespaces.TemplateException
	in catch_exception(nabble:utilities.naml:981) - <n.catch_exception. id="get-node-block"> - public void nabble.naml.namespaces.BasicNamespace.catch_exception(nabble.naml.compiler.IPrintWriter,nabble.naml.compiler.Interpreter)
	in ads(ad:ad.naml:569) - <n.ads.overridden /> - public void nabble.modules.ad.ServletNamespaceExt.ads(nabble.naml.compiler.IPrintWriter,nabble.naml.compiler.ScopedInterpreter)
	in (ad:ad.naml:568) - <override_subroutine name="view_board" requires="basic,nabble,servlet">
	in view_board(nabble:app.naml:13) - <n.view_board/>
	in case(nabble:app.naml:12) - <n.case. value="board"> - public void nabble.naml.namespaces.BasicNamespace$SwitchNamespace._case(nabble.naml.compiler.IPrintWriter,nabble.naml.compiler.Interpreter)
	in switch(nabble:app.naml:2) - <n.switch. value="[n.get_node_from_parameter.type/]"> - public void nabble.naml.namespaces.BasicNamespace._switch(nabble.naml.compiler.IPrintWriter,nabble.naml.compiler.ScopedInterpreter)
	in (nabble:app.naml:1) - <macro name="view_app" requires="servlet,nabble,basic">

Our testing mirror, which should be running the exact same NAML, is still accessible without errors. That fact, along with the text of the error message, leads me to believe that the problem has to do with too many users attempting to access RP recently. However, I don't know of any way to check this. So...

  • Is there a way to check how many users have attempted to access the site?
  • Is there a way to fix and prevent this error in the future?
  • Is there anything in my NAML code that might be increasing the burden on your servers, and triggering this error?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: NAML error on finished app but not testing app

DavidJCobb
Ah, the error seems to have fixed itself. I am a bit worried, though, since I don't know how much traffic triggered this.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: NAML error on finished app but not testing app

Hugo <Nabble>
Administrator
It might have been a glitch. We will investigate what happened.
Is there a way to check how many users have attempted to access the site?
We don't have that feature, but you may use google analytics for that.
 Is there a way to fix and prevent this error in the future?
We will take a look -- we take bugs seriously.
 Is there anything in my NAML code that might be increasing the burden on your servers, and triggering this error?
I am not sure, but it is unlikely. NAML is meant to be efficient and one forum alone shouldn't put the whole server down.  We will take a closer look.
Official Nabble Administrator - we never ask for passwords.
Loading...