Usage Note 20859: "Com.sas.services.connection.Cluster getConnection SEVERE: new
connection failed" during Test Connection
A port number is required to connect to the SAS Server. The number is
entered in a textbox in the SAS Server section of the Ini Tab of the SAS
OpRisk VaR 3.2 Configuration Editor. If an application uses an Object
Spawner instead of the Direct Connection, and if the Object Spawner is a
server in the BI / Metadata platform, then using the port number of the
Object Spawner (as found in the Management Console) will make the Test
Connection fail, resulting in the following error message in the SAS
log:
com.sas.services.connection.Cluster getConnection
SEVERE: new connection failed:
org.omg.CORBA.COMM_FAILURE: sam.S217.ex.msg: An exception was thrown
while reading the server's requirements status from the socket.
vmcid:
0x0 minor code: 0 completed: No
at com.sas.net.brg.sam.SocketAccessMethod.establishConnection(Unknown
Source)
at com.sas.net.brg.sam.SocketAccessMethod.connect(Unknown Source)
etc
By using the correct port number in the Ini Tab of the SAS OpRisk VaR
Configuration Editor, you will be able to complete the test connection.
In a BI / Metadata Platform configuration that uses SAS Management
Console to manage the configuration, use the Workspace Server port
number (as found in SAS Management Console), not the Object Spawner port
number (as found in SAS Management Console).
In a stand-alone Object Spawner configuration (an Object Spawner not
part of the BI / Metadata platform), use the Object Spawner port number.
Operating System and Release Information
SAS System | SAS OpRisk VaR Server | Microsoft Windows 2000 Server | 3.2 | | | |
Microsoft Windows XP Professional | 3.2 | | | |
Microsoft Windows 2000 Professional | 3.2 | | | |
Solaris | 3.2 | | | |
Microsoft Windows 2000 Advanced Server | 3.2 | | | |
Microsoft Windows 2000 Datacenter Server | 3.2 | | | |
64-bit Enabled Solaris | 3.2 | | | |
AIX | 3.2 | | | |
64-bit Enabled AIX | 3.2 | | | |
*
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.
Date Modified: | 2007-10-08 10:57:13 |
Date Created: | 2007-08-24 17:24:33 |