[Building Sakai] tomcat crashes after several "complete: nowhere set to go, going to portal"

[Matthew Buckett]

2014-01-23 16:47:01.198 [INFO]
org.sakaiproject.login.tool.LoginTool:503 - complete: nowhere set to
go, going to portal

These are logins which don't have a URL to return to after completing
the login so Sakai will send the user back to the main portal URL
(normally /portal).

This can happen when people lost their session or aren't accepting
cookies as the return URL is stored in the users session. So if you
load balancer redirected a set of sessions from one node to another
and some of them where partway through login the node that handled the
rest of their login workflow wouldn't have had a return URL.

I'd be more worried about the:

com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
Communications link failure

which looks like you lost communication with your DB server.

On 24 January 2014 18:07, Sanghyun Jeon <euksa99 at gmail.com> wrote:
> We are using sakai 2.8.x and tomcat 5 and mysql 5.1
>
> Yesterday afternoon, we noticed Sakai slowness and finally one of four
> tomcat instances was crashed. Tomcat log around crashing time generated a
> lot of "complete: nowhere set to go, going to portal" not warning, but info.
>
> I am wondering what exactly this INFO means and I am also wondering whether
> the INFO is related with tomcat crashed.
>
> I attached the part of tomcat log below and thank you.
>
>
>
>
> 2014-01-23 16:38:58.330 [WARN]
> org.sakaiproject.lessonbuildertool.tool.producers.ShowPageProducer:453 -
> ShowPage item not in page2014-01-23 16:40:52.492 [INFO]
> org.sakaiproject.login.tool.LoginTool:503 - complete: nowhere set to go,
> going to portal2014-01-23 16:41:05.442 [INFO]
> org.sakaiproject.login.tool.LoginTool:503 - complete: nowhere set to go,
> going to portal2014-01-23 16:45:59.163 [WARN]
> org.sakaiproject.lessonbuildertool.tool.producers.ShowPageProducer:453 -
> ShowPage item not in page2014-01-23 16:46:13.049 [INFO]
> org.sakaiproject.login.tool.LoginTool:503 - complete: nowhere set to go,
> going to portal2014-01-23 16:46:45.182 [WARN]
> org.sakaiproject.access.tool.AccessServlet:467 - doLogin - proceeding with
> null HELPER_DONE_URL
> 2014-01-23 16:46:45.184 [INFO] org.sakaiproject.login.tool.LoginTool:503 -
> complete: nowhere set to go, going to portal2014-01-23 16:47:01.194 [WARN]
> org.sakaiproject.access.tool.AccessServlet:467 - doLogin - proceeding with
> null HELPER_DONE_URL
> 2014-01-23 16:47:01.198 [INFO] org.sakaiproject.login.tool.LoginTool:503 -
> complete: nowhere set to go, going to portal
> 2014-01-23 16:47:38.728 [INFO] org.sakaiproject.login.tool.LoginTool:503 -
> complete: nowhere set to go, going to portal2014-01-23 16:48:04.547 [INFO]
> org.sakaiproject.login.tool.LoginTool:503 - complete: nowhere set to go,
> going to portal2014-01-23 16:48:19.759 [INFO]
> org.sakaiproject.login.tool.LoginTool:503 - complete: nowhere set to go,
> going to portal2014-01-23 16:50:15.140 [INFO]
> org.sakaiproject.login.tool.LoginTool:503 - complete: nowhere set to go,
> going to portal2014-01-23 16:57:43.316 [WARN]
> org.sakaiproject.db.impl.BasicSqlService:586 - Sql.dbRead: sql: select
> TOOL_ID, REGISTRATION, TITLE, LAYOUT_HINTS, PAGE_ORDER from SAKAI_SITE_TOOL
> where PAGE_ID = ? order by PAGE_ORDER ASC
> a52c62e1-2414-4209-861d-1b69da15cac9com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
> Communications link failure
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org
> with a subject of "unsubscribe"



-- 
  Matthew Buckett, VLE Developer, IT Services, University of Oxford