ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ciaran Jessup (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ODE-701) Threading / Synchronization problem with initialization of client side Axis2Services
Date Tue, 17 Nov 2009 13:59:39 GMT

    [ https://issues.apache.org/jira/browse/ODE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778885#action_12778885

Ciaran Jessup commented on ODE-701:

I'd hazard a guess that this is a dupe of ' http://issues.apache.org/jira/browse/ODE-647 '
Does the 'workaround/horrible-kludge' described in there help you at all ?

> Threading / Synchronization problem with initialization of client side Axis2Services
> ------------------------------------------------------------------------------------
>                 Key: ODE-701
>                 URL: https://issues.apache.org/jira/browse/ODE-701
>             Project: ODE
>          Issue Type: Bug
>          Components: Axis2 Integration
>    Affects Versions: 2.0
>         Environment: System:
> 2.6.28-15-generic #52-Ubuntu SMP Wed Sep 9 10:48:52 UTC 2009 x86_64 GNU/Linux
> 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
>            Reporter: Christian Connert
> 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
> 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
> 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

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

View raw message