4 Replies Latest reply on Aug 19, 2003 9:11 AM by adrian.brock

    Connectirn Swing client to JBoss over WAN

    jovial

      Hi,

      We are having EJB application deployed on JBoss 3.0.4 server. The Swing clients should be able to access the server over WAN. There is a firewall between JBoss server and the client.

      We have tried to open ports 1099 for JNDI and 4444 for RMI on the firewall but create() function of home objects still returns NULL. Why is that? Do we need to open additional ports

      thanks,

      dimitar

        • 1. Re: Connectirn Swing client to JBoss over WAN

          Have you specified 4444 as the port for JRMPInvoker.
          Also there was a bug fixed in 3.0.5 where a failure
          return null rather than throwing an exception.

          Regards,
          Adrian

          • 2. Re: Connectirn Swing client to JBoss over WAN
            jovial

            hi,

            Did you mean on this fragment of code in jboss-service.xml?


            4444



            I did. Is there any other place I have to do it?

            thanks,

            dimitar

            • 3. Re: Connectirn Swing client to JBoss over WAN
              jovial

              Hi Adrian,

              Let me rephrase my question. Can JBoss work behind a firewall if the client is not using HTTP to connect to it?

              thanks,

              dimitar

              • 4. Re: Connectirn Swing client to JBoss over WAN

                Yes.

                You need to make sure all the ports are open on the firewall
                and ensure the packets can be routed.
                You also need to ensure the RMI objects are bound to
                specific ports (it looks like you did this for JRMP,
                what about jndi? 1099 is just the bootstrap
                there is another port for the jndi communication),
                see the MBean config on the JMX Console.

                RMI uses ip addresses by default. You might find it
                easier to use the jvm system property -Djava.rmi.server.hostname if you can route packets by
                host.
                It may work better if you specify the bind address (this
                name changes depending upon the service)
                on each RMI object. Again see the attribute names
                on the JMX Console.

                Regards,
                Adrian