Re: App stuck on executeStoredProcedure() (was NPE from...)
Re: App stuck on executeStoredProcedure() (was NPE from...)
- Subject: Re: App stuck on executeStoredProcedure() (was NPE from...)
- From: David Avendasora <email@hidden>
- Date: Fri, 18 Jan 2008 09:06:30 -0500
I do have SQL Server running both locally, and on a remote server
(which has the SP). As long as I pass the machine name (or IP) as
part of the SP name to the local database, it will call it on the
remote server. I use the same setup when I test directly with a SQL
Client (Aqua Data Studio) and it works just fine.
Dave
On Jan 18, 2008, at 8:57 AM, Alexander Spohr wrote:
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@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden