[
https://issues.apache.org/jira/browse/JUDDI-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933302#action_12933302
]
ShengTao Dong commented on JUDDI-425:
-------------------------------------
What I suggested is just want to let you could reproduce the exception, so just
said it in a simple way, in real environment, the parameters will not exactly
same, the normal scenario always like this:
There are three hosts, and all of those provide a same service but with
different endpoint, and then they need register their endpoint to juddi to let
client to lookup, and some time they will register in same time, so will update
the same service entry in database, what we want is all endpoints could be
registered.
The behaviour we expected is the server side can let all these register
success, and when throw these exception, the database state is not right, it's
in a non-consistence state.
I always reproduce this by using a script to start three server to register in
same time, it can be reproduce quickly.
By the way, I find that when I save a service, juddi just remove old one and
save the new one, is there a function that can let client do a update? that
means if the client save a service with some endpoints, the old endpoints of
this service would not be removed, now I just get the service from juddi, then
merge it to the new service, and then save, do I make a wrong understanding of
this?
> 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.
