db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Pendleton <bpendle...@amberpoint.com>
Subject Re: DRDA_InvalidReplyTooShort.S:Invalid reply from network server: Insufficient data.
Date Sat, 01 Apr 2006 19:27:04 GMT
> When stress testing a mechanism to simultaneously start the Derby 
> network server from different applications at the same time, I sometimes 
> get the following exception:
> DRDA_InvalidReplyTooShort.S:Invalid reply from network server: 
> Insufficient data.
> Is this possibly a bug?

I'm not sure I understand the first paragraph above very well, but I can't
think of any reason you should be getting the ReplyTooShort response other
than a bug, so I would say yes, this sounds like a bug to me.

When this happens, can you look on the server side, and find your derby.log,
and look there? Are there interesting messages there?

Also, can you capture the actual console (System.out and System.err) from the
server side, and see if there are any interesting messages there?

I suspect that the problem is happening on the server side, and the stack
trace and error message on the client side aren't going to be all that helpful.

If you are trying to simultaneously start multiple instances of the network
server at the same time, aren't you going to get "port number in use" conflicts,
and the like?

Perhaps, in addition to letting us know what you can learn from crawling around
in your server-side logs, you could also explain a bit more about what behavior
you are expecting to see from your server-starting mechanism that you are testing.



View raw message