[jbossws-issues] [JBoss JIRA] Commented: (JBWS-1310) OperationMetaData.getJavaMethod throws WSException: Ambiguous javaMethod

[Jason T. Greene (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBWS-1310?page=comments#action_12348763 ] 
            
Jason T. Greene commented on JBWS-1310:
---------------------------------------

You are right, getJavaMethod is lazy loading, which is wrong. 

> OperationMetaData.getJavaMethod throws WSException: Ambiguous javaMethod
> ------------------------------------------------------------------------
>
>                 Key: JBWS-1310
>                 URL: http://jira.jboss.com/jira/browse/JBWS-1310
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jaxws
>    Affects Versions: jbossws-1.0.3
>         Environment: Windows XP dual core processor
>            Reporter: Ray Tomlinson
>             Fix For: jbossws-1.0.4
>
>
> Running two copies of a test client beating up on a few web-service methods produces "Ambiguous javaMethod: <method>" from org.jboss.ws.metadata.OperationMetaData(getJavaMethod) (line 203). There is no potential ambiguity since all methods have quite distinctive signatures and the problem is sporadic.
> I believe this a lack of synchronization between multiple threads simultaneously trying to resolve the javaMethod field. Both see that javaMethod has not yet been set and the second to finish finds the javaMethod field has already been set by the first and mis-interprets this as an ambiguous method situation. Running a dual core processor exacerbates the problem.
> Cannot use jboss with this bug.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira