Re: SQL Server 200 JDBC Driver Connection too slow when using IP address


leocortes@xxxxxxxxx wrote:
We have developed an application which uses Tomcat + ApacheSSL
installed on Server 1 and connects to a SQL SERVER 2000 database
installed on Server 2. They connect thru a SQL SERVER 200 JDBC
Microsoft Driver with SP3 (the latest one available). We had connected
the application to the database via the following connection string:

"jdbc:microsoft:sqlserver://192.168.1.100:1433;databaseName=clasioem",

Everything was working fine since we installed the application two
months ago but a few days ago, the application didn't work and after
recovering the application, the connection to the database was very
sloooow. So, the solution was to change the SQL SERVER 2000 server to
the same box where the application resides (both now lives on Server 1)
and kept the same connection string, obviosuly changing the IP of the
database server (Server 1 IP). The slowness problem persisted so what
we did was to change the IP of the database server for the "localhost"
text and the string now looks something like this:

"jdbc:microsoft:sqlserver://localhost:1433;databaseName=clasioem",

For our big surprise, the application ran flawlessly and the connection
to the database was very fast. We switched again the "localhost" string
for the IP of the server (Servre 1 IP), and the connection dropped
instantly.

Any answers about this, they will be fully appreciated..

Hi. It has something to do with how your network lookup is set up
on your box. It has nothing to do with the driver. The driver is simply
asking the JVM, which asks the OS, for a socket to a machine.
It is the OS's job to find the machine. The driver passes on the
machine name or IP address in the same way, unchanged and
unexamined to the same call.

Joe Weinstein at BEA Systems

.

Relevant Pages

  • Complicated Connection Problems bewteen ADP and SQL Server
    ... This database ... expertise for getting the user workstations talking to the SQL Server. ... connection would fail and the adp wouldn't be able to talk to the server. ... might be in my ADO connection string. ...
    (microsoft.public.access.adp.sqlserver)
  • Complicated Connection Problem between ADP and SQL Server
    ... This database ... expertise for getting the user workstations talking to the SQL Server. ... connection would fail and the adp wouldn't be able to talk to the server. ... might be in my ADO connection string. ...
    (microsoft.public.sqlserver.connect)
  • Re: ADO Connection Timeout
    ... so what happens when a connection failure forces one station to revert ... to a local database? ... Further, you *will* have contention issues, Jet does not support record ... to the central server, but you are willing to live with periods where it ...
    (microsoft.public.data.ado)
  • Re: ADO Connection Timeout
    ... When the first test is run, the results are stored in the central database. ... to the central server, but you are willing to live with periods where it ... i.e. a local database or even a text file. ... to function until the connection can be restored to the server. ...
    (microsoft.public.data.ado)
  • RE: WSS install locked into MSDE DB - Can not install for SQL Serv
    ... For the MASTER database ... Althought we change the Configuration Application pool several times ... interface BUT they appear to be MSDE databases and not SQL Server databases. ...
    (microsoft.public.sharepoint.windowsservices)
Loading