When you have a SAS^® 9.2 Content Server clustered environment with an IBM WebSphere application–server configuration, the SAS Content Server periodic journal synchronization fails with the following errors:

[06/06/12 00:44:30:272 BST] 0000007a SystemOut     O 2012-06-06 00:44:30,272[ClusterNode-SASG01WIP] ERROR org.apache.jackrabbit.core.util.db.ConnectionHelper - Failed to execute SQL (stacktrace on DEBUG log level)
java.sql.SQLException: Unable to create IStatement handle. 


[06/06/12 00:44:32:042 BST] 0000007a SystemOut     O 2012-06-06 00:44:32,042[ClusterNode-SASG01WIP] ERROR org.apache.jackrabbit.core.cluster.ClusterNode - Periodic sync of journal failed: Unable to return record iterator.
org.apache.jackrabbit.core.cluster.ClusterException: Unable to return record iterator.
    at org.apache.jackrabbit.core.cluster.ClusterNode.sync(ClusterNode.java:305)
    at org.apache.jackrabbit.core.cluster.ClusterNode.run(ClusterNode.java:274)
    at java.lang.Thread.run(Thread.java:811)
Caused by: 
java.sql.SQLException: Unable to create IStatement handle. 

The failure occurs for the secondary WebSphere Java virtual machine (JVM) cluster instances of SASServer2 and SASServer 3.

To solve this problem, follow the steps below. (Note: This solution only applies to a situation with a SAS Content Server clustered environment that has a WebSphere application–server configuration.

1. Navigate to the SAS-configuration-directory\Lev1\AppData\SASContentServer\appserver–instance\ folder. In this path, appserver–instance specifies the specific server instance (for example, SASServer1)
2. Verify that the AppServer_Instance folder name is same as the actual ID name for the WebSphere application–server JVM instance. If the names match, continue to the next step. If the names do not match, rename the folder so that it is the same as the application-server instance ID name.
3. Locate the following line in repository.xml file that resides in SAS-configuration-directory\Lev1\AppData\SASContentServer\AppServer_Instance2\:
   Cluster id="appserver-instance1"
4. Change the value to the correct application–server instance, as shown in this example:
   Cluster id="appserver–instance2"
5. Locate the following Java start-up command for the Websphere server node:
   
   -Dsas.appserver.instance.id=appserver–instance1
   In this command, appserver-instance1 indicates the primary application–server instance.

6. Change the value for the Java command to the following:
   
   -Dsas.appserver.instance.id=appserver–instance2
   In this command, appserver-instance1 specifies the secondary application–server instance.

7. Restart your WebSphere SASServer JVMs.

Operating System and Release Information