The linux scenario does not work. I can take the same configuration and
drop it on Solaris and no problem.
Rickard �berg
<[EMAIL PROTECTED]> To: jBoss Developer
<[EMAIL PROTECTED]>
Sent by: cc:
<[EMAIL PROTECTED] Subject: Re: [jBoss-Dev] Debug
of Access Denied
-dogs.com>
10/16/98 12:39 AM
Please respond to
"jBoss Developer"
Hi!
[EMAIL PROTECTED] wrote:
> This is not specifically about JBoss but is getting in the way of
deploying
> on Linux.
>
> I am using a policy file that is referenced on the command line at server
> startup that grants all permission's.
>
> Client JDK 1.3
>
> On Linux: (JDK 1.2.2)
> When both Client and Server are on the same machine, no problem. All
works
> well.
> When client is on different machine, BOOM. I get the error below when the
> policy file is used at client start up and I get:
> java.security.AccessControlException: access denied
> (java.net.SocketPermission xx.xx.xxx.xxx:10002 connect,resolve)
> When the policy file is not used.
>
> On Solaris 7 (JDK 1.2.1)
> When both Client and Server are on the same machine, no problem. All
works
> well.
> Move client to another machine, use policy file and all works well.
> Don't use the policy file and I get:
> java.security.AccessControlException: access denied
> (java.net.SocketPermission xx.xx.xxx.xxx:10002 connect,resolve)
>
> Ideas? Is there something about Linux that I am missing with RMI? JDK
> Configuration?
This seems to be correct. You have installed a security manager, so you
have to grant code the permissions it need (AllPermission for example).
The above seems to be correct.
Why do you think that it is not correct?
regards,
Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
