Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


Native JDBC driver fails/JDBC-ODBC driver succeeds using JDK 1.4.1

Native JDBC driver fails/JDBC-ODBC driver succeeds using JDK 1.4.1

Native JDBC driver fails/JDBC-ODBC driver succeeds using JDK 1.4.1


I have downloaded Mimer 8.2.4G and Mimer 9.1.3A.
I firstly installed the 8.2.4G tested it, uninstalled it
and installed the 9.1.3A version and tested the new beast.

My computer is installed with SuSE 7.3 and I am using
Sun's Java2 SDK version 1.4.1_01.

I have exactly followed the directions in the manual:


import java.sql.*;

public class Test {
   public static String DRIVER = "com.mimer.jdbc.Driver";
   public static String URL = "//localhost/backoffice";
   public static void main(Strings args[]) {
     try {
        System.out.println("Hooray, driver loaded...");
        //I came here, hooray!
     catch (Exception e) {
        System.out.println("Problem loading driver!");
     try {
        //The string of *'s is a secret password and isn't
        theConn = DriverManager.getConnection(URL,
                      "SYSADM", "**********");
        System.out.println("Hooray, we've entered the DB");
     catch (Exception e) {
        I always come here, how sad!
        System.out.println("Problem connecting to DB!");

Both Mimer versions give me exactly the same results.

This snippet always load the Mimer JDBC driver without a
hitch, but connecting to the DB always result in a
java.net.ConnectionException while trying to get the
connection to the database. It doesn't matter if the
URL refers to a existing or non-existing database I always
get the java.net.Exception: Connection Refused! I find this
meaningless. This can be everything.

When I replace the native Mimer driver to the Sun's supplied
jdbc-odbc driver, I always get my connection. When I
mistype my URL by purpose to check for an appropriate
problem message, I get a nice message: database not found
and not a meaningless connection problem. So the problem is
the mistyped URL.

In the past when I used JDK 1.3.1 from Sun, I sometimes did
not get the mentioned connection exception. This *might*
indicate that the native Mimer jdbc driver has been compiled
against JDK 1.3.1, but I may have wrong...

Is this driver explicitly compiled against JDK 1.3.1? I know
this shouldn't be a case, but I may have wrong.

With regards from Tom

RE: Native JDBC driver fails/JDBC-ODBC driver succeeds using JDK 1.4.1

If you run everything on a single computer, the ODBC driver will create a "local" connection to the database server. This type of connection uses a shared memory for efficient communication.

Since Mimer's JDBC driver is 100% Java, it can not use shared memory based connections. It will create a TCP/IP based connection to the server (in this case to "localhost"). By default, the JDBC driver will connect to port 1360.

The error message indicates that no one is listening on port 1360 on your machine.

To check what ports your machine listens on, use the command:
 $ netstat -tan

Normally the inetd server is configured to accept remote Mimer connections on port 1360 and forward them to the appropriate Mimer database server. Please check your Mimer documentation how this is done, and also check that the inetd server is configured to accept connections on port 1360.

Note that the URL in your example is incorrect. An URL specifying a Mimer JDBC driver should always begin with "jdbc:mimer:".

RE: Native JDBC driver fails/JDBC-ODBC driver succeeds using JDK 1.4.1


I'm back from my holiday and during that holiday I managed
to get the JDBC working. I didn't know anything about inetd
until you wrote me. I activated the daemon and my problem
vanished. It's was a less than 5 minute job. Thank you!

Happy 2003,

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close