Problem Note 47332: "Failed to connect to server" error is encountered after logging in to the SAS® Merchandise Solutions Configuration Workbench
The following error might be generated after logging in to the SAS Merchandise Solutions Configuration Workbench:
Failed to connect to server.
In addition, the following exception is generated in the MerchIntelWorkbenchSvr.log:
java.lang.OutOfMemoryError: PermGen space
at sun.misc.Unsafe.defineClass(Native Method)
at sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:45)
at sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381)
at java.security.AccessController.doPrivileged(Native Method)
at sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377)
at sun.reflect.MethodAccessorGenerator.generateSerializationConstructor(MethodAccessorGenerator.java:95)
at sun.reflect.ReflectionFactory.newConstructorForSerialization(ReflectionFactory.java:313)
at java.io.ObjectStreamClass.getSerializableConstructor(ObjectStreamClass.java:1327)
at java.io.ObjectStreamClass.access$1500(ObjectStreamClass.java:52)
at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:437)
at java.security.AccessController.doPrivileged(Native Method)
at java.io.ObjectStreamClass.(ObjectStreamClass.java:413)
at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:310)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1114)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
at org.springframework.remoting.rmi.RemoteInvocationSerializingExporter.doWriteRemoteInvocationResult(RemoteInvocationSerializingExporter.java:158)
at org.springframework.remoting.httpinvoker.HttpInvokerServiceExporter.writeRemoteInvocationResult(HttpInvokerServiceExporter.java:173)
at org.springframework.remoting.httpinvoker.HttpInvokerServiceExporter.writeRemoteInvocationResult(HttpInvokerServiceExporter.java:149)
at org.springframework.remoting.httpinvoker.HttpInvokerServiceExporter.handleRequest(HttpInvokerServiceExporter.java:74)
at org.springframework.web.servlet.mvc.HttpRequestHandlerAdapter.handle(HttpRequestHandlerAdapter.java:49)
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:790)
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:719)
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:644)
at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:560)
The errors are generated because there is a memory leak when performing Model Analysis in the SAS Merchandise Solutions Configuration Workbench.
There is no workaround for this issue.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Markdown Optimization | Linux for x64 | 5.2 | 5.2_M1 | 9.3 TS1M0 | 9.3 TS1M0 |
Microsoft® Windows® for x64 | 5.2 | 5.2_M1 | 9.3 TS1M0 | 9.3 TS1M0 |
SAS System | SAS Promotion Optimization | Linux for x64 | 5.2 | 5.2_M1 | 9.3 TS1M0 | 9.3 TS1M0 |
Microsoft® Windows® for x64 | 5.2 | 5.2_M1 | 9.3 TS1M0 | 9.3 TS1M0 |
SAS System | SAS Regular Price Optimization | Linux for x64 | 5.2 | 5.2_M1 | 9.3 TS1M0 | 9.3 TS1M0 |
Microsoft® Windows® for x64 | 5.2 | 5.2_M1 | 9.3 TS1M0 | 9.3 TS1M0 |
SAS System | SAS Retail Forecasting | Linux for x64 | 5.2 | 5.2_M1 | 9.3 TS1M0 | 9.3 TS1M0 |
Microsoft® Windows® for x64 | 5.2 | 5.2_M1 | 9.3 TS1M0 | 9.3 TS1M0 |
*
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: | 2012-08-31 14:40:34 |
Date Created: | 2012-08-27 16:23:36 |