Hi Mark,

On Tue, 27 Nov 2007 18:21:20 +0000 Mark Thomas wrote:
> Can you run the faulty instance with:
> -Djava.security.debug=access,failure
> and report the failure message.

I thought on this, but the exception looks pretty self explanatory.

I'll try it anyway, in case anything new comes up. The machine is used in 
production so this will be applied on the next tomcat restart(might be 
several days from now). 

> If you can reproduce this at will then
> -Djava.security.debug=all
> would be better but it will generate lots of log data
>
> I have also seen problems with policy files where I have had to use
> ${file.separator} rather than / but that was with java.io.FilePermission on
> Windows rather than in the codebase.


Cheers
--
Delian

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to