juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kurt T Stam (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] [Commented] (JUDDI-425) The juddiv3.war can not be accessed in concurrent way
Date Fri, 01 Apr 2011 15:25:05 GMT

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

Kurt T Stam commented on JUDDI-425:

Hi ShengTao, you would think if you follow:

1. Check if the service is there, add if it is not.
2. Then add a bindingTemplate.

Then you would not be overwriting a bindingTemplates. You are right though, if you are saving
a service it will overwrite the existing one, and it will remove any bindingTemplates if they
are there. The current behavior is how the UDDI v3 spec tells us to so it, but we could add
a config option to differentiate from the spec.

Please let me know if you are following the above strategy and *still* seeing issues. 


> 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