Problems with Langstone Cutters Nabble site

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Problems with Langstone Cutters Nabble site

icymacl
Hi Nabble,

We are experiencing frequent time outs and errors on posting to the Langstone Cutters Forum:  

http://langstone-cutters-rc.1095392.n5.nabble.com 

I just had about 5 Error 503 - too many connections:  

HTTP ERROR: 503

Problem accessing /. Reason:

    too many active connections
Powered by Jetty://

and the following Error 500.  I was not trying to do anything fancy, just post a reply as noted below.  

Can you please investigate and resolve?  

Thanks,

Ian Maclennan

Langstone Cutters RC
Oops... An error has occurred

Please contact Nabble Support and explain what you did to cause this error. Your feedback is very important to us.
More Details
Error 500
url=<a href="http://langstone-cutters-rc.1095392.n5.nabble.com/template/NamlServlet.jtp?5k:%M:%S=&item_description_style=text+tn&alert=true&article_num=55&">http://langstone-cutters-rc.1095392.n5.nabble.com/template/NamlServlet.jtp?5k:%M:%S=&item_description_style=text+tn&alert=true&article_num=55&
Accept-Encoding: gzip, deflate, sdch
Accept-Language: fr-CA,fr;q=0.8,en-US;q=0.6,en;q=0.4

tempting bribery to stop,
         but I'd still be willing to steer!

&item_thumbnail_selection=auto&rssmikle_item_podcast=off&reply=&item_thumbnail=crop&message=Hi Nigel,

Thanks for your kind (and poetic!) offer to cox, which we would like to accept.  More than happy to buy you a beer afterwards, although you don't get much these days for 1/-!!  

See you at Millstream Cottage at 1700 hrs. prompt.  

Ian&s2=Post Message  method=POST user-agent=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/601.7.7 (KHTML, like Gecko) Version/9.1.2 Safari/601.7.7 referer=http://langstone-cutters-rc.1095392.n5.nabble.com/template/NamlServlet.jtp?macro=reply&node=8874 remote=86.174.174.79
Message: macroName is null
RequestURI: /template/NamlServlet.jtp
Server: n5.nabble.com
Caused by:
fschmidt.util.servlet.JtpContextServlet$JtpRuntimeException: url=<a href="http://langstone-cutters-rc.1095392.n5.nabble.com/template/NamlServlet.jtp?5k:%M:%S=&item_description_style=text+tn&alert=true&article_num=55&">http://langstone-cutters-rc.1095392.n5.nabble.com/template/NamlServlet.jtp?5k:%M:%S=&item_description_style=text+tn&alert=true&article_num=55&
Accept-Encoding: gzip, deflate, sdch
Accept-Language: fr-CA,fr;q=0.8,en-US;q=0.6,en;q=0.4

tempting bribery to stop,
         but I'd still be willing to steer!

&item_thumbnail_selection=auto&rssmikle_item_podcast=off&reply=&item_thumbnail=crop&message=Hi Nigel,

Thanks for your kind (and poetic!) offer to cox, which we would like to accept.  More than happy to buy you a beer afterwards, although you don't get much these days for 1/-!!  

See you at Millstream Cottage at 1700 hrs. prompt.  

Ian&s2=Post Message  method=POST user-agent=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/601.7.7 (KHTML, like Gecko) Version/9.1.2 Safari/601.7.7 referer=http://langstone-cutters-rc.1095392.n5.nabble.com/template/NamlServlet.jtp?macro=reply&node=8874 remote=86.174.174.79
        at fschmidt.util.servlet.JtpContextServlet.handleException(JtpContextServlet.java:559)
        at fschmidt.util.servlet.JtpContextServlet.service2(JtpContextServlet.java:463)
        at fschmidt.util.servlet.JtpContextServlet.service(JtpContextServlet.java:332)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:565)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1360)
        at org.eclipse.jetty.servlets.UserAgentFilter.doFilter(UserAgentFilter.java:77)
        at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:144)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1331)
        at cachingfilter.CachingFilter.doFilter(CachingFilter.java:126)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1331)
        at fschmidt.util.servlet.BadBotFilter.doFilter(BadBotFilter.java:74)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1331)
        at fschmidt.util.servlet.ConnectionLimitFilter.doFilter(ConnectionLimitFilter.java:94)
        at nabble.view.lib.NabbleConnectionLimitFilter.doFilter(NabbleConnectionLimitFilter.java:26)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1331)
        at nabble.view.lib.NabbleErrorFilter.doFilter(NabbleErrorFilter.java:21)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1331)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:477)
        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:225)
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1031)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:406)
        at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:965)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
        at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:188)
        at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:149)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111)
        at org.eclipse.jetty.server.Server.handleAsync(Server.java:394)
        at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:454)
        at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:73)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:609)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:45)
        at nabble.model.Executors$1$1.run(Executors.java:27)
        at fschmidt.util.executor.ThreadTimer$1.run(ThreadTimer.java:18)
        at fschmidt.util.executor.AbstractThreadPool$1.run(AbstractThreadPool.java:29)
        at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.RuntimeException: macroName is null
        at nabble.view.lib.Jtp.servletException(Jtp.java:585)
        at nabble.view.web.template.NamlServlet.service(NamlServlet.java:154)
        at nabble.view.web.template.NamlServlet.service(NamlServlet.java:134)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at fschmidt.util.servlet.JtpContextServlet.service2(JtpContextServlet.java:461)
        ... 35 more
Powered by Nabble

Note that the Langstone Cutters Gig Club Forum seems to be OK.  
Reply | Threaded
Open this post in threaded view
|

Re: Problems with Langstone Cutters Nabble site

geofredo soleado
You posted about this last week

It is an ongoing problem with the n5 server.

All you will get from Nabble is that it is bring worked on.the only comfort is your forum is not the only one affected.

Can you see the other topics on this?
Reply | Threaded
Open this post in threaded view
|

Re: Problems with Langstone Cutters Nabble site

icymacl
Hi Geofredo,

Wow, seems like it is taking Nabble a long time to fix the N5 server!  Sorry, I did not look back at all the old posts and also I was blissfully unaware that our forum was on the N5 server and that other club members have posted about this.  I guess we need to keep on being patient......  

Thank you.  
Reply | Threaded
Open this post in threaded view
|

Re: Problems with Langstone Cutters Nabble site

Hugo <Nabble>
We have a new server now and the service seems to be stable again. Please let us know if you guys have any issues. We apologize for the issues in the last days.
Reply | Threaded
Open this post in threaded view
|

Re: Problems with Langstone Cutters Nabble site

icymacl
Hi Hugo, just tried to access the site and got two 503 errors and a 500 error.  Sorry, it is still not fixed at our end.  

Thanks,

Ian