- I'm using Eclipse 3.3.1 with the WTP.
- I first checked for the Derby.log file. It was present and I could delete it. This had no effect. - I next found server.policy in derbynet.jar, but I decided against trying to update that. - I finally think I solved my problem. I ended up installing multiple versions of the Derby Eclipse plug-in, but did not have all of the settings correct. I set up the driver to point to 10.1, but the build path was pointing to 10.3. I deleted all but one version of the plug-in and corrected the build path and I can start the network server now. - This may be a topic for Eclipse, but when I try and define the Derby driver in the Driver Definitions screen it only lists thru Derby 10.2. "It's interesting you're getting this error - is this in a new eclipse installation? After upgrade to the next version of derby? Or a new install of the derby plugin into an existing eclipse setup?" "Do you see a derby.log? Can you remove it?" Chris Myrna van Lunteren wrote: > > On 10/15/07, Chris <[EMAIL PROTECTED]> wrote: >> >> I am getting a >> >> "java.security.AccessControlException: access denied >> (java.io.FilePermission derby.log read)" >> >> >> >> error when trying to start the Derby Network server from Eclipse. Can >> anyone help? I saw an article about installing a looser security policy, >> but it's not clear how to do this when use the plug-in. >> >> >> >> Thanks >> >> >> >> Chris Hankey > > Hi Chris, > > It's interesting you're getting this error - is this in a new eclipse > installation? After upgrade to the next version of derby? Or a new > install of the derby plugin into an existing eclipse setup? > Some more info would be appreciated. > > I'm interested because I think I saw this in an existing eclipse > environment, but it appears no one else saw this. > Of course, one could argue that the derby.log can be removed as a > work-around, but in my environment I couldn't find a derby.log. > Do you see a derby.log? Can you remove it? > > Now, for installing a looser security mechanism - the normal way is to > specify -Dsecurity.policy=... but that's not possible with the plugin, > which starts the server for you... At least, I've not heard anyone say > how this can be done. > > I logged https://issues.apache.org/jira/browse/DERBY-2913 > for an improvement in this area. No one's picked this up. If you find > it important, you could vote for it. Or consider doing this yourself. > :-) > > As a work-around, I only have the extremely crude & ugly suggestion of > replacing the file server.policy in derbynet.jar (jar -uvf > derbynet.jar server.policy) in the derby.core plugin with a modified > one... > > Myrna > > -- View this message in context: http://www.nabble.com/java.security.AccessControlException%3A-access-denied-%28java.io.FilePermission-derby.log-read%29-tf4631643.html#a13245825 Sent from the Apache Derby Users mailing list archive at Nabble.com.
