ASF Bugzilla – Attachment 13405 Details for
Bug 4543
RMI fails if tomcat is installed in directory with white space
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Help
|
New Account
|
Log In
Remember
[x]
|
Forgot Password
Login:
[x]
clean work-around with need for security policy input
UnmarshallWorkaround.txt (text/plain), 1.16 KB, created by
Shawn Bertini
on 2004-11-11 18:04:36 UTC
(
hide
)
Description:
clean work-around with need for security policy input
Filename:
MIME Type:
Creator:
Shawn Bertini
Created:
2004-11-11 18:04:36 UTC
Size:
1.16 KB
patch
obsolete
>I have worked around the UnmarshalException when running tomcat in a >directory that has spaces in the name by setting the following options >on my RMI server side: > > -Djava.rmi.server.codebase=http://localhost:8080/WEB-INF/classes/myapp.jar > -Djava.rmi.server.useCodebaseOnly=true > -Djava.rmi.security.policy=../policy > >The policy file looks like: > > grant { > permission java.security.AllPermission; > }; > >When launching tomcat, I replace the $TOMCAT_HOME/conf/catalina.policy file >with the above, open policy file and launch "catalina.bat start -security". >Everything works fine, even across different machines, until I try to use >a more restrictive security policy. I tried to use the catalina.policy >shipped with Tomcat with the following addition (and 100 others): > > grant codeBase "file:${catalina.home}/webapps/ROOT/-" { > permission java.security.AllPermission; > } > >Without this section, I get a security exception. With it, I get a class cast >exception. Again, everything works when I just open up all permissions. If >anyone can help with the security issue, I believe this is a pretty reasonable >workaround.
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 4543
: 13405