[WG: Sakai QA] QA showstopping bug on trunk

classic Classic list List threaded Threaded
3 messages Options
Neal Caidin-3 Neal Caidin-3
Reply | Threaded
Open this post in threaded view
|

[WG: Sakai QA] QA showstopping bug on trunk

[sakai-dev (apereo), sakai-qa (collab)]

Hi all,

After I create a site on nightly trunk server (MySql) [1], I click on the site and I get an unexpected error. Unfortunately, I don't know how to access the stack trace or the log files easily.

Another bug I found, is that one can only create a new site through worksite setup. The shortcut to adding an new site, preferences, and more on the upper right hand side where the user icon is located. Clicking should show a pop-down menu. This is not a showstopper, but seems like a bug.

P.S. I think stack trace should show in GUI by default on QA servers and off by default on production. We have a property already that can do that for us.

[1] Nightly servers - http://nightly2.sakaiproject.org/

Thanks,
Neal



_______________________________________________
sakai-qa mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-qa

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"
Matthew Jones-2 Matthew Jones-2
Reply | Threaded
Open this post in threaded view
|

Re: [WG: Sakai QA] [sakai-dev] QA showstopping bug on trunk

Yeah, we can turn that property on. I believe if you're logged on as admin user you also see the stack traces. 

It should be easy to get setup access to the server logs. The build logs are on jenkins and not public, but easy to see for those of us on with development accounts on github and jenkins.

On Mon, Apr 13, 2015 at 8:54 AM, Neal Caidin <[hidden email]> wrote:
[sakai-dev (apereo), sakai-qa (collab)]

Hi all,

After I create a site on nightly trunk server (MySql) [1], I click on the site and I get an unexpected error. Unfortunately, I don't know how to access the stack trace or the log files easily.

Another bug I found, is that one can only create a new site through worksite setup. The shortcut to adding an new site, preferences, and more on the upper right hand side where the user icon is located. Clicking should show a pop-down menu. This is not a showstopper, but seems like a bug.

P.S. I think stack trace should show in GUI by default on QA servers and off by default on production. We have a property already that can do that for us.

[1] Nightly servers - http://nightly2.sakaiproject.org/

Thanks,
Neal


--
You received this message because you are subscribed to the Google Groups "Sakai Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/a/apereo.org/group/sakai-dev/.


_______________________________________________
sakai-qa mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-qa

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"
Neal Caidin-3 Neal Caidin-3
Reply | Threaded
Open this post in threaded view
|

Re: [WG: Sakai QA] [sakai-dev] QA showstopping bug on trunk

Admin works, for the purpose of getting the stack trace. 

org.sakaiproject.portal.api.PortalHandlerException: java.lang.NullPointerException
    at org.sakaiproject.portal.charon.SkinnableCharonPortal.doGet(SkinnableCharonPortal.java:852)
caused by: java.lang.NullPointerException
    at org.sakaiproject.portal.util.ToolUtils.getPageUrl(ToolUtils.java:138)
    at org.sakaiproject.portal.charon.handlers.SiteHandler.doSite(SiteHandler.java:385)
    at org.sakaiproject.portal.charon.handlers.SiteHandler.doGet(SiteHandler.java:208)
    at org.sakaiproject.portal.charon.SkinnableCharonPortal.doGet(SkinnableCharonPortal.java:852)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
    at org.sakaiproject.util.RequestFilter.doFilter(RequestFilter.java:467)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
    at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
    at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:683)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)
    at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074)
    at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
    at org.apache.tomcat.util.net.AprEndpoint$SocketWithOptionsProcessor.run(AprEndpoint.java:2403)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
    at java.lang.Thread.run(Thread.java:745)



On Mon, Apr 13, 2015 at 8:59 AM, Matthew Jones <[hidden email]> wrote:
Yeah, we can turn that property on. I believe if you're logged on as admin user you also see the stack traces. 

It should be easy to get setup access to the server logs. The build logs are on jenkins and not public, but easy to see for those of us on with development accounts on github and jenkins.

On Mon, Apr 13, 2015 at 8:54 AM, Neal Caidin <[hidden email]> wrote:
[sakai-dev (apereo), sakai-qa (collab)]

Hi all,

After I create a site on nightly trunk server (MySql) [1], I click on the site and I get an unexpected error. Unfortunately, I don't know how to access the stack trace or the log files easily.

Another bug I found, is that one can only create a new site through worksite setup. The shortcut to adding an new site, preferences, and more on the upper right hand side where the user icon is located. Clicking should show a pop-down menu. This is not a showstopper, but seems like a bug.

P.S. I think stack trace should show in GUI by default on QA servers and off by default on production. We have a property already that can do that for us.

[1] Nightly servers - http://nightly2.sakaiproject.org/

Thanks,
Neal


--
You received this message because you are subscribed to the Google Groups "Sakai Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/a/apereo.org/group/sakai-dev/.



_______________________________________________
sakai-qa mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-qa

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"