Note: This SAS Note applies to SAS^® Financial Management 5.3 and earlier releases.

If you are running a large process (such as posting a large number of allocation rules) in SAS^® Financial Management, you might encounter an "Unknown Error" message in SAS Financial Management Studio or see a message similar to the following:

You might also see messages similar to the following written to one or more of these logs:

• SASManagedServer (SAS Financial Management release 4.x)/SASFinancialManagement5.x log (release 5.x)
• the SASODCSServer (release 4.x)/SASODCSForSolutions 5.x log (release 5.x)

This message indicates that the processing time has exceeded the specified time-out values and that the time-out values likely need to be increased.

To increase the time-out values, complete these steps:

1. Access the log where the "Transaction timed out" error was written.


2. Immediately following the "Transaction timed out" error, you should see the bean where the time-out value is being exceeded. Here is an example:
   Transaction timed out after 3600 seconds Name=[EJB com.sas.solutions.finance.models.cycle.ejb.CycleSeedingBean.
   This message indicates that the time-out value of 3600 seconds for the CycleSeedingBean is being exceeded.


3. On the middle tier server, navigate to the following paths:
   • For SAS Financial Management release 4.x: your-drive:\bea\user_projects\domains\SASSolutions\applications\sas.solutions.finance.ear and use WinZip to open the sas.solutions.finance.server jar file.
   • For SAS Financial Management release 5.x: your-drive:\SAS\Config\Lev1\Web\Staging\sas.financialmanagement5.x.ear and use 7-Zip (and only 7-Zip) to open the sas.solutions.finance.server jar file.
     Note: For SAS Financial Management 5.x, you might also need to use 7-Zip to open the sas.financialmanagement5.x ear file
   
   If you do not have 7-Zip, you can download it for free from http://www.7zip.com/.
   If you do not have WinZip, you can download it from http://www.winzip.com/win/en/index.htm/.
   


4. For SAS Financial Management release 4.x: After you unzip the sas.solutions.finance.server jar file, EXTRACT the weblogic-ejb-jar.xml file to the C: root directory on the middle tier machine.
   
   For SAS Financial Management release 5.x: Access the META-INF directory within the sas.solutions.finance.server jar file and then use a standard text editor to open the weblogic-ejb-jar.xml file.


5. For SAS Financial Management release 4.x: Navigate to the C:\META-INF directory and use a standard text editor to open the weblogic-ejb-jar.xml file.


6. Using the above example, search the weblogic-ejb-jar.xml file for <ejb-name>CycleSeedingBean</ejb-name>.
   If you find an entry that looks similar to the following, then adjust the trans-timeout-seconds value as needed (see step 7, below):
   <weblogic-enterprise-bean> <ejb-name>CycleSeedingBean</ejb-name> <stateless-session-descriptor> </stateless-session-descriptor> <transaction-descriptor> <trans-timeout-seconds>3600</trans-timeout-seconds> </transaction-descriptor> <reference-descriptor> <ejb-local-reference-description> <ejb-ref-name>ejb/sas/solutions/finance/FMSLocalEJBLookupLocal</ejb-ref-name> <jndi-name>ejb/sas/solutions/finance/FMSLocalEJBLookupLocal</jndi-name> </ejb-local-reference-description> </reference-descriptor> <jndi-name>ejb/sas/solutions/finance/CycleSeedingBean</jndi-name> <local-jndi-name>CycleSeedingBeanLocal</local-jndi-name> </weblogic-enterprise-bean>
   If you do not find a trans-timeout-seconds entry for the appropriate beans, you must then create a new entry so it resembles the entry above.
   
   IMPORTANT NOTE: Be careful if you plan to copy an existing entry to create a new entry, because existing entries might contain information that is specific to a particular bean, such as the JNDI-NAME or the EJB-REF-NAME information, and might have unintended results if applied to an improper bean.


7. A general rule for adjusting the trans-timeout-seconds value is to double the amount currently allocated. For example, if the current value 3600 as shown above, adjust the value in the weblogic-ejb-jar.xml file to 7200 for the appropriate beans and save the file.


8. For SAS Financial Management release 4.x: Return to WinZip on the mid-tier server and select ADD. Select the weblogic-ejb-jar.xml file and select the Save full path info option in the FOLDERS area of the dialog box.
   
   For SAS Financial Management release 5.x: After you have made your edits to the weblogic-ejb-jar.xml file, save and close the file. Click OK when prompted by 7-Zip to update the file in the archive and then exit out of 7-Zip.


9. Restart your SAS Remote/Foundation Services, SASODCSServer/SASServer4, and SASManagedServer/SASServer3 in order for the new settings to take effect.

Operating System and Release Information