Hello,
I recently upgraded to JRun 3.1 build 16777 and also applied
the duplicate session id fix.
Now I see the following effect:
Specifying
user.javaargs=-Djava.security.manager -Djava.security.policy={jrun.r
ootdir}\lib\jrun.policy
as additional command-line options in the local.properties file
of the default server will prevent JRun from starting.
The default-err.log says that JRun cannot read the local.properties from
within the default server (i.e. when it re-reads the local.properties
after
the security manager has been installed).
java.security.AccessControlException: access denied (java.io.FilePermission
D:\Programme\Allaire\JRun3.1\servers\default\local.properties read)
at java.security.AccessControlContext.checkPermission(AccessControl
Context.java:272)
at java.security.AccessController.checkPermission(AccessController.
java:399)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:5
45)
at java.lang.SecurityManager.checkRead(SecurityManager.java:890)
at java.io.FileInputStream.<init>(FileInputStream.java:61)
at allaire.jrun.ServiceConfig.<init>(../ServiceConfig.java:67)
at JRun.main(../../../JRun.java:102)
This is strange, because I'm using the default policy file provided by
Allaire
(see above) which contains this single entry:
grant {
permission java.security.AllPermission;
};
I have not seen this behavior before upgrading. Can anyone reproduce this,
or tell me where I'm going wrong? I really want to run my applications
with a
SecurityManager installed.
Thanks,
Sebastian
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Get the mailserver that powers this list at http://www.coolfusion.com
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
