In which Wildbook did the issue occur?
Flukebook
What operating system were you using? MacOS Ventura 13.4
What web browser were you using? Safari
What is your role on the site? admin
What happened?
I am writing to ask about an error message I received when trying to accept a collaboration request? When I click this, I get the error message below.
What are some steps we could take to reproduce the issue?
This is the url with the error message:
https://www.flukebook.org/LoginUser#collaborations
This is the error message:
ype Exception Report
Message Filtered request failed.
Description The server encountered an unexpected condition that prevented it from fulfilling the request.
Exception
javax.servlet.ServletException: Filtered request failed. org.apache.shiro.web.servlet.AbstractShiroFilter.doFilterInternal(AbstractShiroFilter.java:384) org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125) org.ecocean.servlet.StrutsUTF8Filter.doFilter(StrutsUTF8Filter.java:33)
Root Cause
java.lang.NullPointerException org.ecocean.servlet.LoginUser.doPost(LoginUser.java:51) org.ecocean.servlet.LoginUser.doGet(LoginUser.java:38) javax.servlet.http.HttpServlet.service(HttpServlet.java:635) javax.servlet.http.HttpServlet.service(HttpServlet.java:742) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) org.apache.shiro.web.servlet.AbstractShiroFilter.executeChain(AbstractShiroFilter.java:449) org.apache.shiro.web.servlet.AbstractShiroFilter$1.call(AbstractShiroFilter.java:365) org.apache.shiro.subject.support.SubjectCallable.doCall(SubjectCallable.java:90) org.apache.shiro.subject.support.SubjectCallable.call(SubjectCallable.java:83) org.apache.shiro.subject.support.DelegatingSubject.execute(DelegatingSubject.java:387) org.apache.shiro.web.servlet.AbstractShiroFilter.doFilterInternal(AbstractShiroFilter.java:362) org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125) org.ecocean.servlet.StrutsUTF8Filter.doFilter(StrutsUTF8Filter.java:33)
Note The full stack trace of the root cause is available in the server logs.