[AXIS2-4437] Possible wsdl mixed-up while have load form differend clients

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.5
• Environment: axis2j 1.5 running in tomcat 6.0 on Linux (debian testing); Services are created using POJO.
• Assignee: Unassigned
• Reporter: Meindert Oldenburger
• Created: 22/Jul/09 11:00
• Updated: 27/Nov/10 13:56
• Resolved: 27/Nov/10 13:56

Description

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.

Issue Links

• is superceded by: AXIS2-4819 Race condition in WSDLDataLocator