
| Key: |
COR-738
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Critical
|
| Assignee: |
Unassigned
|
| Reporter: |
Andy 2003
|
| Votes: |
0
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Time Tracking:
|
|
Original Estimate:
|
Not Specified
|
|
|
Remaining Estimate:
|
0h
|
|
|
Time Spent:
|
3h
|
|
|
|
| Order: |
3
|
| Original IDS Estimate: |
2
|
| Resolution Date: |
22/Aug/07 07:47 PM
|
| First Response Date: |
13/Aug/07 02:57 AM
|
| Labels: |
|
| Participants: |
Andrew Zhang and Andy 2003
|
| Number of Attachments: |
4
|
| Number of Comments: |
6
|
as described in http://developer.db4o.com/forums/thread/39989.aspx
(when switching the database file in c/s mode and using a blob read or write operation, the BlobProcessor closes the current transaction (Is this how it should be???), but db4o continues to use this open transaction. So closing the ObjectContainer results in a NullPointerException, because the Server couldn't find the correct transaction to close.)
|
|
Description
|
as described in http://developer.db4o.com/forums/thread/39989.aspx
(when switching the database file in c/s mode and using a blob read or write operation, the BlobProcessor closes the current transaction (Is this how it should be???), but db4o continues to use this open transaction. So closing the ObjectContainer results in a NullPointerException, because the Server couldn't find the correct transaction to close.) |
Show » |
|
(there are parts of patch [1] included in this patch)
[1] http://tracker.db4o.com/browse/COR-719