Kathey Marsden wrote: > The way this is usually accomplished is with embedded server. Network > server is started in the same JVM as the primary instance. The primary > instance accesses with embedded connections. Other JVM's can access > with client.
Yes. But Angus' extra problem as I understand it, is that the apps will be started and stopped in an undefined order, so there's no natural server to chose. > > See: > http://db.apache.org/derby/docs/10.1/adminguide/radminembeddedserverex.html > > Also the StartNetworkServerSample demo shows how this works using the > derby.drda.startNetworkServer property. > You should be able to just add derby.drdal.startNetworkServer=true to > your derby.properties and be able to start connecting from other JVM's > right away. > http://svn.apache.org/viewvc/db/derby/code/branches/10.1/java/demo/nserverdemo/SimpleNetworkServerSample.java?view=log&pathrev=408612 > > > Kathey > > -- Bernt Marius Johnsen, Database Technology Group, Staff Engineer, Technical Lead Derby/Java DB Sun Microsystems, Trondheim, Norway
signature.asc
Description: OpenPGP digital signature
