Dpa/ignite a database server that is not connected to the monitor due to DNS issues

Problem Description:

The management monitoring interface of DPA (Ignite) found that two SQL Server database servers were not connected, and checked their log contents as follows

The specific error log is as follows, Notice: The specific server name in the log was replaced by my servername.

DATE:2/9/15 11:39:18 PM

DB: ServerName

COM.CONFIO.IGNITE.COMMON.JDBC.EXCEPTIONS.DATABASECONNECTIONEXCEPTION:A connection to the database could is not being Established:invalid host [cause=java.sql.sqlexception:unknown Server host name 'ServerName'.]

At Com.confio.ignite.common.jdbc.exceptions.ConnectionExceptionTranslator.translate (sourcefile:41)

At Com.confio.idc.database.datasource.MonitoredDatabaseDataSource.getConnection (sourcefile:83)

At Com.confio.idc.database.DatabaseMonitor.start (sourcefile:465)

At Com.confio.idc.database.job.DatabaseMonitorLifecycleJob.execute (sourcefile:98)

At Org.quartz.core.JobRunShell.run (jobrunshell.java:202)

At Edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker (threadpoolexecutor.java:1061)

At Edu.emory.mathcs.backport.java.util.concurrent.threadpoolexecutor$worker.run (ThreadPoolExecutor.java:575)

At Java.lang.Thread.run (Unknown Source)

caused By:java.sql.SQLException:Unknown server host name 'ServerName'.

At Net.sourceforge.jtds.jdbc.connectionjdbc2.<init> (connectionjdbc2.java:380)

At Net.sourceforge.jtds.jdbc.connectionjdbc3.<init> (connectionjdbc3.java:50)

At Net.sourceforge.jtds.jdbc.Driver.connect (driver.java:183)

At Com.mchange.v2.c3p0.DriverManagerDataSource.getConnection (drivermanagerdatasource.java:134)

At Com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection (Wrapperconnectionpooldatasource.java : 182)

At Com.mchange.v2.c3p0.impl.c3p0pooledconnectionpool$1pooledconnectionresourcepoolmanager.acquireresource ( c3p0pooledconnectionpool.java:148)

At Com.mchange.v2.resourcepool.BasicResourcePool.doAcquire (basicresourcepool.java:1014)

At com.mchange.v2.resourcepool.basicresourcepool.access$800 (basicresourcepool.java:32)

At Com.mchange.v2.resourcepool.basicresourcepool$acqui

By viewing the log information discovery, that is, the JDBC connection is not monitored by SQL Server A connection to the database could not being established:invalid Host [cause=java.sq L.sqlexception:unknown Server host name ' ServerName '.

I ping the corresponding server name on the Linux server that deploys the DPA (Ignite) to find that the ping is not working, and ping its IP address is OK. The reason is because of problems with our DNS server, and the configuration of the monitored database server is using the server name, instead of using the IP address (because the server name is easier to remember), the result when the DNS problem is, there is a JDBC connection is not monitored SQL Server database servers.

[[email protected] dpa_9_0_146] # ping ServerName

Ping:unknown Host ServerName

Workaround:

run ipconfig/registerdns on the monitored SQL Server server, and in a few minutes, you can ping the server name on the Linux server that deploys the DPA (Ignite), as shown below. Problem solving.

For

inch inch

About Ipconfig/registerdns: Indicates that you can use this parameter to troubleshoot a failed DNS name registration or to resolve a dynamic update issue between the customer and the DNS server without restarting the client computer

Dpa/ignite a database server that is not connected to the monitor due to DNS issues