On 18 Sep 2007, at 03:08, Mark Thomas wrote:
I am not sure if my mail client is mangling the urls you are using but
it looks like you are using '/' characters after 'file:'
Must be your e-mail client... I've tried
jar and file (no slash after file:)
Sam Halliday wrote:
and confirmed that this is where the jar file is... but tomcat is still
refusing to give the permissions on a per-jar basis. Maybe this is a bug
with the Ubuntu release?
This is all standard JVM stuff. The only bit Tomcat adds is the odd
PrivilegedAction but that won't stop
Hello all,
I have a Servlet running on tomcat-5.5.20, Ubuntu Feisty Fawn, which
is accessing some hardware through a shell script. The following
provides adequate permissions for everything to work
grant {
permission java.io.FilePermission /bin/sh, execute;
permission
Sam Halliday wrote:
Does anyone have any ideas?
Start Tomcat with -Djava.security.debug=access,failure
That should tell you what permissions you are missing.
Mark
-
To start a new topic, e-mail: users@tomcat.apache.org
To
Hello Mark,
That doesn't give me any additional input... I already know which
permissions I need, I just want to restrict them to the one Servlet.
If you really want to know the exception, I'll print it here but I
don't think it's relevant...
Caused by:
Sam Halliday wrote:
Hello Mark,
That doesn't give me any additional input... I already know which
permissions I need, I just want to restrict them to the one Servlet.
The debug output should tell you what coedbase is requesting what
permission. I can't tell where, but you are missing at
Hmm, where should I expect to see the extra debugging output. It
isn't in any of the log files.
The permissions are perfectly fine... it is in the assignation of the
permissions to the correct jar file/servlet that things are getting
messed up. Will the debugging output really point to
Sam Halliday wrote:
Hmm, where should I expect to see the extra debugging output. It isn't
in any of the log files.
Should be on standard out.
The permissions are perfectly fine... it is in the assignation of the
permissions to the correct jar file/servlet that things are getting
messed up.
On 17 Sep 2007, at 18:16, Mark Thomas wrote:
Sam Halliday wrote:
Hmm, where should I expect to see the extra debugging output. It
isn't
in any of the log files.
Should be on standard out.
Aah! That's why I wasn't seeing it. There is a pretty bad bug in
Ubuntu which puts the output into
Hmm.
The output shows that your jar isn't getting the permissions. You are
right that the codebase is the problem.
I am not sure if my mail client is mangling the urls you are using but
it looks like you are using '/' characters after 'file:'
Try without these as per the entries in the TC6
10 matches
Mail list logo
