From: Fausto L. <f....@in...> - 2003-03-20 15:15:46
|
Hi, I've been tracking down that "IOException: Socket Closed " too=20 and I found a piece of code that seems suspicious to my eyes.=20 It is in the BERInputStream class that belongs to the package=20 com.k_int.codec.runtime : public int read(byte abyte()[], int i, int j) throws IOException { int k =3D in.read(abyte(),i,j); if(k=3D=3D-1)=20 throw new IOException("Connection Closed"); if(endcoding_info.size() > 0) { CodecStackInfo codecstackinfo =3D = (CodecStackInfo)encoding_info.peek(); codecstackinfo.bytes_processed +=3D k; } return k; } It *might* happen that thera are two IOException thrown, since the = instance "in" is of type BufferedInputStream whose method "read" throws a IOException = itself. Once exception is caught in upper levels, the other propagates up to the = top of=20 the listening thread stack where it is finally printed out as a stack = trace. =20 I can't verify these hipotesis since the newest release of a2j does not = contain=20 the package com.k_int.gen.AsnUseful, as the old a2j did, and cannot=20 be used together with the jzkit release 1.0. The package has been moved to the main jzjkit project, version 1.2 ,=20 which in turn i can't compile, since I don't know where to find the = package jdbm.*. Ok, I said it all, thank you for your consideration. Let me know what do you think of all this and how could I proceed .. Fausto=20 |