Arcot Admin does not come up on restart when the Primary Principal DB is down and SQL mirror up

book

Article ID: 131948

calendar_today

Updated On:

Products

CA Rapid App Security CA Advanced Authentication CA API Gateway

Issue/Introduction

The Broadcom Admin Console cannot be restarted when the Principal DB is kept down and Mirror DB is up . The Admin restart fails with the following error calling for default Port 1433 even when the JDBC string did not specify port 1433. 

"port 1433 has failed. Error: "connect timed out. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.".

Cause

The cause is that that the JDBC string  (in arcotcommon.ini) provided for the Mirror DB (via the parameter failoverPartner=) is found to be incorrect and need to be specified as such. 

URL.1=jdbc:sqlserver://PRIMARY_DB_HOSTNAME;DatabaseName=DBNAME;port=PORTNUMBER; 
failoverPartner=MIRROR_DB_HOSTNAME\\INSTANCE_NAME;selectMethod=cursor 

Note:-please ensure that the "failoverPartner=" has the instance name  and the escape character "\" is provided as in "\\INSTANCE_NAME"

This is indicative of the fact that when making an initial connection when Primary is found down or not reachable, the MS SQL JDBC Driver tries to connect to the Default MS SQL DB port 1433. Hence if the Port 1433 is not open when incorrect JDBC connection string provided (via arcotcommon.ini) for mirror DB, then arcotadmin will come up on a restart.

 

Environment

CA Strong Authenticaton and CA Risk Authentication Admin Console

Resolution

Provide the JDBC sting in arcotcommon.ini as 

URL.1=jdbc:sqlserver://PRIMARY_DB_HOSTNAME;DatabaseName=DBNAME;port=PORTNUMBER; 
failoverPartner=MIRROR_DB_HOSTNAME\\INSTANCE_NAME;selectMethod=cursor 
 

Additional Information

None.