Java Changed security permission for DERBY network socket
Posted on Monday Jan 25, 2016 at 06:25PM in Technology
I just realized that my Apache Derby database had stopped listening on its DB port 1527.
It took a bit of tracing but soon found
that a Java runtime policy had changed to be more restrictive than
before. It now restricts java apps to create and listen to IP ports by
add the follwoing to the end of the java.policy file in the jre\lib\security dir
permission java.net.SocketPermission "localhost:1527", "listen";
Thats it. the derby network server now starts as usual.