Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-6882

A client is not able to invoke EJB's deployed as "HASingleton deployment"

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 11.0.0.Final
    • 10.0.0.Final, 11.0.0.Alpha1
    • Clustering, EJB
    • None
    • Hide

      Checkout https://github.com/wfink/jboss-eap-playground/tree/master/eap7ClusterHASingletonDeployment
      follow the readme and build the application,
      start both servers.
      If node1 is the owner of the app

      • invoke the client and see it works
      • restart node1
      • now node2 become owner of the app
      • invoke client and seeit will fail
      Show
      Checkout https://github.com/wfink/jboss-eap-playground/tree/master/eap7ClusterHASingletonDeployment follow the readme and build the application, start both servers. If node1 is the owner of the app invoke the client and see it works restart node1 now node2 become owner of the app invoke client and seeit will fail

    Description

      Given that an application contains a SLSB and is clustered, any EJB client will be updated to have a view off all cluster members and is able to use and failover to any node in the cluster no matter whether it is in the initial list of servers.

      Now if the application is marked as "singleton-deployment" via jboss-all.xml and deployed to all servers only one server in a cluster will pick it and make it active.
      Now the expectation is that a client is routed to that server no matter whether this special server is included in the clients initial connection list.

      The interesting thing is that the client.log show that both servers are connected it the application is NOT marked as singleton
      But only the initial server is connected if the app is marked as singleton!

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-5422 [GSS](7.1.0) A client is not able to invoke EJB's deployed as "HASingleton deployment"

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-7765 Application deployed as "singleton-deployment" in a cluster is not reachable for EJB calls under all circumstances

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              pferraro@redhat.com Paul Ferraro
              rhn-support-wfink Wolf Fink
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: