On 1/17/14 7:23 AM, John I. Moore, Jr. wrote:
Java version 1.7.0_51 (latest version) causes the following error when
trying to start the network server. I can see from the issue tracker
that there is a fix to be added that should correct this problem in
the next release, but is there an easy workaround that exists now?
Details would be appreciated.
_________________________________________
John I. Moore, Jr.
C:\Java\db-derby-10.10.1.1-bin\bin>startNetworkServer.bat
Thu Jan 16 16:34:04 EST 2014 : Security manager installed using the
Basic server security policy.
Thu Jan 16 16:34:04 EST 2014 : access denied
("java.net.SocketPermission" "localhost:1527" "listen,resolve")
java.security.AccessControlException: access denied
("java.net.SocketPermission" "localhost:1527" "listen,resolve")
at
java.security.AccessControlContext.checkPermission(AccessControlContext.java:372)
at
java.security.AccessController.checkPermission(AccessController.java:559)
at
java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
at
java.lang.SecurityManager.checkListen(SecurityManager.java:1134)
at java.net.ServerSocket.bind(ServerSocket.java:375)
at java.net.ServerSocket.<init>(ServerSocket.java:237)
at
javax.net.DefaultServerSocketFactory.createServerSocket(ServerSocketFactory.java:231)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.createServerSocket(Unknown
Source)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.access$000(Unknown
Source)
at
org.apache.derby.impl.drda.NetworkServerControlImpl$1.run(Unknown Source)
at
org.apache.derby.impl.drda.NetworkServerControlImpl$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.blockingStart(Unknown
Source)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.executeWork(Unknown Source)
at org.apache.derby.drda.NetworkServerControl.main(Unknown
Source)
Hi John,
The release notes for 7u51 should describe this problem and its
solution. The solution is to give the server "listen" permission on the
port where it listens for incoming connection requests. The solution is
described on https://issues.apache.org/jira/browse/DERBY-6438
Hope this helps,
-Rick
