Problem with portal 6.2.0 with Weblogic14

Message Boards

Mihail Ionescu, modified 2 Years ago.

Problem with portal 6.2.0 with Weblogic14

New Member Post: 1 Join Date: 6/4/21 Recent Posts

Hello,

We have a large legacy application which uses version 6.2.0 (I know it is pretty old :)). RIght now, we are trying to migrate our Weblogic from Weblogic 12.1.1 to Weblogic 14.1.1 (which also include an upgrade from Java 6 to Java 8). But we get the following error for all liferay pages:

12:10:39,401 ERROR [[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'][PortletRequestDispatcherImpl:131] javax.servlet.ServletException: weblogic.servlet.jsp.CompilationException: Failed to compile JSP /html/
common/themes/portlet.jsp
portlet.jsp:17:18: Error in "init.jsp" at line 331: The code of method _jspService(HttpServletRequest, HttpServletResponse) is exceeding the 65535 bytes limit
<%@ include file="/html/common/themes/init.jsp" %>
^----------------------------^

javax.servlet.ServletException: weblogic.servlet.jsp.CompilationException: Failed to compile JSP /html/common/themes/portlet.jsp
portlet.jsp:17:18: Error in "init.jsp" at line 331: The code of method _jspService(HttpServletRequest, HttpServletResponse) is exceeding the 65535 bytes limit
<%@ include file="/html/common/themes/init.jsp" %>
^----------------------------^

   at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:313)
   at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:490)
   at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:379)
   at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:25)
   at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:82)
   at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.doFilter(InvokerFilterChain.java:116)
   at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.processDirectCallFilter(InvokerFilterChain.java:188)
   at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.doFilter(InvokerFilterChain.java:96)
   at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilter.doFilter(InvokerFilter.java:96)
   at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:82)
   at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:650)
   at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:518)
   at com.liferay.portlet.PortletRequestDispatcherImpl.dispatch(PortletRequestDispatcherImpl.java:331)
   at com.liferay.portlet.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:128)
   at com.liferay.portal.struts.PortletRequestProcessor.doInclude(PortletRequestProcessor.java:370)
   at com.liferay.portal.struts.PortletRequestProcessor.doForward(PortletRequestProcessor.java:338)
   at org.apache.struts.tiles.TilesRequestProcessor.processTilesDefinition(TilesRequestProcessor.java:239)
   at org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.java:302)
   at com.liferay.portal.struts.PortletRequestProcessor.processForwardConfig(PortletRequestProcessor.java:478)
   at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:241)

(actually the stacktrace is longer, if anyone needs more information I can provide).

Is there anything we can do, short of migrating to another Liferay version?

Thanks,

Mihai

Olaf Kock, modified 2 Years ago.

RE: Problem with portal 6.2.0 with Weblogic14

Liferay Legend Posts: 6403 Join Date: 9/23/08 Recent Posts

As a minimum, you should be on the latest GA of 6.2 with a security patch if you insist being on 6.2. That would be the easiest upgrade that you can try to run on newer Weblogic servers.

Note that 6.2.0 has been released in 2013, while Weblogic 14 was released in 2020. That means nobody has ever tried running the ancient release on that appserver. Whatever your reason for upgrading Weblogic (likely: no-more-support or security-issues): Apply the same reason to your Liferay infrastructure.