You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Riken Shah (JIRA)" <ji...@apache.org> on 2009/06/23 23:15:10 UTC

[jira] Updated: (AXIS2-4357) Client generated by wsdl2java is not thread safe for neither single nor multiple stubs

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

Riken Shah updated AXIS2-4357:
------------------------------

    Comment: was deleted

(was: What I have come to find after a lot of stress testing, under heavy load, the Axis2 1.4 - with a stub per thread, is still not thread safe - if someone has any other way to make it, please add your comments.)

> Client generated by wsdl2java is not thread safe for neither single nor multiple stubs
> --------------------------------------------------------------------------------------
>
>                 Key: AXIS2-4357
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4357
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>            Reporter: uygar yuzsuren
>
> I'm working on a web service client generated by wsdl2java.sh tool of axis2-1.4.
> When I load the client with a multiple of threads, the server starts to throw exceptions stating that there are unexpected characters in the input. When I checked the transferred SOAP messages via tcpdump, I see that the requests of my client becoming garbage, they are not valid SOAP messages when loaded.
> I googled it on the net and found out that there might be a workaround by creating a different stub instance for each call. But the author of this comment was not sure about that.
> I changed my code to create different stubs for each call but nothing changed, the sent messages were garbage again.
> Is there are way to solve this issue?I would be pleased if you could notify.
> Thank you

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