Note: This SAS note applies to SAS® Financial Management 5.3 and earlier releases.
If you are executing a large process in SAS Financial Management, such as posting a large number of adjustments/adjustment rules, you might encounter situations in which SAS Financial Management connections are timing out while waiting for the process to complete on the application server.
For example, you might encounter a message in SAS Financial Management Studio that is similar to the following:
Some or all of the allocation rules failed to post, please see the Log.
If you see this error, check the SASFinancialManagement5.x log file. If you see a message similar to the following, there is a time-out setting that is causing the session to go into hibernate mode:
ERROR LazyInitializationException could not initialize proxy - no Session
org.hibernate.LazyInitializationException: could not initialize proxy - no Session
at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:57)
at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:111)
at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:150)
at com.sas.solutions.finance.models.rules.persistence.Rule$$EnhancerByCGLIB$$6b853ed5.isReady()
at com.sas.solutions.finance.models.cycle.ejb.ResultRuleManagerBean.executeSingleRule(ResultRuleManagerBean.java:1478)
at com.sas.solutions.finance.models.cycle.ejb.ResultRuleManager_jzt93k_ELOImpl.executeSingleRule(ResultRuleManager_jzt93k_ELOImpl.java:1023)
at com.sas.solutions.finance.models.cycle.ejb.ResultRuleManagerBean.executeImpl(ResultRuleManagerBean.java:1552)
at com.sas.solutions.finance.models.cycle.ejb.ResultRuleManagerBean.execute(ResultRuleManagerBean.java:811)
at com.sas.solutions.finance.models.cycle.ejb.ResultRuleManager_jzt93k_ELOImpl.execute(ResultRuleManager_jzt93k_ELOImpl.java:787)
at com.sas.solutions.finance.models.cycle.ejb.ResultManagerBean.execute(ResultManagerBean.java:980)
at com.sas.solutions.finance.models.cycle.ejb.ResultManager_a2htm8_EOImpl.execute(ResultManager_a2htm8_EOImpl.java:2557)
...
Begin by estimating the amount of time from when you initiated the process until when the error message was encountered. Assuming the time was approximately 30 minutes, you would want to check the time-out values for the beans that are specified in the error message. In the above example, you would check the <ResultRuleManagerBean> and the <ResultManagerBean>.
After identifying the specific beans, see SAS Note 39559 for information on modifying SAS Financial Management Enterprise JavaBean time-out values. Note that time time-out values are specified in seconds. So a value of 1800 would be 30 minutes, a value a 3600 would be 60 minutes, and so on.
Note: If your process unexpectedly terminates and you encounter messages similar to the following in the SASFinancialManagement5.x log while executing your process, see SAS Note 40270 for information about modifying WebLogic server connection time-out values:
com.sas.solutions.odcs.client.ODCSRuntimeException: weblogic.rjvm.PeerGoneException
If your process unexpectedly terminates and you encounter messages similar to the following in the SASFinancialManagement5.x log while executing your process, see SAS Note 39559 for information about modifying SAS Financial Management Enterprise JavaBean time-out values:
Transaction timed out after 3600 seconds
Name=[EJB com.sas.solutions.finance.models.cycle.ejb.CycleSeedingBean
See SAS Note 20058 for the default location of SAS Financial Management logs.
Operating System and Release Information
SAS System | SAS Financial Management | Microsoft® Windows® for x64 | 5.1 | | 9.2 TS2M0 | |
Microsoft Windows Server 2003 Datacenter Edition | 5.1 | | 9.2 TS2M0 | |
Microsoft Windows Server 2003 Enterprise Edition | 5.1 | | 9.2 TS2M0 | |
Microsoft Windows Server 2003 Standard Edition | 5.1 | | 9.2 TS2M0 | |
Microsoft Windows Server 2003 for x64 | 5.1 | | 9.2 TS2M0 | |
Microsoft Windows Server 2008 for x64 | 5.1 | | 9.2 TS2M0 | |
Microsoft Windows XP Professional | 5.1 | | 9.2 TS2M0 | |
Windows Vista | 5.1 | | 9.2 TS2M0 | |
Windows Vista for x64 | 5.1 | | 9.2 TS2M0 | |
*
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.