If you are posting allocation rules, seeding data, or running some other ‘I/O intensive process’ in SAS Financial Management Studio and you receive the message

Unknown Error Occurred

in the client application, check your:

• SASManagedServer and your SASODCSServer log files
  (in SAS Financial Management release 4.x) or your
• SASServer3, SASServer4, SASFinancialManagement5.x and SASODCSForSolutions5.x log files
  (release 5.x)

If you see the message:

com.sas.solutions.odcs.client.ODCSRuntimeException: weblogic.rjvm.PeerGoneException

in the logs, the problem might be due to the SAS Financial Management Studio client connection timing out while waiting for the posting to complete on the server. If so, increasing some WebLogic settings might overcome this.

Specifically, try the following:

1. Access the WebLogic Server Administration Console at:

   http://middle-tier-server-name:7501/console
   
   (beginning with SAS Financial Management release 5.x, you might need to use the following URL:
   
   http://middle-tier-server-name:7501/console/console.portal)

   The default log on credentials are:
   
        Username: weblogicadm (for SAS Financial Management release 4.x) or
                         weblogic (for release 5.x)
   
        Password: AdminAdmin1
   
   but these might be different at your site.
2. On the WebLogic Server Home page, select

   Domain Configurations > Network Configuration > Domain
   (for SAS Financial Management release 4.x) or
   
   Domain Configurations > Domain
   (for release 5.x OR for earlier releases running on a 64-bit environment)

3. Select the "JTA" tab.
4. Set the "Timeout Seconds" field to 36000.
   Select "Apply" or "Save".
5. In the left navigation tree, select

   Servers
   (for SAS Financial Management release 4.x) or
   
   Environment > Servers
   (for release 5.x OR for earlier releases running on a 64-bit environment)

6. Select

   SASManagedServer
   (for SAS Financial Management release 4.x) or
   
   SASServer3
   (for release 5.x)

7. Select the "Configuration" tab (in the top row)
   and then select the "Tuning" tab (in the 2nd row).
8. For SAS Financial Management release 5.x only (OR for earlier releases running on a 64-bit environment), select the "Lock & Edit" option in the Change Center before continuing to the following steps.
9. Set "Stuck Thread Max Time" to 36000 seconds and
   set "Stuck Thread Timer Interval" to 6000 seconds. Select "Apply" or "Save".
10. Select "Protocols" tab and then select the "General" tab.
    For SAS Financial Management release 4.x only, also select "Show" for "Advanced Options" under the "General" tab.
11. For SAS Financial Management release 5.x only (OR for earlier releases running on a 64-bit environment) - if you have not already done so, select the "Lock & Edit" option in the Change Center before continuing to the following steps.
12. Set "Complete Message Timeout" to 480 seconds,
    set "Idle Connection Timeout" to 3600 seconds and
    set "Maximum Message Size" to 2000000000 bytes. Select "Apply" or "Save".
13. PLEASE NOTE (for release 5.x OR for earlier releases running on a 64-bit environment):
    If you also see a message in the <SASFinancialManagement5.x> log that is similar to:

    javax.ejb.EJBException: EJB Exception: : com.sas.solutions.odcs.client.ODCSRuntimeException: weblogic.rjvm.PeerGoneException: No message was received for: '240' seconds

    there is one more setting to adjust in the WebLogic Server Administration Console.
    • Select: Environment > Servers.
    • Select SASServer3 (select SASODCSServer if you are running release 4.x on a 64-bit environment).
    • Select the "Configuration" tab (in the top row)
      and then select the "Tuning" tab (in the 2nd row).
    • At the bottom of the page, select 'Advanced'.
    • Increase the 'Idle Periods Until Timeout' value to 10
      (the default value for this setting is 4, with each period consisting of 60 seconds; hence the initial timeout value of 240 seconds).
    • Select "Apply" or "Save".
14. In the left navigation tree, select

    Servers
    (for SAS Financial Management release 4.x) or
    
    Environment > Servers
    (for release 5.x OR for earlier releases running on a 64-bit environment)

15. Select

    SASODCSServer
    (for SAS Financial Management release 4.x) or
    
    SASServer4
    (for release 5.x)

16. Repeat steps 7 - 13, using the identical settings/values as above for the SASODCSServer (release 4.x)/SASServer4 (release 5.x), EXCEPT you should NOT need to perform step 13 if you are using release 4.x (unless you are running on a 64-bit environment)
17. For SAS Financial Management release 5.x (OR for earlier releases running on a 64-bit environment), when you have completed these steps, select the 'Activate Changes' option in the Change Center. A message will indicate that you must restart for the changes to take effect.
18. Restart your SAS Remote/Foundation Services, your SASODCSServer/SASServer4 and your SASManagedServer/SASServer3.

For the default location of SAS Financial Management log files, please refer to SAS Note 20058.

Operating System and Release Information

Product Family	Product	System	SAS Release
			Reported	Fixed*
SAS System	SAS Financial Management	Microsoft Windows 2000 Advanced Server	9.1 TS1M3 SP4
		Microsoft Windows 2000 Datacenter Server	9.1 TS1M3 SP4
		Microsoft Windows 2000 Server	9.1 TS1M3 SP4
		Microsoft Windows 2000 Professional	9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Datacenter Edition	9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Enterprise Edition	9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Standard Edition	9.1 TS1M3 SP4
		Microsoft Windows XP Professional	9.1 TS1M3 SP4
		64-bit Enabled AIX	9.1 TS1M3 SP4
		64-bit Enabled Solaris	9.1 TS1M3 SP4

* 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.

---

How to update settings for the WebLogic application servers to avoid receiving the 'PeerGoneException'.

Type:	Problem Note
Priority:	high

Date Modified:	2011-01-18 13:11:10
Date Created:	2010-07-08 12:07:56