Hi Trent,

   There's a problem accesing CommAPI after setting an
RMISecurityManager(). I did not have time to find out where
the problem is, just went thru a simple workaround. Now I
see somebody else on JINI-USERS reporting the same problem
and it happens not to appear on Windoze machines.

Just for your information and for you to be aware of it
I am attaching two messages (original message and my response)
to JINI-USERS.

I personally think the problem may well be at comm.jar
solaris implementation.

Best regards
--Alejandro

Hi,

Allow me to clarify this problem further. I am aware of the Java 2
security policies, and I am starting both the server and client with
the -Djava.security.policy=policy parameter, where policy contains
the usual

   permission java.security.AllPermission

The code works fine on Windows with the win32com.dll driver for
Javacomm API. But on Linux the same code fails when trying to load
the RXTXCommDriver (native driver for javacomm on linux). Seems
like it might be a bug in gnu.io.RXTXCommDriver, either that or
RMISecurityManager is not behaving the same way on Linux.

Any Ideas?

Thanks,
Doug


> Correction: I meant to say:
>
>  - if I comment out System.setSecurityManager(new
RMISecurityManager())
>                                                   ^^^
>    the serial port access works fine. But with the RMI security
manager
>    the loading of serial port drivers fails.
>
> Doug
>
>
>
> ----------  Forwarded Message  ----------
> Subject: RMI Security Manager prevents access to other classes?
> Date: Sun, 5 Dec 1999 04:49:54 -0800
> From: Doug Sutherland <doug@los-gatos.net>
>
>
> Hi There,
>
> I am working with JDK1.2 (blackdown) on Linux kernel 2.0.36 (Redhat
5.2).
> I have an RMI client application that connects to an RMI server,
grabs
> some data, and sends it out the serial port to an LCD display using
the
> Java commapi for Linux. I have a situation where:
>
>  - if I comment out System.setSecurityManager(new SecurityManager())
>    the serial port access works fine, I write out characters to the
>    display no problem. The program finds the serial ports using
>    getPortIdentifier and is able to open the serial port.
>
>  - if I put back in the RMI security manager, the application does
>    not find the serial ports, instead it throws an exception while
>    trying to load the serial drivers:
>
>      caught java.lang.IllegalArgumentException: name can't be null
>      while loading driver gnu.io.RXTXCommDriver
>
> It appears that the RMI security manager is somehow messing with the
> loading of the native serial port driver (RXTX for linux). I assume
> that this is a feature not a bug. What do I need to do to get the
> RMI security manager to allow access to other classes? In this case
> the serial driver consists of a native shared library:
>
>  /usr/local/java/jdk1.2/jre/lib/i386/libSerial.so
>
> And java classes that reside here:
>
>  /usr/local/java/jdk1.2/jre/lib/ext/jcl.jar
>  /usr/local/java/jdk1.2/jre/lib/ext/comm.jar
>
> Anyone have any ideas? Do you have commapi working in an app
> that also does RMI? Any tips would be appreciated.
>
> Thanks,
> Doug

===========================================================================
To unsubscribe, send email to listserv@java.sun.com and include in the
body
of the message "signoff JINI-USERS".  For general help, send email to
listserv@java.sun.com and include in the body of the message "help".

To view past JINI-USERS postings, please see:
http://archives.java.sun.com/archives/jini-users.html

To participate in the community, please visit:
http://www.jini.org

>
> The code works fine on Windows with the win32com.dll driver for
> Javacomm API. But on Linux the same code fails when trying to load
> the RXTXCommDriver (native driver for javacomm on linux). Seems
> like it might be a bug in gnu.io.RXTXCommDriver, either that or
> RMISecurityManager is not behaving the same way on Linux.
>
> Any Ideas?
>
I've experienced that very same problem. My work around was
to install RMISecurityManager _after_ fetching the desired
CommPortIdentifier (and of course I can perform I/O on the ports
after setting RMISecurityManager)

This is not necessary a problem with RXTXCommDriver,
there are other components involved such as 'comm.jar'.

--Alejandro

===========================================================================
To unsubscribe, send email to listserv@java.sun.com and include in the
body
of the message "signoff JINI-USERS".  For general help, send email to
listserv@java.sun.com and include in the body of the message "help".

To view past JINI-USERS postings, please see:
http://archives.java.sun.com/archives/jini-users.html

To participate in the community, please visit:
http://www.jini.org