Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: v3.0.1
    • Fix Version/s: 3.1.2_b06
    • Component/s: orb
    • Labels:
      None
    • Environment:

      GlassFish Server Open Source Edition 3.0.1 (build 22)
      Java(TM) SE Runtime Environment (build 1.6.0_21-b07)

      Description

      When specifying properties for Glassfish connection like :

      org.omg.CORBA.ORBInitialHost='hostname'
      org.omg.CORBA.ORBInitialPort='portnumber'

      Other CORBA common properties seem to be ignored :

      com.sun.corba.ee.transport.ORBWaitForResponseTimeout=5
      com.sun.corba.ee.transport.ORBTCPConnectTimeouts=100:500:100:500
      com.sun.corba.ee.transport.ORBTCPTimeouts=500:2000:50:1000

      As you can see in this topic : http://blogs.sun.com/ejcorba/entry/client_side_transport_timeouts_and

      Steps to reproduce :

      • Define the given properties in a new InitialContext
      • Start the application from Eclipse :
      • Once when Glassfish is started and the EAR deployed : everything is ok
      • Once when Glassfish is not started at all : The timeout properties are ignored ; you have to wait 1 or 2 minutes before a timeout to be thrown.

        Activity

        Hide
        Cheng Fang added a comment -

        re-categorize it to orb compoment.

        Show
        Cheng Fang added a comment - re-categorize it to orb compoment.
        Hide
        Ken Cavanaugh added a comment -

        No plan to fix in 3.1.1

        Show
        Ken Cavanaugh added a comment - No plan to fix in 3.1.1
        Hide
        Ken Cavanaugh added a comment -

        Is this still a problem in 3.1.0? 3.0.1 shared a single ORB on the client side
        for all naming contexts, while 3.1.0 does not. However, properties passed in
        to the InitialContext are NOT passed on to the ORB. You'll need to set the
        properties as system properties for the ORB to see them.

        Show
        Ken Cavanaugh added a comment - Is this still a problem in 3.1.0? 3.0.1 shared a single ORB on the client side for all naming contexts, while 3.1.0 does not. However, properties passed in to the InitialContext are NOT passed on to the ORB. You'll need to set the properties as system properties for the ORB to see them.
        Hide
        Harshad Vilekar added a comment -

        Setting these properties as system properties works just fine with 3.1.2_b06 - The connection times out within 5 seconds.

        Example:
        java -Dcom.sun.corba.ee.transport.ORBWaitForResponseTimeout=5 -Dcom.sun.corba.ee.transport.ORBTCPConnectTimeouts=100:500:100:500 -Dcom.sun.corba.ee.transport.ORBTCPTimeouts=500:2000:50:1000 -cp .. <java client>

        Show
        Harshad Vilekar added a comment - Setting these properties as system properties works just fine with 3.1.2_b06 - The connection times out within 5 seconds. Example: java -Dcom.sun.corba.ee.transport.ORBWaitForResponseTimeout=5 -Dcom.sun.corba.ee.transport.ORBTCPConnectTimeouts=100:500:100:500 -Dcom.sun.corba.ee.transport.ORBTCPTimeouts=500:2000:50:1000 -cp .. <java client>

          People

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

            Dates

            • Created:
              Updated:
              Resolved: