Bryan Pendleton wrote: > Kathey Marsden (JIRA) wrote: > > If I understand this correctly, if we go with 1) would the workaround > > just be for the user to break up their batches into a few batches each > > with less than 64K statements? > > Yes, exactly so. > > > If so, I think 1) is fine for now. > > Great! That's the path I'll pursue. > > > We have bigger fish to fry with Network Server. > > Can you be more specific? Are there a few particular bugs you want > to point me at? Or is it more a general feeling...
Both. Here are some bugs that I think are important in client and server. I will send a mail later on my general concerns and the bigger issues. Wrong results DERBY-889 getTimestamp on a TIME column will print the date 1900-01-01 instead of the current date. Which leads into encoding issues. These showed up on zOS but are generic problems with network server and client and could show up on other platforms. I was about to work on these but had to attend to some immediate xa issues. DERBY-951 DERBY-583 DERBY-900 DERBY-901 DERBY-902 Hang on NetworkServer Control commands: In the hard to reproduce but probably Bryan can whip up a repro category: we have had reports of occasional hangs on NetworkServerControl shutdown and other commands. DERBY-589 may be this but more consistent on zOS. I have a feeling maybe the stream is not getting flushed properly for the NetworkServer commands. Exception handling issues for Network Server and nightly tests Exception handling is one of my general concerns but here is a related bug. DERBY-803 is the result of an intentional shutdown causing the error on cleanup of the connections going to the console. Really in this case the error closing the connection is expected because the db was intentionally shutdown. DERBY-902 touches this category as well. In the sticky category, could you look at comments for DERBY-51? Is there possibly a problem with network server shutting down Derby? David reports the code is commented out. We really couldn't just turn this back on. Maybe some sort of controlled shutdown for embedded like we discussed in an earlier thread would be appropriate.
