Kbase P129868: Can't connect SQL Explorer to a database on a remote machine - Ports not open on firewall
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/15/2010 |
|
Status: Verified
SYMPTOM(s):
Can't connect SQL Explorer to a database on a remote machine.
Connecting user ""<username> to URL ""<URL>... (8920)
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 Stack trace taken from the SQLExplorer.exceptions file.
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)
java.sql.SQLException
Message (throw): ### Connect stack trace. ###
Message (excp): [DataDirect][OpenEdge JDBC Driver]OE Broker fails to start SQL server.
Stack Trace:
java.sql.SQLException: [DataDirect][OpenEdge JDBC Driver]OE Broker fails to start SQL server.
at com.ddtek.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.ddtek.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.ddtek.jdbc.openedge.client.OpenEdgeClientLoginRequest.preOpenConnection(Unknown Source)
at com.ddtek.jdbc.openedge.client.OpenEdgeClientLoginRequest.preSubmitRequest(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)
Firewall exists between the database server machine and the JDBC client.
FACT(s) (Environment):
Database is being started with multiple brokers.
SQL Explorer connection on the same machine works fine.
Can ping the server from the client machine.
Ports have been opened on the firewall for the multiple database login brokers.
All Supported Operating Systems
OpenEdge 10.1x
CAUSE:
Ports for the minport and maxport ranges for the primary and secondary login brokers have not been opened on the firewall that exists between the database server and JDBC client machines.
FIX:
Start each database login broker with a minimum and maximum port range that will be used when spawning server processes for clients connecting to these brokers. The minimum and maximum port ranges are specified with the -minport and -maxport database startup parameters. Port ranges should be unique to each login broker. The firewall should then have the initial ports that the primary and secondary login brokers are started with opened for communication. The minimum and maximum port ranges being used by the multiple brokers should also be opened on the firewall for client and server communication.