qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Godfrey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-4288) PID and Platform info should be cached and reused for subsequent connections
Date Mon, 17 Sep 2012 13:48:07 GMT

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

Rob Godfrey updated QPID-4288:
------------------------------

    Assignee: Rajith Attapattu
    
> PID and Platform info should be cached and reused for subsequent connections
> ----------------------------------------------------------------------------
>
>                 Key: QPID-4288
>                 URL: https://issues.apache.org/jira/browse/QPID-4288
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Client
>    Affects Versions: 0.18
>            Reporter: Rajith Attapattu
>            Assignee: Rajith Attapattu
>             Fix For: 0.19
>
>
> While investigating the reasons for the java client occasionally not being able to negotiate
the connection within a reasonable time, we noticed that there is often a time gap between
receiving connection-start and the client responding with connection-start-ok.
> Upon further investigation it appears that getPid() and getPlatformInfo() is a contributory
factor. 
> These values are per JVM and there is no reason to fetch them for every connection. Instead
we should fetch them in a static block and then return the cached value when the getters are
called.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message