geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jack Cai (JIRA)" <>
Subject [jira] Updated: (GERONIMO-4608) when reading ejb response
Date Thu, 06 Aug 2009 13:47:15 GMT


Jack Cai updated GERONIMO-4608:

             Priority: Critical  (was: Major)
    Affects Version/s: 2.2

After extensive testing and debugging, I believe it's a problem in JDK. The OpenEJB server
has written the result properly to the outputstream every time, but occasionally the client
failed to retrieve the complete result. The underlying socket or object streams must be doing
something wrong.

The failure actually happens quite frequently. I assume it is a common problem for all remote
EJB access. On my Windows box the failure usually happens once out of 20 times. So I regard
it as a serious reliability problem.

To work around this problem, we can add a BufferedInputStream around the SocketInputStream
in the EJB client's code. I created a JIRA against OpenEJB (see
and provide a patch there. The patch works well. I ran the monitoring function for 500 times
and didn't encounter the problem again.

> when reading ejb response 
> -----------------------------------------------
>                 Key: GERONIMO-4608
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: OpenEJB
>    Affects Versions: 2.1.4, 2.1.5, 2.2
>         Environment: Windows
>            Reporter: Jack Cai
>            Priority: Critical
> In the monitoring admin console page, define a server, enable query and then view its
statistics. Keep refreshing the server view page, and soon there will be a "server is offline"
message. Initial debugging reveals when the jsp access the server-side agent ejb, there is
a thrown during the reading of ejb response.
> An old mail discussion also mentioned this problem, see [1]. 
> This problem only occurs on Windows system.
> [1]

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message