History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: COR-738
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Unassigned
Reporter: Andy 2003
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
db4o Core

NullPointerException while using Blobs in Client/Server mode

Created: 24/Jul/07 08:23 PM   Updated: 22/Aug/07 07:47 PM
Component/s: Client/Server
Affects Version/s: None
Fix Version/s: Denmark - v6.3

Time Tracking:
Original Estimate: Not Specified
Remaining Estimate: 0h
Time Spent - 3h
Time Spent: 3h
Time Spent - 3h

File Attachments: 1. Text File COR-719_and_COR-738.patch (16 kb)
2. Text File socket.patch (5 kb)
3. Text File socket.test_case.patch (2 kb)
4. Text File socket_new.patch (6 kb)


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


 Description  « Hide
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.)

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Andy 2003 - 24/Jul/07 08:26 PM
This patch adds a new Message for just closing the socket without terminating the current transaction.

(there are parts of patch [1] included in this patch)

[1] http://tracker.db4o.com/browse/COR-719

Andy 2003 - 12/Aug/07 04:21 PM
Here is the TestCase.
The exception is thrown when the server closes, but it's only catched and printed to the console, so I couldn't assert it.

Andy 2003 - 12/Aug/07 04:22 PM
Here is the patch created from the current source.

Andrew Zhang - 13/Aug/07 02:57 AM
Hi Andreas,

Thanks for updating the patch. The reproducible test case looks very good. But when I tried to apply the new patch, I met some problems:
1. The method getWorkingPath() is undefined for i_config
2. Class MDoesFileExists is not included in the patch.

Would you please verify? Thanks a lot!

Andy 2003 - 13/Aug/07 09:04 AM
Hi Andrew,

you have to remove this lines as they belong to a second patch I supplied. Or you can applay both patches at the same time.
I attached a new file with both patches included (the second is cor-719)

- Andreas

Andrew Zhang - 13/Aug/07 02:43 PM
Hi Andreas,

Thanks a lot! The patch has been committed with some modifications. The changes include:

1. removed the methods in ExtObjectContainer.
2. removed two new message classes which are file path related.

Because we want to keep the external interface (especially ExtObjectContainer) and codebase stable and lean.
Would you please verify? Thanks!