[jbossws-issues] [JBoss JIRA] Commented: (JBWS-2324) jbossws client Port isn't thread safe

Sefai Tando?an (JIRA) jira-events at lists.jboss.org
Mon Aug 17 07:13:27 EDT 2009


    [ https://jira.jboss.org/jira/browse/JBWS-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12481110#action_12481110 ] 

Sefai Tando?an commented on JBWS-2324:
--------------------------------------

Why postpone this issue constantly? It is a major performance problem?

>  jbossws client Port isn't thread safe
> --------------------------------------
>
>                 Key: JBWS-2324
>                 URL: https://jira.jboss.org/jira/browse/JBWS-2324
>             Project: JBoss Web Services
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-native
>    Affects Versions:  jbossws-native-3.0.3
>            Reporter: Stefano Maestri
>            Assignee: Darran Lofthouse
>             Fix For: jbossws-native-3.2.1
>
>
> While Service is 3ad safe, Port isn't. I'm referring to client part.
> It's a problem to achieve better performance in a concurrent environments like Wise/ESB.
> While it's still possible to invoke Service.getPort() for each call it still not achieve good performance since getPort isn't so fast doing a lot of things under the hood.
> AFAIK referential implementation have Port 3ad safe and not Service, that would be good for our purpose, since Service.getPort would be good to be invoked in a 3adLocal manner and then Ports cached and reused.

-- 
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

        


More information about the jbossws-issues mailing list