[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1930) Timeouts for RMI-Calls to EJBs

[Bernd Köcke (JIRA)]

    [ https://jira.jboss.org/jira/browse/EJBTHREE-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12490338#action_12490338 ] 

Bernd Köcke commented on EJBTHREE-1930:
---------------------------------------

I had some problems with the classcaching feature of the pooled invoker for non clustered beans on JBossAS 4.0.2. I solved it by switching off the cache. But this doesn't affect the EJB 3 code.

But I read an article about EJB 3.1 and found the feature of making asynchronous calls to EJBs and that it will find its way into the standard.TIF is a little bit more comfortable, because there are no changes to the beans interface and the client need not call a get method on a Future. But the asynch annotation is part of the EJB 3.1 standard and I think that this compansates the code changes in the beans and clients code. So I think that TIF can be replaced by this asynch calling feature of EJB 3.1.

> Timeouts for RMI-Calls to EJBs
> ------------------------------
>
>                 Key: EJBTHREE-1930
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1930
>             Project: EJB 3.0
>          Issue Type: Feature Request
>          Components: ejb3
>         Environment: Linux, SUN-Java5-20, JBoss 4.0.2, JBoss 4.2.3.GA
>            Reporter: Bernd Köcke
>         Attachments: tif-1.1.zip
>
>
> I would like to introduce client defined timeouts for RMI-Calls to EJBs. We have EJBs which are called from webfrontends and background processes. The Frontends have strong timing demands, e.g they only want to wait 50ms to get an answer but they accept to goon without it. This can be solved by application desing, but we have running applications which should not change. By looking into the code I found that it should be enough to set the SO-Timeout on the clients socket and the goal was to do this without changes in the clients code and the EJBs. So I build a small framework that the client only needs a jar- and a property-file to set timeouts for the RMI-Calls. I build this for EJB 2.1 on JBossAS 4.0.2 and EJB 2.1 + 3 for 4.2.3.GA. I talked to Carlo and he said that the latter could be interesting. It is installed on the server side by additonal JARs and configuration, no patches to existing JBoss code is needed.
> The attachment is a complete Maven Eclipse project with sources, classes and artifacts. The framework is called "Timed Invoker Framework" (TIF). I added JBoss deployment descriptor fragments to the ZIP and a readme PDF. The PDF is a copy of my internal Wiki page which describes usage and installation of TIF and the source contains JavaDoc.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira