Re: [openorb-users] COMM_FAILURE error when SID cache was exhausted

[Lars K. <lak...@t-...>]

Rahsmi,

didn't you get my response to your first email? I sent it Oct 1st....

rashmi.chidambara wrote:

> Here the jdk version is 1.5. and corba is openORB1.3.1
>
>  
>
> Ø      Why there is  java.io.EOFException occurs?
>

Client keeps a connection open but doesn't send any further requests. 
The server tries to read a few bytes, but because the client doesn't 
send anything, that read times out with an exception. This is perfectly 
normal, so it shouldn't be logged by the server. This has been fixed in 
OpenOrb 1.4.0.

> Ø      The above messages are  repeatedly thrown in the logs.
>

Sure, you have multiple clients, right. They all time out at some point.

> Ø      What are main causes we get EOFException error and is it the 
> root cause for GUI goes to hung state?
>

If the client ORB is robust, this is probably not the cause of your 
problems. If you have control over the clients, try to debug them or use 
a profiling tool like JProfiler or YourKit to detect deadlocks.

> Ø      How can we correct this error?
>
> Ø      This EOFException is leading to COMM_FAILURE .
>
>  
>

Like I said in my earlier email: I don't know your code and you seem to 
use SSL features of OpenORB I have never used personally, so I can't 
really help you. All I can say is that you really should upgrade to 
OpenOrb 1.4.0.

Regards,
Lars