Nope. This is a Java Client project. No browser involved.
I think that message is simply the server connections to the
database timing out due to inactivity. I can have several connections
open at any one time and they automatically close if not used.
Maybe I'm wrong?
Dave
On Jan 18, 2008, at 9:02 AM, Alexander Spohr wrote:
Um.. forget it.
I am wrong, that’s your Browser timing out, right?
Am 18.01.2008 um 14:57 schrieb Alexander Spohr:
Dave,
I have no idea how you send an SP to an MS-database. But the error
looks like your app tries to talk to your local machine
(10.0.1.5), not to your database (10.10.10.8). And I bet your
machine simply does not answer on that port :)
atze
Am 18.01.2008 um 14:35 schrieb David Avendasora:
[2008-01-18 06:32:44 EST] <WorkerThread0> <WOWorkerThread id=0
socket=Socket[addr=/10.0.1.5,port=59366,localport=59363]> Timed-
out reading from socket (exception ignored):
java.net.SocketTimeoutException: Read timed out; dropping connection
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
