glassfish
  1. glassfish
  2. GLASSFISH-3762

EJB deployed on the Glassfish on server with multiple IP

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 9.1pe
    • Fix Version/s: future release
    • Component/s: orb
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

      Description

      Server OS: Linux debian (sarge), kernel 2.6.8-3-386, libc6 2.3.2.ds1-22
      Glassfish V2
      java : version "1.6.0", Java(TM) SE Runtime Environment (build 1.6.0-b105)
      Client OS : Windows XP SP2

      I can't connect to EJB, deployed on the Glassfish, via IIOP.
      It has multiple IP addresses : LAN 192.x.x.x and Internet 217.x.x.x.
      I set two IIOP listeners. The first listener on 192.x.x.x (port 9411), the
      second - on 217.x.x.x (port 8811).
      If client is trying to connect from the LAN, the connection is successful. Two
      connections are opened (both to the 192.x.x.x:9411). It is clear from the netstat.
      If client is trying to connect from the Internet, its connection is fail. The
      first connection is established correctly (to the 217.x.x.x:8811), but the
      second one is trying to connect 192.x.x.x:8811 or 192.x.x.x:9411, which is not
      accessible from the Internet since it is internal network IP.

        Activity

        Hide
        gfbugbridge added a comment -

        <BT6616065>

        Show
        gfbugbridge added a comment - <BT6616065>
        Hide
        Mahesh Kannan added a comment -

        Can the submitter provide the server.log containing the stacktrace? Also, it
        will be helpful if the snippet of the client code can be posted

        Show
        Mahesh Kannan added a comment - Can the submitter provide the server.log containing the stacktrace? Also, it will be helpful if the snippet of the client code can be posted
        Hide
        Mahesh Kannan added a comment -

        Have asked the submitter to provide stacktrace and client code snippet. In any
        case this doesn't even sound like an ejb container bug. Transferring this to ORB
        for their evaluation and since this is also not a show stopper, adding as91ur1-na

        Show
        Mahesh Kannan added a comment - Have asked the submitter to provide stacktrace and client code snippet. In any case this doesn't even sound like an ejb container bug. Transferring this to ORB for their evaluation and since this is also not a show stopper, adding as91ur1-na
        Hide
        falsehood added a comment -

        Created an attachment (id=1235)
        problem stacktace

        Show
        falsehood added a comment - Created an attachment (id=1235) problem stacktace
        Hide
        falsehood added a comment -

        Created an attachment (id=1236)
        graphical description of the problem

        Show
        falsehood added a comment - Created an attachment (id=1236) graphical description of the problem
        Hide
        falsehood added a comment -

        Stacktrace and graphical description of the problem had been attached.

        Show
        falsehood added a comment - Stacktrace and graphical description of the problem had been attached.
        Hide
        Ken Cavanaugh added a comment -

        This has become a rather common feature request, and I think we'll
        implement a solution for GFv3. Basically, this is yet another example
        of why NAT is a very bad idea, but we are stuck with it until the world
        moves to IPv6.

        Given that we need to do something to handle this, what I plan is to add
        a capability of tagging addresses in an IOR with a domain, adding a
        configurable domain to the ORB, and then modifying the
        CorbaContactInfoListIterator to only look at those ContactInfos that
        correspond to addresses in the same domain as the client ORB. For outside
        clients, we would default this, whereas inner clients (behind the firewall)
        would need to set a domain (probably just an int).

        Since this is mostly an ORB issue, I'm re-assigning it to myself and changing
        this to an enhancement for V3.

        Show
        Ken Cavanaugh added a comment - This has become a rather common feature request, and I think we'll implement a solution for GFv3. Basically, this is yet another example of why NAT is a very bad idea, but we are stuck with it until the world moves to IPv6. Given that we need to do something to handle this, what I plan is to add a capability of tagging addresses in an IOR with a domain, adding a configurable domain to the ORB, and then modifying the CorbaContactInfoListIterator to only look at those ContactInfos that correspond to addresses in the same domain as the client ORB. For outside clients, we would default this, whereas inner clients (behind the firewall) would need to set a domain (probably just an int). Since this is mostly an ORB issue, I'm re-assigning it to myself and changing this to an enhancement for V3.
        Hide
        Ken Cavanaugh added a comment -

        Should also mark this started.

        Show
        Ken Cavanaugh added a comment - Should also mark this started.
        Hide
        Ken Cavanaugh added a comment -

        Considering for v3.1.

        Show
        Ken Cavanaugh added a comment - Considering for v3.1.

          People

          • Assignee:
            Harshad Vilekar
            Reporter:
            falsehood
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: