Hi Rick, Ouch, I didn't know we also needed that JAR for Derby to work in client/server! I usually just have them all in the classpath but now I just had derby.jar.
Anyway, it works now, thanks! Regards, Tiago On Mon, Jun 13, 2011 at 2:47 PM, Rick Hillegas <[email protected]>wrote: > On 6/12/11 11:26 AM, Tiago Espinha wrote: > >> Hi everyone, >> >> I've been trying to get Derby to automatically start the network server by >> using derby.drda.startNetworkServer=true together with an embedded >> connection but I haven't had any luck. >> >> I've made a small repro that I've put here: http://pastebin.com/E5MeSJnw >> >> And I'm trying to run it with: >> java -cp ".:derby.jar" -Dderby.drda.startNetworkServer=true TestClass >> >> But fact is, the network server never gets started. I've checked with >> netstat and lsof, and it's pretty clear. There's nothing on port 1527. >> >> Am I missing something really obvious? >> >> Thanks! >> Tiago >> > Hi Tiago, > > Your classpath looks a little odd: it contains the engine jar but not the > server jar. > > Hope this helps, > -Rick >
