David Van Couvering wrote: > I think the issue of derby.system.home and two databases running in the > same VM is a symptom of a wider problem where I am not convinced we > actually work running two instances in the same VM. Derby makes use of > a lot of system properties; if you have two instances, it seems to me > that they will always be at war with each other when trying to configure > Derby. > > I would like to bet that if we built a test trying to do this sort of > thing we would quickly find that it's problematic. But not actually > having done this test myself, I can't say for sure. Has anyone tried this?
I think you are right, Derby uses system properties, well documentated that it does, and there is only a single set of system properties. Thus even with using classloading to have two Derby instances they are going to share (probably not very happily) the same configuration for certain items, like derby.log. Dan.
