[ODE-701] Threading / Synchronization problem with initialization of client side Axis2Services

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.0
• Fix Version/s: 2.0-beta3
• Component/s: Axis2 Integration

Environment

System:
2.6.28-15-generic #52-Ubuntu SMP Wed Sep 9 10:48:52 UTC 2009 x86_64 GNU/Linux

JAVA:
java version "1.6.0_16"
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)

Server:
apache-tomcat-6.0.20

• Assignee: Unassigned
• Reporter: Christian Connert
• Created: 17/Nov/09 08:02
• Updated: 13/Apr/10 14:19

Description

Hi,

1.) 'm using the Axis2 Integration mechanism to configure the client side AxisServices (for outgoing service calls, in my case i used it to config rampart and the corresponding policies).
Everything works as expected if I start the server (Apache Tomcat) and call the process with one client. After that it's possible to call the process with multiple concurrent clients.

2.) But if I call the process with multiple concurrent clients right after the start of the server it happens that some of the ServiceClients bypass the Axis2 Integration mechanism and the service is not correctly configured (in my case no WS-Security is applied). All further concurrent calls suffer form the same problem and some of them are using the miss-configured ServiceClients.

It happens most of the time, but sometimes it works as expected (all client calls have a consitent behavoiur), thus I conclude that this is some sort of thread synchronization at the client side AxisService initialization.

The workaround has been described in 1.

Greetings

Christian