Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 4.2 IR8
    • Fix Version/s: 4.2 CR2
    • Component/s: EAP, JBossAS
    • Labels:
      None
    • Environment:

      Full SOA-P

    • Affects:
      Documentation (Ref Guide, User Guide, etc.), Release Notes

      Description

      This is intended as a tracking issue on how to run SOA-P with clustered JMS.

      I was able to run clustered JMS and let the servers to share the messages.
      And it really works out of the box (except for the ServerPeerID of course).

      Steps to reproduce:
      1. I switched off ServerInvoker's load balancing by setting the load balancer to FirstAvailable - just for sure.
      2. I used jms-provider in the jboss-esb.xml of my service because plain JMS provider doesn't use ServiceInvoker and this means no load balancing on the ESB side.
      3. I started 2 nodes and deployed the same service on both of them (it was not so easy - see SOA-231).
      4. I sent some messages to the nodes and voila - the load balancing happend on the JMS side.

      This means we can try to start failover testing now.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  mvecera Martin Vecera
                  Reporter:
                  mvecera Martin Vecera
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: