JDBC Abruptly Stopped Working

Does anyone have working JDBC code (that is "still" working)?

I had several working installs on both Mac and Windows Server, but after not using them for a little while, we're now getting "Connection Refused" errors.

[FileMaker][FileMaker JDBC] Connection refused. Check that the host address and port are correct and that xDBC sharing is enabled on the host.

(Port 2399 is handled by the driver, host address has not changed.)

Same error regardless of whether we're using:

  1. FileMaker app in FileMaker Server (has been working for years).
  2. Several Standalone FileMaker Apps (app is "open" and JDBC is enabled for all).
  3. Third-party Database utility using the JDBC library to access either local FMP apps (open) or FMS, also open apps.

I've tried both the 2023 version of the FMP JDBC driver (the one that has been working lately) and the newest Feb, 2024 version, but that made no difference...same errors.

The common denominator in all the errors is that now it is throwing "Connection Refused" errors.

Here's a code snippet that used to work for testing, just fine:

  Class.forName("com.filemaker.jdbc.Driver");
            Connection connection = DriverManager.getConnection(
                    "jdbc:filemaker://localhost/testFMP",
                    "Admin",
                    "admin");
            System.out.println("Connection successful!");
            connection.close();

Since obviously something has changed, but not the code, drivers, etc., I'm a bit baffled at the moment.

Suggestions welcome!

Thanks

Resolutions:

  1. Local Mac. Claris broke the FMJDBC driver under Mac OS 15 and FMP 19 requiring an "upgrade". Since there was really nothing of an improvement to me between FMP versions 19 and 21, I just forgot about using JDBC with Mac and FileMaker. When testing FMP version 21, the latest JDBC driver was required (From February, 2024).

  2. Windows Server. JDBC Problem was AWS firewall configuration issue where server administrator restricted port 2399 for global access by mistake.

Hope this info may help others.

3 Likes