Error messages are lost

[NormD]

I have an interesting situation that I hope you can help me with. I have two
versions of one application. One connects to Oracle database running on a sun
box directly. The other connects to the database via webservices. If let's
say I queried for a non existing table, I've got a "table not exists"
exception back in the application that connects to the database directly and
"Unable to read data from the transport connection" exception in the
application that connects to the database via webservices. Both applications
have exactly the same code for querying the database.
I've put in a trace in the network and I can see that "table not exists"
exception is dispatched from database. But I don't know what happens after
that so I get the "Unable to read data from the transport connection"
exception.

[[MSFT]]

The exception "Unable to read data from the transport connection" may come
from the web service or proxy on clients. The web service pass your query
to database and get "table not exists" back. It may send its own exception
to clients.

Luke

[[MSFT]]

The exception "Unable to read data from the transport connection" may come
from the web service or proxy on clients. The web service pass your query
to database and get "table not exists" back. It may send its own exception
to clients.

Luke

[NormD]

I have a try catch block in the web services and I'm passing the exceptions
to the client without changing them (I create a soap exception embedding the
original exception). I'm thinking somehow the message is either not received
even though it's dispatched or the message is not interpreted correctly.

"[MSFT]" wrote:

The exception "Unable to read data from the transport connection" may come
from the web service or proxy on clients. The web service pass your query
to database and get "table not exists" back. It may send its own exception
to clients

[NormD]

I have a try catch block in the web services and I'm passing the exceptions
to the client without changing them (I create a soap exception embedding the
original exception). I'm thinking somehow the message is either not received
even though it's dispatched or the message is not interpreted correctly.

"[MSFT]" wrote:

The exception "Unable to read data from the transport connection" may come
from the web service or proxy on clients. The web service pass your query
to database and get "table not exists" back. It may send its own exception
to clients

[[MSFT]]

Have you traced the communication between web service and client? you may
find the raw soap message in the trace and check if the soap exception has
been passed to client. Also, even the client received the soap exception,
it may generate its own exceptiom message based on the soap exception.

Luke