Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (athena.apache.org: domain of m.v.lunteren@gmail.com
 designates 64.233.182.189 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Tequ0b1T1umMp00ATpv+0N3xtoxNyMy1cLc9lBi8j1X7uFHFjyTIdnso5MqPi0Rm0c4rIUr8XnYjfh1mWJyOQTl7OEj6CPyWRVePqbp9kziQZQJYRme6jvQHqJ+M8qyRdS9xCwP/73oVU4FqmYGhxurSqm35WUCADlPEODzhwUQ=
Message-ID: <c25576af0710161017n65ec87f4sf47d522d5883f051@mail.gmail.com>
Date: Tue, 16 Oct 2007 10:17:31 -0700
From: "Myrna van Lunteren" <m.v.lunteren@gmail.com>
To: "Derby Discussion" <derby-user@db.apache.org>
Subject: Re: java.security.AccessControlException: access denied
 (java.io.FilePermission derby.log read)
In-Reply-To: <BAY134-DAV40BF7B9F5969E1B4ECD74CB9C0@phx.gbl>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <BAY134-DAV40BF7B9F5969E1B4ECD74CB9C0@phx.gbl>

On 10/15/07, Chris <cwhankey@hotmail.com> 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