db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steffen Winkler" <steffen.wink...@danprodukte.de>
Subject AW: AW: somtimes no connect
Date Wed, 06 Dec 2006 14:28:25 GMT
Thank you Stan.

We come closer to the solution:

Application, database and Network server is installed on the same computer
Url contains computername (e.g. danxpu73).

If the network-cable is plugged off, the connection closes with following
 -4499: A communications error has been detected: Connection reset by peer:
socket write error.

Restart the application and ping leads to the error:
DRDA_NoIO.S:Es konnte keine Verbindung zu Derby Network Server auf dem Host
danxpu73, Port 1527, hergestellt werden.
That means "no connection possible".

Shutdown the server leads to the error:
-4499 java.net.NoRouteToHostException : Error connecting to server danxpu73
on port 1527 with message No route to host: connect.
Restarting the Network-Sever solves this problem.

If the network-cable is plugged off and re-plugged in, then new connection
of the application is possible.

Similar problems occur, when I use IP-Number instead of computername.

No problem occurs, when I use "localhost".

-----Urspr√ľngliche Nachricht-----
Von: Stanley Bradbury [mailto:Stan.Bradbury@gmail.com]
Gesendet: Dienstag, 5. Dezember 2006 19:30
An: Derby Discussion
Betreff: Re: AW: somtimes no connect

Steffen Winkler wrote:
> Thank you for reply.
>> Check to be sure that the application does not shutdown the Network
> when it shutsdown.
> If the network server was shutdown, i should see it in the log. But the
> shows that the network server was shut down after the ConnectException.
> Are there any other reasons why connection was not possible?
==  SNIP ===

I've seen instances where the Network server has been terminated without
any messages being sent so I recommend testing availability using
'NetworkServerControl sysinfo' or 'ping'.  If these commands indicate
that the Network Server is running and the application still cannot
connect I would check that the correct hostname and port are being
supplied on the connection URL.  To remove any possible problems
stemming from name resolution perform a test using the IP address of the
server machine rather than 'localhost' or the hostname.

I hope these guesses help.  You might try to create a small test case
that could be used to demonstrate the problem.  Knowing the specifics of
the configurations of the client, server and seeing the code that
manages the Server and the establishes the client connection would help
in looking into this further and, if this is a bug, filing a Jira bug
entry for the problem.

View raw message