SUPPORT / SAMPLES & SAS NOTES
Problem Note 49319: Java exception occurs when attempting to open Markdown Approvals view
 |  |  |  |  |
When opening the Markdown Approvals view in SAS® High-Performance Markdown Optimization, the following Java exception might be generated:
java.lang.reflect.UndeclaredThrowableException
at $Proxy14.getMarkdownsByProduct(Unknown Source)
at com.sas.solutions.di.studio.mdo.jobs.AbstractMDOJob.retrieveMarkdownsByPlanDetail(AbstractMDOJob.java:1132)
at com.sas.solutions.di.studio.mdo.jobs.AbstractMDOJob.retrieveMarkdownsByPlanDetail(AbstractMDOJob.java:1092)
at com.sas.solutions.di.studio.mdo.jobs.LoadMarkdownsJob.execute(LoadMarkdownsJob.java:86)
at com.sas.solutions.di.commons.jobs.AbstractJob.internalExecute(AbstractJob.java:432)
at com.sas.solutions.di.commons.jobs.AbstractJob.run(AbstractJob.java:401)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.sas.solutions.di.server.api.ServerException: org.hibernate.PropertyAccessException: Null value was assigned to a property of primitive type setter of com.sas.solutions.di.server.mdo.api.Markdown.markdownLoss
at com.sas.solutions.di.server.util.Interceptors.toCanonicalThrowable(Interceptors.java:64)
at com.sas.solutions.di.server.util.Interceptors.toCanonicalThrowable(Interceptors.java:55)
at com.sas.solutions.di.server.spring.SpringServer.handleThrowableFromInvoke(SpringServer.java:227)
at com.sas.solutions.di.server.util.Interceptors.handleThrowableFromInvoke(Interceptors.java:33)
at com.sas.solutions.di.server.util.Interceptors.privateInvoke(Interceptors.java:216)
at com.sas.solutions.di.server.spring.SpringServer.invoke(SpringServer.java:173)
at com.sas.solutions.di.server.spring.SessionRemoteInvocationExecutor.invoke(SessionRemoteInvocationExecutor.java:47)
at org.springframework.remoting.support.RemoteInvocationBasedExporter.invoke(RemoteInvocationBasedExporter.java:78)
at org.springframework.remoting.support.RemoteInvocationBasedExporter.invokeAndCreateResult(RemoteInvocationBasedExporter.java:114)
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:875)
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809)
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571)
at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:511)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
at org.springframework.remoting.support.RemoteInvocationUtils.fillInClientStackTraceIfPossible(RemoteInvocationUtils.java:47)
at org.springframework.remoting.support.RemoteInvocationResult.recreate(RemoteInvocationResult.java:115)
at org.springframework.remoting.support.RemoteInvocationBasedAccessor.recreateRemoteInvocationResult(RemoteInvocationBasedAccessor.java:85)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.invoke(HttpInvokerClientInterceptor.java:147)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy13.getMarkdownsByProduct(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sas.solutions.di.server.api.ServerProxy.invoke(ServerProxy.java:60)
... 7 more
This exception occurs under the following conditions:
- The FUTURE_PRICE_CHG_EXE_SOURCE global setting is set to 1.
- There is a price change in the frozen week.
- There is a promotion in the frozen week.
Under these conditions, the markdown loss amount value is calculated incorrectly. If it is set to null, the Java exception occurs.
There is no workaround for this issue. However, when it occurs, you can do one of the following in order to approve plan prices for plans that do not have this issue:
- Temporarily change the FUTURE_PRICE_CHG_EXE_SOURCE global setting to 0 and reoptimize the plans with the issue. This causes the system to read the frozen weeks prices from the approval table instead of from the price fact table.
- Mark the plans with the issue as completed through the UI. Markdowns for completed plans do not appear in the approval list and therefore you do not encounter the issue.
A fix for this issue is planned for a future software release.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS High-Performance Markdown Optimization | Microsoft® Windows® for x64 | 4.3_M2 | 5.2 | 9.2 TS2M3 | 9.3 TS1M1 |
| Linux for x64 | 4.3_M2 | 5.2 | 9.2 TS2M3 | 9.3 TS1M1 | ||