You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/12/28 09:31:54 UTC
DO NOT REPLY [Bug 17523] -
Servlet can't getSession
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17523>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17523
Servlet can't getSession
------- Additional Comments From wglass@forio.com 2003-12-28 08:31 -------
I hit this problem too. After several hours, I realized that a workaround is
to include the following in catalina.policy:
// needed to overcome Tomcat bug with Coyote
// http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17523
// org.apache.coyote.tomcat4.CoyoteRequest.PrivilegedGetSession
Grant {
permission
java.lang.RuntimePermission "defineClassInPackage.org.apache.coyote.tomcat4";
permission
java.lang.RuntimePermission "defineClassInPackage.org.apache.coyote.tomcat4.*";
}
Hope this helps anyone else who hits this frustrating issue.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: Procrun improvements
Posted by Bill Barker <wb...@wilshire.com>.
----- Original Message -----
From: "Remy Maucherat" <re...@apache.org>
To: "Tomcat Developers List" <to...@jakarta.apache.org>
Sent: Sunday, December 28, 2003 1:42 AM
Subject: Procrun improvements
> Hi,
>
> There are some problems with procrun for the VM setup. Right now, the
> only setting which works AFAIK is using "java" and letting procrun
> detect the VM using the Windows registry.
>
> I think the following two items should be supported:
> - I think it should be possible to specify a path to the JVM base
> directory (this feature is supposed to be present, but doesn't actually
> work for reasons I can't remember); using the config dialog to change
> the JVM path makes the config dialog refuse to start again
> - when using "java", procrun should look at the JAVA_HOME env property
> before looking in the registry, to be consistent with all Java based
> tools available
>
If you want to open a commons BZ item for this, I can attach patches for it
(I'm not a commons committer, so the round-about is all we've got if you
want to go through me :).
> Rémy
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
RE: Procrun improvements
Posted by Mladen Turk <mt...@apache.org>.
> -----Original Message-----
> From: Remy Maucherat
> Subject: Procrun improvements
>
> Hi,
>
> There are some problems with procrun for the VM setup. Right
> now, the only setting which works AFAIK is using "java" and
> letting procrun detect the VM using the Windows registry.
The procrun is a little bit clumsy to maintain.
I'm working on the 2.0 version that will have spitted code
in few files that will be easier to maintain, with lots of
enhancements.
The question is do you need the mentioned features _now_,
if there is a new release on the horizon, or this can wait
for a week or two?
MT.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Procrun improvements
Posted by Remy Maucherat <re...@apache.org>.
Hi,
There are some problems with procrun for the VM setup. Right now, the
only setting which works AFAIK is using "java" and letting procrun
detect the VM using the Windows registry.
I think the following two items should be supported:
- I think it should be possible to specify a path to the JVM base
directory (this feature is supposed to be present, but doesn't actually
work for reasons I can't remember); using the config dialog to change
the JVM path makes the config dialog refuse to start again
- when using "java", procrun should look at the JAVA_HOME env property
before looking in the registry, to be consistent with all Java based
tools available
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org