[
https://issues.apache.org/jira/browse/AXIS2-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933855#action_12933855
]
Chris Bontempi commented on AXIS2-4437:
---------------------------------------
We are also seeing this issue. There does not seem to be a pattern to it, and
it is infrequent (maybe every 1000th call or so?). We have C code that
requests the WSDL before it makes a service call, and on occasion that call to
xxx?wsdl returns the WSDL for the wrong service. So far it is always the same
pair of services -- always the same WSDL being requested and always the same
wrong WSDL being returned, but that could just be a quirk of how our particular
application works.
> Possible wsdl mixed-up while have load form differend clients
> -------------------------------------------------------------
>
> Key: AXIS2-4437
> URL: https://issues.apache.org/jira/browse/AXIS2-4437
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5
> Environment: axis2j 1.5 running in tomcat 6.0 on Linux (debian
> testing)
> Services are created using POJO.
> Reporter: Meindert Oldenburger
>
> Description of our test environment:
> We have two services in the webserver (tomcat/axis2j), one gives the axis
> version, and another calculates two numbers and returns the result. This
> means that both services results in two different wsdl's.
> Now we have a client that gets the wsdl (libcurl) and tries to find the
> operation expected to be in the wsdl.
> GetVersion?wsdl has operation "show_version"
> TestService?wsdl has operation "calc_numbers"
> Description of the problem:
> Now we start calling two clients at ones (parallel) xxx times. Each client
> knows about which operation belongs to a particular web services.
> Now we think that the web server is sometimes sending the wrong wsdl back to
> a particular client. Client one needs to find operation "show_version" in
> "GetVersion?wsdl", but sometimes it tries to search in wsdl
> "TestService?wsdl".
> To exclude problems on our side, we set-up another machine with the same
> webservices and call only web-services A from machine A and web-services B
> from machine B. Now we have no problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
