3.x right? 1099 is used to obtain an RMI proxy to JNDI. This is a standard socket. JNDI invocations happen through RMI though and must be configured through the NamingService mbean. RTFM.
Other ports that must be accessible: WebServer 8083 (for classloading) EJB Communications 4444 (JRMPInvoker) If you don't want this, you can use HTTP as a transport for everything I believe, except maybe the Webserver for classloading, I don't know. Bill > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Jeremy > Rempel > Sent: Friday, February 21, 2003 5:00 PM > To: [EMAIL PROTECTED] > Subject: [JBoss-user] Force RMI to a specific port > > > My server communicates with clients running applets. I have port 1099 > open on the server and thats how my jndi.properties references the > server. The server is still using random ports and only works when all > ports are open not just 1099. > > How can I use jboss rmi through a firewall? > > I am using EJB's. > > Thanks, Jeremy > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. > The most comprehensive and flexible code editor you can use. > Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. > www.slickedit.com/sourceforge > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
