If you set the JVM flag, "-Djava.security.debug=access,failure", you'll get
a lot of log spam that has the root cause buried in it somewhere. If you
post the logs to the list, we can help debug it for you. Remember that if
you're running dev_appserver from the command line, you need to use
--jvm_fl
I am receiving the exact same problem.
The directory in question is indeed writable ... it creates the .policy file
okay, but doesn't seem to delete it.
If i run it inside of Eclipse it works; if i run it outside of Eclipse i get
this issue.
java.security.AccessControlException: access denied
Thanks, I will try that and get back with the results, unfortunately not
until next week when I get back to work. Obviously, I should read up on the
system variables, and java.io.File.createTempFile.
/Fredrik
2010/3/24 Toby Reyelts
> Try setting the system property, "java.io.tmpdir", to a path
Try setting the system property, "java.io.tmpdir", to a path that you are
allowed to write to.
On Wed, Mar 24, 2010 at 5:22 AM, fredrik wrote:
> I am trying to run Google App Engine 1.3.1 from Eclipse 3.5 on a lab
> computer where I don't have access to the local disk (C:), only
> network disks.
I am trying to run Google App Engine 1.3.1 from Eclipse 3.5 on a lab
computer where I don't have access to the local disk (C:), only
network disks. Already the first easiest example in the tutorial fails
when I start the development server in Eclipse, see below.
Any suggestions on either paths or
