[sakai-core-team] [sakai-dev] QA showstopping bug on trunk

Matthew Jones matthew at longsight.com
Tue Apr 14 06:44:41 PDT 2015


Thanks, the nightly trunk servers do drop and auto.ddl the databases
nightly. Currently the 10.x ones don't. But if you need conversion scripts
or database changes for 10.x they should also be included in

https://github.com/sakaiproject/sakai/blob/master/reference/docs/conversion/sakai_11_mysql_conversion.sql
and
https://github.com/sakaiproject/sakai/blob/master/reference/docs/conversion/sakai_11_oracle_conversion.sql

On Tue, Apr 14, 2015 at 9:31 AM, Fish, Adrian <a.fish at lancaster.ac.uk>
wrote:

>  I know what the issue is, I think. A schema update is needed and I should
> have realised that. Sorry for wasting people’s time :(
>
>  I’ll have a look tonight. The db changes basically add a realm from
> which the roles are copied during site creation.
>
>  Again, my apologies.
>
>  Adrian.
>
>   ======================================
>  Adrian Fish
> Analyst Programmer
> ISS
> Lancaster University
> Bailrigg
> Lancaster
> United Kingdom
> LA1 4YW
>
>  https://dialangweb.lancaster.ac.uk
> https://www.linkedin.com/pub/adrian-fish/6/a12/665
>
>
>
>
>  On 14 Apr 2015, at 14:24, Matthew Jones <matthew at longsight.com> wrote:
>
>  Just some initial info, I looked at it this morning.
>
>  The trunk build failed last night (April 14 3AM) so nothing new was
> deployed so this would have been from the trunk build on or before April
> 13th 3AM.
>
>  I updated a couple of tools individually and got the error when I rolled
> on a new site-manage. The PR that went into site-manage right before the
> 3AM build was SAK-28084, reverting that makes this bug go away. That
> changes 4 tools, but just redeploying site-manage fixes this bug. I haven't
> looked specifically at what's going on, there's no stack trace until the
> site is created unsuccessfully.
>
>  Neal created a new ticket as
> https://jira.sakaiproject.org/browse/SAK-29254
>
>  I can try a rebuild whenever this is fixed.
>
>
> On Tue, Apr 14, 2015 at 8:14 AM, Neal Caidin <neal.caidin at apereo.org>
> wrote:
>
>> Hi Sakai Core Team,
>>
>>  Is anyone available to research this? See below.
>>
>>  I was hoping to have a round of testing this week on trunk. Marist
>> volunteered to spin up a QA server with a snapshot of trunk, but we are
>> still seeing this error. One cannot seem to get into a site after it is
>> created.
>>
>>  I was planning on starting the testing cycle this afternoon, if
>> possible. I was heading over to Durham Tech to do some testing with them.
>> And it seems like Marist and Rutgers might have student workers available.
>>
>>  Thanks,
>> Neal
>>
>>  ---------- Forwarded message ----------
>> From: Warwick Chapman <warwickchapman at gmail.com>
>> Date: Mon, Apr 13, 2015 at 11:46 PM
>> Subject: Re: [sakai-dev] QA showstopping bug on trunk
>> To: Neal Caidin <neal.caidin at apereo.org>
>> Cc: Matthew Jones <matthew at longsight.com>, "
>> sakai-qa at collab.sakaiproject.org QA" <sakai-qa at collab.sakaiproject.org>,
>> sakai-dev <sakai-dev at apereo.org>
>>
>>
>> As admin, at:
>> https://trunk-mysql.nightly.sakaiproject.org/portal/site/16a2160c-e210-436e-bf1a-4ccf4059f024
>>
>>  Technical Details
>>
>> This information will automatically be included in your bug report.
>>
>>  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)
>>
>>
>> user: admin
>>
>> usage-session: 2847df80-4b0c-4278-92a6-e32f9e23c9b8
>>
>> time: Apr 13, 2015 23:43:03
>>
>>
>>  -- Warwick Bruce Chapman | +27 83 7797 094 | http://warwickchapman.com
>>
>> On Mon, Apr 13, 2015 at 3:06 PM, Neal Caidin <neal.caidin at apereo.org>
>> wrote:
>>
>>> 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 <matthew at longsight.com>
>>> 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 <neal.caidin at apereo.org>
>>>> 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 sakai-dev+unsubscribe at apereo.org.
>>>>> To post to this group, send email to sakai-dev at apereo.org.
>>>>> Visit this group at
>>>>> http://groups.google.com/a/apereo.org/group/sakai-dev/.
>>>>>
>>>>
>>>>
>>>
>>>  --
>>> 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 sakai-dev+unsubscribe at apereo.org.
>>> To post to this group, send email to sakai-dev at apereo.org.
>>> Visit this group at
>>> http://groups.google.com/a/apereo.org/group/sakai-dev/.
>>>
>>
>>
>>
>> _______________________________________________
>> sakai-core-team mailing list
>> sakai-core-team at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-core-team
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-core-team/attachments/20150414/8a642120/attachment-0001.html 


More information about the sakai-core-team mailing list