Anonymous | Login | Signup for a new account | 12-17-2024 08:25 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0001934 | [Resin] | minor | always | 08-10-07 11:31 | 08-29-07 14:07 | ||||
Reporter | norlab | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | closed | Product Version | 3.1.2 | ||||||
Summary | 0001934: Security Manager does not start 3.1.2 | ||||||||
Description |
Using the <security-manager/> tag does not start the security manager. Using <security-manager/> <jvm-arg>-Djava.security.policy=file:/resin/resin.policy</jvm-arg> <jvm-arg>-Djava.security.debug=true</jvm-arg> <jvm-arg>-Xmx256m</jvm-arg> <jvm-arg>-Xss1m</jvm-arg> <jvm-arg>-J-d32</jvm-arg> <jvm-arg>-Xdebug</jvm-arg> <jvm-arg>-Dcom.sun.management.jmxremote</jvm-arg> I am able to start the security manager by modifying the start script to be: exec $java -Djava.security.manager -Djava.security.debug=all -Djava.security.policy=file:/resin/resin.policy -jar $bin/../lib/resin.jar $* In both cases the security manager does not follow policy rules. |
||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
31 total queries executed. 26 unique queries executed. |