juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ShengTao Dong (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] [Commented] (JUDDI-425) The juddiv3.war can not be accessed in concurrent way
Date Wed, 27 Apr 2011 02:55:03 GMT

    [ https://issues.apache.org/jira/browse/JUDDI-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025576#comment-13025576

ShengTao Dong commented on JUDDI-425:

I'm doing that just like your mail wrote, and it works.
And maybe you can add a option to change the way if 'overwrite' the bindings, that seems a
potential requirement.
-------------Below is the content from your mail-------------------------
 so the idea is, you check if the service is there (and only create it 
if it not there), and then, in a separate transaction you save your 
bindingTemplate to this service. If the bindingKey already exist it will 
overwrite the existing binding. So you will have add a hostname or 
something to your binding key.

> The juddiv3.war can not be accessed in concurrent way
> -----------------------------------------------------
>                 Key: JUDDI-425
>                 URL: https://issues.apache.org/jira/browse/JUDDI-425
>             Project: jUDDI
>          Issue Type: Bug
>          Components: CXF 
>    Affects Versions: 3.0.1
>            Reporter: ShengTao Dong
>            Assignee: Kurt T Stam
>             Fix For: 3.1.0
> We are using juddiv3 war component to provide a soap way to access the juddi database,
but it seems it can not support concurrent access, if the client initial concurrent visit,
it will throw a exception like below:
> javax.xml.ws.soap.SOAPFaultException: org.hibernate.StaleStateException: Batch update
returned unexpected row count from update [0]; actual row count: 0; expected: 1 

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message