Hi,
I have a question on the commit.
You added permissions for localhost and 127.0.0.1, i.e. also localhost...
I think this means this problem might then still pop up in remote
server testing, no?
I don't understand the nature of the problem...but I think this means
that a similar permission needs to be granted to either
${derbyTesting.serverhost} (which means it can't be done in this test
policy file) or, if these are permissions for the client, the test
specific policy file should also list an entry for
${derbyTesting.clienthost}. If that it's client permissions, can you
please add that?
Myrna
On 7/26/06, Andreas Korneliussen (JIRA) <[email protected]> wrote:
[ http://issues.apache.org/jira/browse/DERBY-1545?page=all ]
Andreas Korneliussen resolved DERBY-1545.
-----------------------------------------
Fix Version/s: 10.2.0.0
Resolution: Fixed
Committed revision 425732.
> derbynet/testProtocol.java fails with security manager enabled
> --------------------------------------------------------------
>
> Key: DERBY-1545
> URL: http://issues.apache.org/jira/browse/DERBY-1545
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure
> Affects Versions: 10.2.0.0
> Environment: Solaris 10 x86, Sun JVM 1.5.0
> Reporter: Knut Anders Hatlen
> Assigned To: Andreas Korneliussen
> Fix For: 10.2.0.0
>
> Attachments: DERBY-1545.diff, DERBY-1545.stat
>
>
> The tinderbox test started failing after revision 423676 which enabled
security manager for derbynet/testProtocol.java. See
http://www.multinet.no/~solberg/public/Apache/TinderBox_Derby/testlog/SunOS-5.10_i86pc-i386/423706-derbyall_diff.txt
> Exception in thread "main" java.security.AccessControlException: access
denied (java.net.SocketPermission 127.0.0.1:1527 connect,resolve)
> at
java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
> at
java.security.AccessController.checkPermission(AccessController.java:427)
> at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
> at java.lang.SecurityManager.checkConnect(SecurityManager.java:1034)
> at java.net.Socket.connect(Socket.java:501)
> at java.net.Socket.connect(Socket.java:457)
> at java.net.Socket.<init>(Socket.java:365)
> at java.net.Socket.<init>(Socket.java:178)
> at org.apache.derby.impl.drda.TestProto.getConnection(Unknown Source)
> at org.apache.derby.impl.drda.TestProto.<init>(Unknown Source)
> at
org.apache.derbyTesting.functionTests.tests.derbynet.testProtocol.executeFile(Unknown
Source)
> at
org.apache.derbyTesting.functionTests.tests.derbynet.testProtocol.main(Unknown
Source)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
