Hi,
These are all purely client-side and don't seem to affect other functionality (we'll get round to resolving these soon, as they're mostly resource issues); we get nothing in the console for the sign in page.
We don't see anything specific in the Tomcat logs when we hit the sign in page, although we do occasionally get things like:
108:48:22,992 ERROR [ajp-bio-8009-exec-4][IncludeTag:253] Current URL /home;jsessionid=9A8137A512C61F1ABF3E7B25246C9B08 generates exception: com.liferay.portal.security.auth.PrincipalException
208:48:22,994 ERROR [ajp-bio-8009-exec-4][IncludeTag:154] com.liferay.portal.security.auth.PrincipalException
3 at com.liferay.portlet.asset.service.permission.AssetEntryPermission.check(AssetEntryPermission.java:57)
4 at com.liferay.portlet.asset.service.impl.AssetEntryServiceImpl.incrementViewCounter(AssetEntryServiceImpl.java:130)
5 at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:122)
6 at com.liferay.portal.spring.transaction.TransactionInterceptor.invoke(TransactionInterceptor.java:71)
7 at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
8 at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:57)
9 at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
10 at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:57)
11 at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
12 at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:57)
13 at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
14 at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:57)
15 at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
16 at com.liferay.portal.spring.aop.ServiceBeanAopProxy.invoke(ServiceBeanAopProxy.java:211)
17 at com.liferay.portlet.asset.service.AssetEntryServiceUtil.incrementViewCounter(AssetEntryServiceUtil.java:94)
18 at org.apache.jsp.html.portlet.asset_005fpublisher.display.full_005fcontent_jsp._jspService(full_005fcontent_jsp.java:1258)
19 at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
20 at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
21 at com.liferay.portal.servlet.DirectRequestDispatcher.include(DirectRequestDispatcher.java:97)
22 at com.liferay.portal.servlet.PACLRequestDispatcherWrapper.doDispatch(PACLRequestDispatcherWrapper.java:90)
As well as the odd null pointer that we'd been seeing on the old server since upgrading and losing our old themes.
Tomcat access log for the page shows:
12.30.155.8 - - [09/Sep/2012:09:02:35 +0000] "GET /home?p_p_id=58&p_p_lifecycle=0&p_p_state=maximized&p_p_mode=view&saveLastPath=0&_58_struts_action=%2Flogin%2Flogin HTTP/1.1" 200 4646
22.30.155.8 - - [09/Sep/2012:09:02:40 +0000] "GET /c/portal/login?p_l_id=494076 HTTP/1.1" 302 -
32.30.155.8 - - [09/Sep/2012:09:02:41 +0000] "GET /home?p_p_id=58&p_p_lifecycle=0&p_p_state=maximized&p_p_mode=view&saveLastPath=0&_58_struts_action=%2Flogin%2Flogin HTTP/1.1" 304 -
What we did in this case was to mysqldump the database from one system and recreate it on the new, copy over the webapps and other liferay directories (data, etc.) and then start things up. Everything came back except the issue here (unless there are other things we haven't found yet because they're masked by this).
We didn't have similar issues before when upgrading, which also involved moving chunks of the pre-existing stuff around.
There are two key differences to our old server:
1) Rather than running the server from /opt/liferay, it now lives in the /home partition, with symlinks recreating the previous structure. Inside the liferay directories, the structure is unchanged.
2) We're now running through mod_jk rather than raw Tomcat. The issue seems to be there whether we connect at 80 or 8080, so I don't think this has anything to do with the issue.
Interestingly, we no longer seem to see the /web/guest bit any more, though we haven't changed any settings around this.
Does any of this suggest anything?
Many thanks,
Phil.
Por favor, faça login para denunciar.