Re: 500 error when inviting new blog admin

Um ... sorry ... my mistake, the second invite immediately after the first *did* result in a 500 this time, but this time for a different reason:

Caused by: java.lang.NoClassDefFoundError: javax/activation/DataSource
        at org.apache.roller.weblogger.util.MailUtil.sendMessage(MailUtil.java:577) ~[classes/:?]

However, that appears to be a configuration problem - ie, no mail server designated. So probably unrelated.


On 2021/03/17 15:54:41, Rich Bowen <[email protected]> wrote: 
> Hi, folks,
> 
> I have just added some people to the Conferences section of blogs.apache.org, as authors. Each time, the server returns a 500 error, but the user is successfully added.
> 
> The error message, which is extremely lengthy, starts with:
> 
> 15:45:43.850 [http-nio-8080-exec-747] ERROR org.apache.struts2.dispatcher.DefaultDispatcherErrorHandler - Exception occurred during processing request: Method "save" failed for object org.apache.roller.weblogger.ui.struts2.editor.MembersInvite@51d2271
> ognl.MethodFailedException: Method "save" failed for object org.apache.roller.weblogger.ui.struts2.editor.MembersInvite@51d2271
>         at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:1932) ~[ognl-3.1.26.jar:?]
>         at ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:68) ~[ognl-3.1.26.jar:?]
>         at com.opensymphony.xwork2.ognl.accessor.XWorkMethodAccessor.callMethodWithDebugInfo(XWorkMethodAccessor.java:98) ~[struts2-core-2.5.22.jar:2.5.22]
> 
> 
> This is apparently caused by ...
> 
> 
> Caused by: java.lang.ClassNotFoundException: javax.activation.DataSource
> 
> 
> Infra can provide the whole error message if that would be at all helpful.
> 
> This appears to happen when the server has been idle for a very long time. ie, if I invite someone, this happens, but if I do a second one right away, I do not get the 500 error. Trying again the next morning, I get the 500 error again. This seems to suggest some kind of data connection timeout?
> 
> Anyways, thanks, as always, for a great tool, and let me know if I can provide any further information.
> 
>