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?

John


Reply via email to