Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Data base connection fails from Util node

SA-88034

 

Summary

Data base connection fails from Util node.

Error Messages

microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host your_host, port 1433 has failed. Error: "connect timed out. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.".
at microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:170) ~[sqljdbcjar:?]
at microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1049) ~[sqljdbcjar:?]
at microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:833) ~[sqljdbcjar:?]
at microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:716) ~[sqljdbcjar:?]
at microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:841) ~[sqljdbcjar:?]
at zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:112) ~[HikariCP-jar:?]
at zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:118) ~[HikariCP-java.jar:?]
at zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:341) ~[HikariCP-java jar:?]
at zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:193) ~[HikariCP-jav jar:?]
at zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:428) ~[HikariCP-java.jar:?]
at zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:499) ~[HikariCP-java jar:?]
at zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:112) ~[HikariCP-java jar:?]
at zaxxer.hikari.HikariDataSource.<init>(HikariDataSource.java:72) ~[HikariCP-java jar:?]
at pega.platform.datastore.connection.internal.jdbc.JdbcConnectionManager.newHikariDataSource(JdbcConnectionManager.java:188) ~[datastore.jar:?]

 

Steps to Reproduce

Unknown

Root Cause

A software use or operation error. The database schema name is not set on the table definition. This causes a request looking for a schema that does not exist to time out by default.

Resolution

Perform the following local-change: 

  1. Set the Schema definition on the table
  2. Ensure that all the nodes in the cluster are restarted to pick up the correct definition
Enter the schema name in the Schema name field.
Setting the Schema definition on the table

 

Published December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us