Socket read time out

Question

Hi,
A java class I use is connecting to another system via socket.
This always works fine when using Java 1.3. However my database installation forces me to use Java 1.2.1 where the same code fails.
Does anybody know of a workaround to this problem?
I use Solaris.
When using Java 1.2.1 I get
Read timed out
java.io.InterruptedIOException: Read timed out
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.socketRead(Compiled Code)
at java.net.SocketInputStream.read(Compiled Code)
at java.net.SocketInputStream.read(Compiled Code)
at java.io.InputStreamReader.fill(Compiled Code)
at java.io.InputStreamReader.read(Compiled Code)
at java.io.InputStreamReader.read(Compiled Code)
at java.io.StreamTokenizer.read(Compiled Code)
at java.io.StreamTokenizer.nextToken(Compiled Code)
at com.posten.autent.AutentClient.receive(Compiled Code)
at com.posten.autent.AutentClient.connect(AutentClient.java:265)
Here is the code
// Attempt to connect to server.
try {
socket = new Socket( host, port );
in = new InputStreamReader( socket.getInputStream() ) ;
input = new StreamTokenizer( in );
output = new PrintStream( socket.getOutputStream() );
input.resetSyntax();
input.wordChars( '\u0021', '\uffff' );
input.whitespaceChars( '\u0010', '\u0020' );
input.whitespaceChars( '=', '=' );
input.quoteChar( 39 );
socket.setSoTimeout( timeout );
catch( Exception e ) { ...
The timeout is 10000 (10 seconds) which is far much more than necessary.
Regards,
Erika Biesse

Answer 1

Well now, I've found a way around the problem myself.
The java bug is Bug Id 4150737 and it was corrected in Java 1.2.2.
The reason why I must stick to java 1.2.1 is that I call the java code from stored procedures in Oracle 8.1.7, which is JDK 1.2.1 compliant only. (If you the other way around call the OracleDB from java, you can use any java version.)
Here is the WO:
Before the very first input.nextToken I send an empty command, an extra
newline.
After each 'real' command I send, I call input.nextoken until TT_EOF or TT_EOL
because the other system answers 'Error' on the empty command.
Then I send another empty command, and then input.nextoken can read the answer
of the 'real' command.
Ugly, but it works!