44473 - 'weblogic.rjvm.PeerGoneException' when loading dimension members

Problem Note 44473: 'weblogic.rjvm.PeerGoneException' when loading dimension members

Loading a dimension containing more than 100,000 members into the SAS^® Solutions Data Mart might result in an error similar to the following:

weblogic.rjvm.PeerGoneException: ; nested exception is: java.io.EOFException

Also, an error similar to the following might be written to the <SASSolutionsServices5.x.log> file.

09-26 13:54:51,704 ERROR DimensionImportManagerBean runETLDimension() - u:sasdemo - Error committing dimension updates dimension: GEOGRAPHY. com.sas.solutions.odcs.client.ODCSRuntimeException: weblogic.rjvm.PeerGoneException: ; nested exception is: java.io.EOFException at com.sas.solutions.odcs.client.ETLDelegate.etlDimension(ETLDelegate.java:41) at com.sas.solutions.odcs.client.ETLDelegate.etlDimension(ETLDelegate.java:46) at com.sas.solutions.etl.metadata.ejb.DimensionImportManagerBean.runETLDimension(DimensionImportManagerBean.java:881) at com.sas.solutions.etl.metadata.ejb.DimensionImportManagerBean.load(DimensionImportManagerBean.java:374) at com.sas.solutions.etl.metadata.ejb.DimensionImportManagerBean.load(DimensionImportManagerBean.java:542) at com.sas.solutions.etl.metadata.ejb.DimensionImportManager_uld1m4_ELOImpl.load(DimensionImportManager_uld1m4_ELOImpl.java:58) at com.sas.solutions.etl.metadata.ejb.ExecuteMessageDrivenBean.onMessage(ExecuteMessageDrivenBean.java:198) at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466) at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371) at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659) at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345) at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821) at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115) at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is: java.io.EOFException at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234) at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348) at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259) at com.sas.solutions.odcs.ejb.DimensionManager_xlnk0y_EOImpl_1033_WLStub.etlDimension(Unknown Source) at com.sas.solutions.odcs.client.ETLDelegate.etlDimension(ETLDelegate.java:38) ... 17 more Caused by: java.io.EOFException at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:338) at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:768) at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:702) at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:92) at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29) at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)

This problem might be circumvented by increasing the 'HTTP Post Timeout' setting to 60 seconds for SASServer3 and SASServer4, as follows:

Access the Oracle WebLogic Server Administration Console via
http://servername:7501/console
The default log on credentials are
Username: weblogic
Password: AdminAdmin1
but this might be different at your site.

From the Home Page, select 'Lock & Edit'.

Select 'Servers', from under the 'Environment heading in the 'Domain Configurations' section.

In the 'Servers' table, select 'SASServer3'.

Under 'Settings for SASServer3', select the 'Protocols' tab and then select the 'HTTP' tab.

Change the 'Post Timeout' value to 60 (seconds).

Select 'Activate Changes'. You should see the message "Settings updated successfully".

Repeat the above steps for SASServer4.

Restart your SASServer3 and your SASServer4 application servers.

If in doubt, please contact SAS Technical Support for assistance with modifying the 'HTTP Post Timeout' setting.

For default SAS Financial Management log locations, please refer to SAS Note 20058.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
Product Family	Product	System	Reported	Fixed*	Reported	Fixed*
SAS System	SAS Financial Management	Microsoft® Windows® for x64	5.2	5.3		9.3 TS1M1
		Microsoft Windows Server 2003 Datacenter Edition	5.2	5.3		9.3 TS1M1
		Microsoft Windows Server 2003 Enterprise Edition	5.2	5.3		9.3 TS1M1
		Microsoft Windows Server 2003 Standard Edition	5.2	5.3		9.3 TS1M1
		Microsoft Windows Server 2003 for x64	5.2	5.3		9.3 TS1M1
		Microsoft Windows Server 2008	5.2	5.3		9.3 TS1M1
		Microsoft Windows Server 2008 for x64	5.2	5.3		9.3 TS1M1
		Microsoft Windows XP Professional	5.2	5.3		9.3 TS1M1
		Windows 7 Enterprise 32 bit	5.2	5.3		9.3 TS1M1
		Windows 7 Enterprise x64	5.2	5.3		9.3 TS1M1
		Windows 7 Professional 32 bit	5.2	5.3		9.3 TS1M1
		Windows 7 Professional x64	5.2	5.3		9.3 TS1M1
		Windows 7 Ultimate 32 bit	5.2	5.3		9.3 TS1M1
		Windows 7 Ultimate x64	5.2	5.3		9.3 TS1M1
		Windows Vista	5.2	5.3		9.3 TS1M1
		Windows Vista for x64	5.2	5.3		9.3 TS1M1

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

Type:	Problem Note
Priority:	medium

Date Modified:	2011-10-19 10:11:15
Date Created:	2011-09-29 13:30:42