Home/ Questions/Q 6865011
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T02:59:12+00:00

I have a very short Java application that just opens a connection to a

  • 0

I have a very short Java application that just opens a connection to a remote MySQL database, reads some data, prints it, and exits. The most time-consuming part of the application is the database connection.

Currently I have only a single thread, and my only concern is to save the time of opening the connection.

I thought of several ways to make it faster, but it turned out they do not help:

  • Connection Pooling – doesn’t help because the pool lives only only during a single run of the application. When the application is terminated, the pool is gone, and when I re-run the application, I have to re-open all the connections in the pool.
  • mysql-proxy – connects only to the local server: mysql-proxy for a remote MySQL server
  • TCP/IP server – I thought of holding a local TCP/IP server that will keep a persistent open connection and send it to a TCP/IP client on request. However, Connection objects cannot be serialized, so I have no way to pass the Connection object from client to server.

Any other option?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Generally connection to a DB is a most time-consuming operation. If the application is to be started and stopped then there is little that you can do.

    Using connection-pooling in a web-server and call that by running your app which talks to the web server using JSON might be an option.

    • 0