Support Questions

Find answers, ask questions, and share your expertise

DBCP Connection Pool can't connect to "Progress-Database"

avatar

Hi everyone,

I have a weird behavior with one of my DBCP Controllers.

I'm trying to conncet to a Progress-Database on 10.254.249.24:31510. The controller is configured as shown: 

CommanderLaus_0-1700566585890.png

When I try to connect the Database (ie. with an "Execute SQL Processor" I get the following error message:

CommanderLaus_1-1700566806770.png

Now the weird thing is: The shown Port number in the error mesage is not the Port I configured in the DBCP Connection.

I thought it's a firewall thing, but when I check the IP via netcat, everything is fine:

CommanderLaus_2-1700567047040.png

I also can succesfully connect to the database with the exact same parameters and *.jar-Files as shown in the first Screenshot when I use a SQL Client like "SQuirreL".

Any Ideas?

Best regards
Maik

 

1 ACCEPTED SOLUTION

avatar

@CommanderLaus:

First things first, as I see in your netcat command, you are connecting to port 31510, whereas in your error message it seems that you are going on port 1025. Something is not right here and you need to check your configurations. Try a netscan on port 1025 as well and see if you have any connectivity. And besides netscan try using telnet as well.

Next, regarding your DBCP Connection Pool, in the property Database Driver Location(s), I highly recommend you to write the full path to the JAR File and not using "." or any other shortcuts.

View solution in original post

1 REPLY 1

avatar

@CommanderLaus:

First things first, as I see in your netcat command, you are connecting to port 31510, whereas in your error message it seems that you are going on port 1025. Something is not right here and you need to check your configurations. Try a netscan on port 1025 as well and see if you have any connectivity. And besides netscan try using telnet as well.

Next, regarding your DBCP Connection Pool, in the property Database Driver Location(s), I highly recommend you to write the full path to the JAR File and not using "." or any other shortcuts.