After Post, restarting browser = Error 500 macroName is null

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

After Post, restarting browser = Error 500 macroName is null

MichaelAtOz
After clicking the Post Button, the post text is presented, yet due to the changed handling (where it is created AFTER the mailing list accepts it [this change has other UI issues too BTW]), it has yet to be created.
That is fine when you next click the Forum Title (top left) etc, or otherwise move on.
But if you leave that as is, when you restart the browser you get:

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.


Hence, I log this issue.
Detailed error below.

======================================================
Error 500

macroName is null

Message: macroName is null

RequestURI: /template/NamlServlet.jtp

Server: n5.nabble.com
Caused by:

fschmidt.util.servlet.JtpContextServlet$JtpServletException: url=http://forum.openscad.org/template/NamlServlet.jtp?reply  user-agent=Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.9) Gecko/20100101 Goanna/3.4 Firefox/52.9 PaleMoon/27.8.3 method=GET referer=http://forum.openscad.org/template/NamlServlet.jtp?reply
        at fschmidt.util.servlet.JtpContextServlet.handleException(JtpContextServlet.java:571)
        at fschmidt.util.servlet.JtpContextServlet.service2(JtpContextServlet.java:465)
        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:135)
        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 fschmidt.util.servlet.PatternRedirectFilter.doFilter(PatternRedirectFilter.java:60)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1331)
        at fschmidt.util.servlet.PatternRedirectFilter.doFilter(PatternRedirectFilter.java:60)
        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:250)
        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.handle(Server.java:349)
        at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:449)
        at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:910)
        at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:634)
        at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:230)
        at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:76)
        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:748)
Caused by: javax.servlet.ServletException: macroName is null
        at nabble.view.lib.Jtp.servletException(Jtp.java:590)
        at nabble.view.web.template.NamlServlet.service(NamlServlet.java:155)
        at nabble.view.web.template.NamlServlet.service(NamlServlet.java:135)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at fschmidt.util.servlet.JtpContextServlet.service2(JtpContextServlet.java:461)
        ... 42 more

Reply | Threaded
Open this post in threaded view
|

Re: After Post, restarting browser = Error 500 macroName is null

haozwang<Nabble>
Administrator
yes that would be an issue since it messes with the URL where the reply macro must be accompanied by a node number. As long as the post is made correctly this isn't a serious issue.
Reply | Threaded
Open this post in threaded view
|

Re: After Post, restarting browser = Error 500 macroName is null

MichaelAtOz
When I got the email with your reply it had this at the bottom:
If you reply to this email, your message will be added to the discussion below:
http://support.nabble.com/After-Post-restarting-browser-Error-500-macroName-is-null-tp7600392p7600393.html 
Could you point me to the code doing that please.
Since the change, emails no longer have the post details (it used to have the node number in the emails), so there is nothing to click. The above seems to be a reasonable compromise.

Currently they just have "Sent from: http://forum.openscad.org/" not the particular topic.
Reply | Threaded
Open this post in threaded view
|

Re: After Post, restarting browser = Error 500 macroName is null

haozwang<Nabble>
Administrator
Hi,
I did some further digging and it seems that the mailinglist archive operates a little bit differently from the normal forums. I made a bit of mistake looking at the URL though that its the wrong input to the "reply" macro which is not the case here, my apologies

In the mailing list archive after the post reply did you see a preview message and in the bottom saying something like
"This message was sent from your email to the mailinglist email mailing list.
This message will not appear in this archive until it has been accepted by the mailing list. You may want to save a copy of this message in case it is not accepted. "
?

that is the submission preview page

the error you mentioned I think is that you left it there for two long and browser restarts without remembering what
you did leading up to the point, as in the URL the parameter of "macro" is missing.  do you follow?

It seems strange because I got email from this post with the message in it....
Reply | Threaded
Open this post in threaded view
|

Re: After Post, restarting browser = Error 500 macroName is null

MichaelAtOz
Yes it was labled 'preview', but not the original preview, via pressing the Preview Message button.




After I press Post Message it also says Preview ie



That is where, if I do not navigate away (I usually switch to another tab/window), then later restart the browser, I get the OP error.