>>>>> "DWVC" == David W Van Couvering <[EMAIL PROTECTED]> writes:
DWVC> Hi, all. I've been running tests with the new i18n framework, which
DWVC> included having all public methods throw SQLException instead of
DWVC> org.apache.derby.client.am.SqlException.
DWVC> For reasons that are mystifying me, in tests that prepare a statement
DWVC> which deal with stored procedures/functions (either to create or to
DWVC> drop), the client hangs waiting for a description of the input
DWVC> parameters. Here's the stack trace. It's the same for
DWVC> derbynet/callable.java and DerbyJunitTest.dropSchemaObject().
Meanwhile
DWVC> the network server is completely idle.
DWVC> These same tests pass for JCC and for the trunk. Can anyone give me
any
DWVC> tips how I might go about tracking this down? I am mystified how I
DWVC> could have caused this problem simply by changing what exception is
DWVC> thrown. I'm not expecting you to figure this out, but if you have
any
DWVC> "did you check this" kind of hints it would be very much appreciated.
I have seen the same behavior when I tried to modify the parsing of
messages to the NetworkServer. I accidently caused the NetworkServer
to expect more data than the client was sending. The client waited for
the reply, while the server waited for more data from the client.
Don't know exactly how your change could trigger this type of behavior
though...
--
dt
