[jira] Updated: (GERONIMO-3718) ResourceRef lookups are now really slow

["David Jencks (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GERONIMO-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks updated GERONIMO-3718:
-----------------------------------

    Attachment: GERONIMO-3718-1.patch

Attached patch seems to work ok for connection factories and admin objects but does not work for mail or uddi.  It should be sufficient to test lookup speed on however.

> ResourceRef lookups are now really slow
> ---------------------------------------
>
>                 Key: GERONIMO-3718
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3718
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: connector, naming
>    Affects Versions: 2.0.x, 2.1
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 2.1
>
>         Attachments: GERONIMO-3718-1.patch
>
>
> We had to turn off jndi reference lookup result caching since the tck is now testing that e.g. datasource lookups give you a different object each time.  Some of Matt's performance tests indicate that finding the MCFWrapper gbean takes an inordinate amount of time.
> One possibility is to, instead of caching the lookup result, look up the gbean when the jndi tree is set up for the javaee component.  Calling e.g. $getResource() is then as fast as the resource adapter makes it to get a new connection factory.  This needs a few changes in both naming and connector and connector-builder.

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