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 Wed, 17 Nov 2010 03:52:14 GMT

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

Kurt T Stam commented on JUDDI-425:
-----------------------------------

ShengTao, what is your expected behavior? I think if 2 transaction are trying to accomplish
the same thing at the same time, one is supposed to fail? 
We are not taking out write locks, but the entire update should be in one transaction. So
one of the updates will fail I think which is ok no? The database end up in the right state
right?

Anyway to reproduce I can for example update the serviceName concurrently? 

--Kurt

> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message