Uploaded image for project: 'EJB 3.0'
  1. EJB 3.0
  2. EJBTHREE-1429

SFSB replication soak testing

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • TBD EAP 5
    • None
    • Clustering
    • None

      Long running tests of SFSB replication under heavy load.

      Should include:

      1) Letting a significant percentage of sessions passivate and later activate.
      2) Letting a significant percentage of sessions expire due to time out.
      3) Invalidating remaining sessions after a while (i.e. don't use any sessions for the life of test; all get used and replaced after a while).
      4) Perhaps, a low (say 1/1000) probability of failover.

        1.
        		 check thread.sleep after failover Sub-task Closed Major Radoslav Husar
        2.
        		 check why test sometimes hangs up Sub-task Closed Major Radoslav Husar
        3.
        		 add other configurations to hudson+create hudson tasks Sub-task Closed Major Radoslav Husar
        4.
        		 after EJB3 is not found, forget that wrong session and create new one Sub-task Closed Major Radoslav Husar
        5.
        		 add ejb3 spefic params to wiki Sub-task Closed Major Radoslav Husar
        6.
        		 increase / check thread pool for EJB Sub-task Closed Major Radoslav Husar
        7.
        		 move uncommited code to old repository to new repository Sub-task Closed Major Radoslav Husar
        8.
        		 remove bandwidth monitoring in SF config for EJB3 Sub-task Closed Major Radoslav Husar
        9.
        		 implement to ExplicitFailoverInterceptor double checking to avoid stale failover requests Sub-task Closed Major Radoslav Husar

            rhn-engineering-rhusar Radoslav Husar
            bstansbe@redhat.com Brian Stansberry
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: