Kbase P179475: Unable to connect database via SQL-92 after adding a secondary login Broker
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  12/22/2010 |
|
Status: Unverified
SYMPTOM(s):
Unable to connect database via SQL-92 after adding a secondary login Broker
Error: <command name | SQL Exception message>. (8933)
Error: [DataDirect][OpenEdge JDBC Driver]Error establishing socket to host and port: hostname:1025. Reason: Connection refused. (8933)
java.sql.SQLException
Message (throw): ### Connect stack trace. ###
Message (excp): [DataDirect][OpenEdge JDBC Driver]Error establishing socket to host and port: hostname:12500.
Reason: Connection refused
Stack Trace:
java.sql.SQLException: [DataDirect][OpenEdge JDBC Driver]Error establishing socket to host and port: hostname:12500. Reason: Connection refused at com.ddtek.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.ddtek.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.ddtek.jdbc.openedge.OpenEdgeImplConnection.open(Unknown Source)
at com.ddtek.jdbc.base.BaseConnection.connect(Unknown Source)
at com.ddtek.jdbc.base.BaseConnection.setupImplConnection(Unknown Source)
at com.ddtek.jdbc.base.BaseConnection.open(Unknown Source)
at com.ddtek.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:559)
at java.sql.DriverManager.getConnection(DriverManager.java:189)
at com.progress.sql.explorer.SQLConnectServer.call(SQLConnectServer.java:37)
at com.progress.common.rmiregistry.TryIt.run(TryIt.java:186)
FACT(s) (Environment):
Database is being started with multiple brokers.
The database broker has been started on the server.
ABL / 4GL connections work correctly
ABL configuration is started
All Supported Operating Systems
OpenEdge 10.x
OpenEdge SQL Category: SQL-92 Clients
No Firewall exists between the database server machine and the JDBC client.
Running ldd command against $DLC/bin/_sqlsrv2 returns no errors
CAUSE:
Using incorrect port number to connect new secondary login broker.
FIX:
Use correct port number to connect the new secondary login broker.