It is good to see this just gets better. My fellow programmer turned up the
logging on GF. Now we can see that within the same second a server.log read
was 'allowed' - had read permissions. Then this stack trace occurred saying
it had no AccessControl permissions. The immediate next log output
(milliseconds after) the server.log read permission was 'allowed'. How does
Glassfish pick and choose when a read of the server.log is allowed, is not
allowed, and then allowed?
The problem appears to be all wtih Glassfish. The real problem, if there
really is one, seems to be obfuscated by GF being stuck on whether it can
read its own server.log or not.
--
[Message sent by forum member 'rdblaha1']
View Post: http://forums.java.net/node/847299