Skip to end of metadata
Go to start of metadata

Cannot load driver

This occurs when attempting to connect without the JDBC driver set up normally.

Please refer to how to see the JDBC driver to be used in WebLogic.

Can not make a database connection to the given URL / Invalid Altibase URL (No suitable driver)

If there is an error in the connection URL as below, an error occurs.

  • Incorrect format, typo
  • When JDBC item is set to a name other than "Altibase" (In this case, no suitable driver may occur depending on the version.)

Could not create pool connection

This occurs when there is an error in the connection pool configuration when creating a JDBC data source. There are various cases, but typical cases are as follows.
  • When the connection target it ALTIBASE 4, the user to access in the form of "user=sys" must be entered in the property.

Client unable to establish connection / Communication link failure

In the following cases, a client unable to establish a connection error occurs. (Communication link failure may occur depending on the version.)
  • ALTIBASE server is not running
  • If the connection is impossible because the IP address or port number of the ALTIBASE server is incorrectly set in the connection URL

The following is an example of the case where the IP address of the ALTIBASE server to be integrated is and the port number is 20300, and it is incorrectly specified as a different value.

Hang phenomenon

If the user tries to connect while the ALTIBASE JDBC driver and the CM protocol version of the ALTIBASE server are different, a phenomenon such as hang may occur depending on the WebLogic version.

When this happens, most of the WebLogic server instances have to be restarted, so caution is required in advance.

For related information, refer to How to Check the ALTIBASE JDBC Driver Version.





  • No labels