Problem Note 56179: An exception with code 1201 might be generated when switching tasks in a SASĀ® Merchandise Planning worksheet
In SAS Merchandise Planning, an exception with code 1201 might be generated with exception details similar to the following in the log:
<Error code="IPC_CONNECTION_BROKEN" userMessage="A client connection could not be established,because the planning process
or network is down." systemMessage="Connection reset" level="4" />
at com.sas.retail.merchplan.Interface.me.adapter.LocalDPEAdapter.handleIPCException(LocalDPEAdapter.java:155)
at com.sas.retail.merchplan.Interface.me.adapter.LocalDPEAdapter.open(LocalDPEAdapter.java:88)
at com.sas.retail.merchplan.Interface.me.command.OpenCommand.process(OpenCommand.java:474)
at com.sas.retail.merchplan.Interface.me.command.AbstractMECommand.execute(AbstractMECommand.java:69)
at com.sas.retail.merchplan.Interface.me.command.OpenCommand.execute(OpenCommand.java:44)
at com.sas.retail.merchplan.Interface.me.MMXMEInterfaceManager.open(MMXMEInterfaceManager.java:163)
at com.sas.retail.merchplan.Interface.servlet.MMXWorksheetInterfaceServlet.callPE(MMXWorksheetInterfaceServlet.java:265)
at com.sas.retail.merchplan.Interface.servlet.MMXWorksheetInterfaceServlet.doGet(MMXWorksheetInterfaceServlet.java:97)
at com.sas.retail.merchplan.Interface.servlet.MMXWorksheetInterfaceServlet.doPost(MMXWorksheetInterfaceServlet.java:91)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at com.sas.retail.merchplan.util.ValidateSessionFilter.doFilter(ValidateSessionFilter.java:38)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at com.sas.retail.merchplan.framework.coe.web.RequestFilter.doFilter(RequestFilter.java:37)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at com.sas.retail.merchplan.util.XSSFilter.doFilter(XSSFilter.java:27)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:581)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:929)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.ha.tcp.ReplicationValve.invoke(ReplicationValve.java:333)
at org.apache.catalina.ha.session.JvmRouteBinderValve.invoke(JvmRouteBinderValve.java:219)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1002)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
This exception is generated when navigating through all subtasks and then switching tasks in a worksheet.
As a workaround for this exception, you can add the maxPostSize=0 attribute to the Connector element in server.xml configuration file for each SAS® Web Application Server.
Operating System and Release Information
SAS System | SAS Merchandise Financial Planning | Microsoft Windows Server 2008 R2 | 6.5_M1 | 6.6 | 9.4 TS1M2 | 9.4 TS1M2 |
64-bit Enabled AIX | 6.5_M1 | 6.6 | 9.4 TS1M2 | 9.4 TS1M2 |
Linux for x64 | 6.5_M1 | 6.6 | 9.4 TS1M2 | 9.4 TS1M2 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2015-08-12 13:49:03 |
Date Created: | 2015-07-14 10:37:39 |