Error establishing socket. Unknown host: vmqcrnd44

  • Questions
  • Error establishing socket. Unknown host: vmqcrnd44
Question ID: 107743
1
0

We’re getting a really off error as of recent, a couple of nights ago our instance of ALM v11 just went toes up and started presenting the error below. All ic an find from HP is that it’s a "known issue" and not one that they support. Has anyone else experienced this or know how to resolve it? Nothings changed on our end.

**Server on ‘XYZ’ has entered an unstable state, please contact your site administrator.**

status=MUTED, label=QC server is muted due to unrecoverable error,
StackTrace=
java.sql.SQLNonTransientConnectionException: [Mercury][SQLServer JDBC Driver]Error establishing socket. Unknown host: vmqcrnd44
at com.mercury.jdbc.sqlserverbase.dda4.b(Unknown Source)
at com.mercury.jdbc.sqlserverbase.dda4.a(Unknown Source)
at com.mercury.jdbc.sqlserverbase.dda3.b(Unknown Source)
at com.mercury.jdbc.sqlserverbase.dda3.a(Unknown Source)
at com.mercury.jdbc.sqlserver.tds.ddc.(Unknown Source)
at com.mercury.jdbc.sqlserver.SQLServerImplConnection.f(Unknown Source)
at com.mercury.jdbc.sqlserverbase.BaseConnection.a(Unknown Source)
at com.mercury.jdbc.sqlserverbase.BaseConnection.i(Unknown Source)
at com.mercury.jdbc.sqlserverbase.BaseConnection.a(Unknown Source)
at com.mercury.jdbc.sqlserverbase.BaseConnection.a(Unknown Source)
at com.mercury.jdbc.sqlserverbase.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:582)
at java.sql.DriverManager.getConnection(DriverManager.java:154)
at com.mercury.optane.core.db.CTdDriverManager.getConnection(CTdDriverManager.java:81)
wrapped in com.mercury.optane.core.CTdException:
at com.mercury.optane.core.db.CTdDriverManager.getConnection(CTdDriverManager.java:88)
at com.mercury.optane.core.db.CConnectionPool.newConnection(CConnectionPool.java:822)
at com.mercury.optane.core.db.CConnectionPool.tryToGetConnection(CConnectionPool.java:612)
at com.mercury.optane.core.db.CConnectionPool.getConnection(CConnectionPool.java:379)
at com.mercury.optane.core.db.CConnectionManager.getNotTransactedConnection(CConnectionManager.java:239)
at com.mercury.optane.core.db.CConnectionManager.getConnection(CConnectionManager.java:212)
at com.mercury.optane.core.db.CAbsStatement.(CAbsStatement.java:91)
at com.mercury.optane.core.db.CTdPreparedStatement.(CTdPreparedStatement.java:98)
at com.mercury.optane.core.db.CTdPreparedStatement.(CTdPreparedStatement.java:94)
at com.mercury.optane.core.db.spring.JDBCTemplate$AbstractPreparedStatementCreator.create(JDBCTemplate.java:1231)
at com.mercury.optane.core.db.spring.JDBCTemplate.executeQuery(JDBCTemplate.java:1050)
at com.mercury.optane.core.db.spring.JDBCTemplateWithRetry.access$101(JDBCTemplateWithRetry.java:14)
at com.mercury.optane.core.db.spring.JDBCTemplateWithRetry$2.exec(JDBCTemplateWithRetry.java:50)
at com.mercury.optane.core.db.spring.JDBCTemplateWithRetry.executeWithRetry(JDBCTemplateWithRetry.java:91)
at com.mercury.optane.core.db.spring.JDBCTemplateWithRetry.executeQuery(JDBCTemplateWithRetry.java:46)
at com.mercury.optane.core.db.spring.JDBCTemplate.executeQuery(JDBCTemplate.java:907)
at com.mercury.optane.core.db.spring.JDBCTemplate.executeQuery(JDBCTemplate.java:892)
at com.mercury.optane.core.db.spring.JDBCTemplate.executeQuery(JDBCTemplate.java:800)
at com.mercury.optane.core.directory.CAbsDirectory.setCacheOverrides(CAbsDirectory.java:223)
at com.mercury.optane.core.directory.CAbsDirectory.init(CAbsDirectory.java:175)
at com.mercury.td.init.InitServlet.init(InitServlet.java:125)
at javax.servlet.GenericServlet.init(GenericServlet.java:212)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1048)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:950)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4122)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4421)
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310)
at org.jboss.web.tomcat.service.deployer

Marked as spam
Posted by (Questions: 1, Answers: 6)
Asked on July 21, 2017 5:07 pm
5 views
Answers
1
Private answer

This can be caused by alot of issues, a few things I would try:

Reboot the ALM server (make sure the db server is running before restarting the ALM server)

Make sure that you can connect to the database instance using some kind of database explorer tool (I.E. SQL server management studio) Try this FROM the alm server machine it could even be a network issue. I would check to make sure that your network guys did not start blocking db ports or something to that affect.

Marked as spam
Posted by (Questions: 0, Answers: 327)
Answered on July 21, 2017 5:53 pm
Odd, my initial response isn't showing. Anyway, what I was going to post was that we are running an Oracle database and those connections are fine, no issues there, thank you for the suggestion! I was able to find some info from HP regarding this error and basically it's a ''You're on your own'' scenario from them.
( at July 24, 2017 4:18 pm)
0
Private answer

Here's a thought, if the system (physical server) is configured to not allow interactive services, could that affect JBoss and it's deployment of certain apps like the CIA ones?

Marked as spam
Posted by (Questions: 1, Answers: 6)
Answered on July 21, 2017 9:59 pm