SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 37580: Exiting the user interface while optimization is running results in subsequent logon issues

DetailsHotfixAboutRate It

In the SAS® Revenue Optimization Suite (SAS® Markdown Optimization, SAS® Regular Price Optimization, SAS® Promotion Optimization) and in SAS® Size Profiling, if you exit the user interface (UI) while optimization is occuring, you might prevent all users from being able to logon to the solution.

The UI appears to be attempting a logon. You might also see error messages similar to the following in the distudio.log:

ERROR main com.sas.solutions.di.studio.runtime.internal.StudioApplication -  connection error 
com.sas.solutions.di.server.api.ConnectionException: Failed to connect to server: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: host_name; nested exception is: 
	java.net.ConnectException: Connection refused: connect]
	at com.sas.solutions.di.server.api.SessionFactory.connectionException(SessionFactory.java:254)
	at com.sas.solutions.di.server.api.SessionFactory.createSession(SessionFactory.java:307)
	at com.sas.solutions.di.studio.ConnectionProfile.createSession(ConnectionProfile.java:175)
	at com.sas.solutions.di.studio.pool.SessionPool.createGlobalSession(SessionPool.java:225)
	at com.sas.solutions.di.studio.runtime.internal.StudioApplication.attemptLogin(StudioApplication.java:315)
	at com.sas.solutions.di.studio.runtime.internal.StudioApplication.displayLoginDialog(StudioApplication.java:282)
	at com.sas.solutions.di.studio.runtime.internal.StudioApplication.run(StudioApplication.java:180)
	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:324)
	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
	at org.eclipse.core.launcher.Main.run(Main.java:977)
	at org.eclipse.core.launcher.Main.main(Main.java:952)
......

To work around this issue, you must restart the middle-tier server, object spawner, and the metadata server.

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Regular Price OptimizationMicrosoft Windows Server 2003 Standard Edition3.24.29.1 TS1M3 SP49.2 TS2M3
Microsoft Windows Server 2003 Datacenter Edition3.24.29.1 TS1M3 SP49.2 TS2M3
Microsoft Windows Server 2003 Enterprise Edition3.24.29.1 TS1M3 SP49.2 TS2M3
64-bit Enabled AIX3.24.29.1 TS1M3 SP49.2 TS2M3
SAS SystemSAS Markdown OptimizationMicrosoft Windows Server 2003 Datacenter Edition3.24.29.1 TS1M3 SP49.2 TS2M3
Microsoft Windows Server 2003 Enterprise Edition3.24.29.1 TS1M3 SP49.2 TS2M3
Microsoft Windows Server 2003 Standard Edition3.24.29.1 TS1M3 SP49.2 TS2M3
64-bit Enabled AIX3.24.29.1 TS1M3 SP49.2 TS2M3
SAS SystemSAS Promotion OptimizationMicrosoft Windows Server 2003 Datacenter Edition3.24.29.1 TS1M3 SP49.2 TS2M3
Microsoft Windows Server 2003 Enterprise Edition3.24.29.1 TS1M3 SP49.2 TS2M3
Microsoft Windows Server 2003 Standard Edition3.24.29.1 TS1M3 SP49.2 TS2M3
64-bit Enabled AIX3.24.29.1 TS1M3 SP49.2 TS2M3
SAS SystemSAS Size Profiling64-bit Enabled AIX1.22.29.1 TS1M3 SP49.2 TS2M3
Microsoft Windows Server 2003 Standard Edition1.22.29.1 TS1M3 SP49.2 TS2M3
Microsoft Windows Server 2003 Enterprise Edition1.22.29.1 TS1M3 SP49.2 TS2M3
Microsoft Windows Server 2003 Datacenter Edition1.22.29.1 TS1M3 SP49.2 TS2M3
* 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.