Uploaded image for project: 'Geronimo'
  1. Geronimo
  2. GERONIMO-5356

EJB Client can access a stopped EJB Node

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Invalid
    • 2.2.1
    • 2.2.1
    • Clustering
    • Security Level: public (Regular issues)
    • None
    • OS: windows 2003 Sp2, winxp sp3

    Description

      1.Enable server ejb mutlicast, set MulticastEnabled=true of file var/config/config-substitutions.properties
      2.Deploy attached slsb.jar with plan slsb.xml to server 1, server2
      3.Deploy attached loadbeanwar.war to server 1.
      4.Access [server1]:8080/load/Multicast, it displays
      Run on single point server 1 : ejbd://9.123.237.141:4201
      Add 1 + 2 = 3
      Ping
      Sum 1 + 2 + 1 = 4
      Run on single point server 2 : ejbd://9.123.233.112:4201
      Add 1 + 2 = 3
      Ping
      Sum 1 + 2 + 1 = 4
      Run on multicast 3 : multicast://239.255.3.2:6142?group=cluster1
      Add 1 + 2 = 3
      Ping
      Sum 1 + 2 + 1 = 4
      Run on mulicast 4 : failover:sticky:ejbd://9.123.233.112:4201,ejbd://9.123.237.141:4201
      Add 1 + 2 = 3
      Ping
      Sum 1 + 2 + 1 = 4
      Run on mulicast 5 : failover:random:ejbd://9.123.233.112:4201,ejbd://9.123.237.141:4201
      Add 1 + 2 = 3
      Ping
      Sum 1 + 2 + 1 = 4
      Run on mulicast 6 : failover:round-robin:ejbd://9.123.233.112:4201,ejbd://9.123.237.141:4201,multicast://239.255.3.2:6142
      Add 1 + 2 = 3
      Ping
      Sum 1 + 2 + 1 = 4

      5.If i shutdown one server : 9.123.237.141,
      "Run on single point server 1 : ejbd://9.123.237.141:4201
      Add 1 + 2 = 3
      Ping
      Sum 1 + 2 + 1 = 4" this line still exist, seems no break, but in theory, if 9.123.237.141 shutdown, apps cann't acess loadbean via ejbd://9.123.237.141

      Attachments

        1. EJBMulticast.zip
          11 kB
          viola.lu

        Activity

          People

            Unassigned Unassigned
            viola.lu viola.lu
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: