| Key: |
SES-513
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Jan Stette
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
Sesame
Created: 11/Jan/08 05:24 PM
Updated: 20/Mar/08 08:06 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
2.0-rc2
|
| Fix Version/s: |
2.0.1
|
|
I'm seeing incorrect handling of transactions in an application when using a RemoteRepositoryConnection to a remote repository.
What happens is that when the client calls clear() then add(...) in a single transaction, only the clear() seems to take effect. I.e. the statement added don't appear. So this code doesn't work correctly:
connection.clear(context);
connection.add(inputStream, ns, format, context);
connection.commit();
...whereas this does work:
connection.clear(context);
connection.commit();
connection.add(inputStream, ns, format, context);
connection.commit();
This sounds very similar to a problem we had before, which turned out to be a bug in the store used. In this case, we see the problem using either MemoryStore or NativeStore. I have tried to reproduce it in a unit test using a local Repository. However, I could not reproduce the problem this way, so I suspect the problem is with the remote (HTTP) repository connection or some part of the remote access chain.
|
|
RDF documents in the form of files, URLs, stream or readers were sent directly to the server by the HTTPRepository, even if auto-commit was disabled. This data is now parsed locally and is made part of the transaction.
|
|
Incorrect transaction handling when using HTTPRepository