We have one particular user reporting an issue where getRuntimeInfo() stalls while trying to read the data back from the server:"SwingWorker-pool-1-thread-3" Id=48 RUNNABLE at java.net.PlainSocketImpl.isConnectionReset(PlainSocketImpl.java:623) - locked java.lang.Object@48183ac5 at java.net.SocketInputStream.read(SocketInputStream.java:112) at org.apache.derby.impl.drda.NetworkServerControlImpl.ensureDataInBuffer(NetworkServerControlImpl.java:2853) at org.apache.derby.impl.drda.NetworkServerControlImpl.readLDString(NetworkServerControlImpl.java:2962) at org.apache.derby.impl.drda.NetworkServerControlImpl.readStringReply(NetworkServerControlImpl.java:2943) at org.apache.derby.impl.drda.NetworkServerControlImpl.runtimeInfo(NetworkServerControlImpl.java:1385) at org.apache.derby.drda.NetworkServerControl.getRuntimeInfo(NetworkServerControl.java:482) The same server is doing it fairly reproducibly (if getRuntimeInfo() is called often enough, it eventually will stall, but it might take a few tries each time) but it doesn't happen at all for anyone else. (1) What could cause this sort of thing?
I've never seen this. It certainly sounds like a bug. Can you isolate this into a standalone test program which does only this and nothing else, and reproduce it? Also, what is in your derby.log? Are there any clues there about what might be going wrong? thanks, bryan
