[jira] Updated: (AXIS2-2641) In RPCMessageReceiver, the class level variable "method" is not threadsafe, which will lead to concurrency method call issue.

["Srinath Perera (JIRA)" <ji...@apache.org>]

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

Srinath Perera updated AXIS2-2641:
----------------------------------

    Priority: Blocker  (was: Major)

> In RPCMessageReceiver, the class level variable "method" is not threadsafe, which will lead to concurrency method call issue.
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-2641
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2641
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: adb
>    Affects Versions: 1.1.1
>         Environment: Java  1.5.0_07-b03, tomcat 5.5.16, WinXP SP2 Intel machine 
>            Reporter: Lee Eng Leong
>            Assignee: Deepal Jayasinghe
>            Priority: Blocker
>
> In org.apache.axis2.rpc.receivers.RPCMessageReceiver, the class level variable "method" is not threadsafe, which will lead to concurrency method call issue.
> I have a concurrent method call for say Class A, method1 and method2, some of the method call override the "method" variable each other. Therefore, say I have a call to method1, it actually calls method2, which cause InvocationTargetException in method.invoke() call. 
> The way to fix this is to move the method class instance variable to method level variable (inside method invokeBusinessLogic)

-- 
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org