On Tue, 08 Jan 2008 21:10:31 + Mark Thomas wrote:
> All I can suggest is start Tomcat with remote debugging enabled and when
> you see the error, connect, debug you way through a request and see if you
> can see what the security settings are and try and confirm that they match
> the policy fil
Delian Krustev wrote:
On Mon, 07 Jan 2008 20:59:28 + Mark Thomas wrote:
Not right now. Could you provide the full debug stack trace again please.
We should at least see a different problem now the code has been changed.
Here it goes:
I'm stumped. This stack trace indicates an issue with
On Mon, 07 Jan 2008 20:59:28 + Mark Thomas wrote:
> Not right now. Could you provide the full debug stack trace again please.
> We should at least see a different problem now the code has been changed.
Here it goes:
SEVERE: Servlet.service() for servlet jsp threw exception
java.security.Acces
Delian Krustev wrote:
On Thu, 27 Dec 2007 16:04:29 +0200 Delian Krustev wrote:
I'll monitor the container for the next several restarts.
The problem appeared once again on the next tomcat restart.
Any other ideas ?
Not right now. Could you provide the full debug stack trace again please.
W
On Thu, 27 Dec 2007 16:04:29 +0200 Delian Krustev wrote:
> I'll monitor the container for the next several restarts.
The problem appeared once again on the next tomcat restart.
Any other ideas ?
-
To start a new topic, e-mail: u
On Thu, 27 Dec 2007 11:12:28 + Mark Thomas wrote:
> I have uploaded it here.
> http://people.apache.org/~markt/dev/remove-sm-opt.patch
Thanks
> OK. Let us know the results.
I did a build with your patch and replaced just lib/tomcat-coyote.jar .
The exception did not show this time.
I'll mo
Delian Krustev wrote:
> Thanks for the build Mark, and sorry for the delay of this reply.
No problem.
> Could you please provide the patch also?
I have uploaded it here.
http://people.apache.org/~markt/dev/remove-sm-opt.patch
> I could not afford to move this instance to 6.0-trunk.
> I'll do the
On Thu, 13 Dec 2007 21:54:22 + Mark Thomas wrote:
> Snapshot build of trunk available from:
> http://people.apache.org/~markt/dev/
>
> This is the current 6.0.x trunk with the security manager optimisation
> reverted for the org.apache.coyote.* packages.
>
> *HEALTH WARNING*
> This is a snapsho
Delian Krustev wrote:
> On Tue, 11 Dec 2007 22:35:20 + Mark Thomas wrote:
>> Are you happy to mod the code and build a patched version yourself or do
>> you want some help? I can build a binary with the patch for you to test if
>> you wish.
>
> I've not built Tomcat from source before, so I'll
On Tue, 11 Dec 2007 22:35:20 + Mark Thomas wrote:
> Are you happy to mod the code and build a patched version yourself or do
> you want some help? I can build a binary with the patch for you to test if
> you wish.
I've not built Tomcat from source before, so I'll take advantage of the help
yo
Delian Krustev wrote:
> On Wed, 05 Dec 2007 22:13:00 + Mark Thomas wrote:
>> I am beginning to think that
>> http://svn.apache.org/viewvc?view=rev&rev=505593 introduced a subtle timing
>> issue. If Tomcat internal code causes Constants to be loaded, everything is
>> fine. If the webapp code cau
Krustev [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 06, 2007 10:18 AM
To: Tomcat Users List
Subject: Re: AccessControlException in Coyote Http11Processor (Tomcat
6.0.14). Bug in Coyote ?
On Wed, 05 Dec 2007 22:13:00 + Mark Thomas wrote:
> Did it happen straight away or did it work for a wh
On Wed, 05 Dec 2007 22:13:00 + Mark Thomas wrote:
> Did it happen straight away or did it work for a while and then fail?
Dec 3, 2007 10:14:24 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 152362 ms
..
Dec 3, 2007 10:17:22 PM org.apache.catalina.core.ApplicationDispa
Delian Krustev wrote:
> Well, here we go. The problem appeared once again after the next restart.
Did it happen straight away or did it work for a while and then fail?
I am beginning to think that
http://svn.apache.org/viewvc?view=rev&rev=505593 introduced a subtle timing
issue. If Tomcat interna
On Thu, 29 Nov 2007 07:51:07 + Mark Thomas wrote:
> It should show more information. If there is something subtle going on with
> the permissions then it should make it easier to figure out.
Well, here we go. The problem appeared once again after the next restart.
I've hidden the username and
On Thu, 29 Nov 2007 07:51:07 + Mark Thomas wrote:
> It should show more information. If there is something subtle going on with
> the permissions then it should make it easier to figure out.
The container has been restarted today.
Oddly enough the exception does not show now. I'll keep the o
Delian Krustev wrote:
> Hi Mark,
>
> On Tue, 27 Nov 2007 18:21:20 + 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 tr
Hi Mark,
On Tue, 27 Nov 2007 18:21:20 + 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 co
Delian Krustev wrote:
> My guess is that either this is a bug in the Coyote HTTP connector or
> the security policy is not strict enough and one of the
> installed applications (third party, I don't have access to the source)
> modifies the security manager somehow. My modifications
> to the polic
19 matches
Mail list logo
