🚀 go-pugleaf

"Alexei Akimov" <a_p_akimov@mtu-net.ru> wrote in message
news:3d9c31f5@newsgroups.borland.com...
> Here are the extracts of  my code:

<snip>

The freezing shouldn't have any bearing on the stream being open; in fact
the only place, IMO, you should be calling close on the streams at either
end is in a finally block - there's no reason to need to close it
mid-transaction, AFAICS.

Is the freeze occurring when you attempt to create the ObjectOutputStream or
when you try and flush the writer?

Have you verified that the Response class serializes ok?

What are you doing with respect to threading on the server?

Why aren't you producing stack traces of exceptions on the server side?

Finally:
      if (theResponse.Result != Response.RESULT_OK)
         throw new Exception(theResponse.ErrorMessage);
     }
     catch (Exception e){
       Result = false;
       System.err.println(e.getLocalizedMessage());
     }
     return Result;
   }

is basically using an exception for flow control, which is very naughty (and
expensive) , either throw the exception back out of the method for higher
level handling or just return false.

Owen