RE: [Wrapper-user] Re: RMI

[Stacey A. <Sta...@in...>]

Thanks Leif.  And I will post to the user list from now on.  ;)  I got my
account yesterday evening.

That was my guess from what I had seen.   I was looking at this to replace
some vb code I have.  It uses an xml file to start our servers and
automatically starts an rmi for each.  The benefit is that that the user can
start up N number of servers with one service...our clients had a need for
at least three servers.  Plus they can "mix and match".  In other words they
could start three xyz servers and two abc servers by adding a line in the
xml file for each server they want.  

I can see the downfall of having all the servers tied to one service, but
our client has uhmmm ... Difficulties dealing with their three servers let
alone three services.

I agree that starting the rmi programtically would be a great alternative
and then I could work w/ the JSW.  

Once again, thanks for your input! 

:)

sra



-----Original Message-----
From: Leif Mortenson [mailto:le...@ta...] 
Sent: Thursday, April 14, 2005 12:23 AM
To: Stacey Acosta; Wrapper User List
Subject: [Wrapper-user] Re: RMI

Stacey,
The Wrapper user list is a better place for these questions. :-)

The Wrapper only supports the execution of a single JVM per Wrapper
instance. If you want to have both an app and an rmiregistry then you would
need to either use two JVM/Wrappers or create the rmiregistry instance from
within your application.

The second is not as hard as it sounds. This is from an application that I
have which does the same. First you need to set a security manager:
if ( System.getSecurityManager() == null ) { System.setSecurityManager( new
RMISecurityManager() ); }

There is a lot of unrelated code in my program that you probably don't need,
but I think the guts of what you want are the following:
m_registry = LocateRegistry.createRegistry( m_port, m_rmiSocketFactory,
m_rmiSocketFactory ); getLogger().debug( " RMI registry created." );

// Now that we have a registry, bind the RemoteBackboneServer instance.
getLogger().debug( "Binding master server instance..." ); m_registry.rebind(
MASTER_NAME, m_remoteServer );

Variable description. m_port is the RMI port to use. m_rmiSocketFactory is a
custom RMISocketFactory implementation that lets me handle socket timeouts.
m_remoteServer is a UnicastRemoteObject subclass instance that represents
the application to the RMI world.

Cheers,
Leif

Stacey Acosta wrote:

> Hello Leif,
> Short of creating two services (one for the app and one for 
> rmiregistry), does JSW support rmi? I haven't found any documentation 
> on the site nor have I seen any information about it in either the 
> user or support mailing lists.
> If it does and there is some documentation, could you point me to it?
> Thanks,
> sra




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide Read honest & candid reviews
on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user