Details

      Description

      When a site is under a load of requests, using eZDFS, over oracle database, ORA-0001 errors, leading to segmentation fault, may occur.

      steps to reproduce
      • Configure two nodes behind a load balancer
      • Using jmeter (or a different tool of your choice) simulate several clients accessing the same page in concurrency.
      • While the test is running, order cache clearing from the back end, in order to increase the damage
      • Check your error.log. Entries such as the one below will start flooding it

       Aug 13 2013 21:34:14 ] [192.168.3.4] Timing Point: Module end 'content'
      [ Aug 13 2013 21:34:14 ] [192.168.3.4] _storeContents(var/ezdemo_site/cache/designbase_e9cf5ecd5ac461977ad3639c58b5fbc6.php, ..., designbases, php)::_storeContents(var/ezdemo_site/cache/designbase_e9cf5ecd5ac461977ad3639c58b5fbc6.php, ..., designbases, php):
      Failed to execute SQL for function:
       INSERT INTO ezdfsfile (name, name_hash, datatype, scope, filesize, mtime, expired) VALUES ('var/ezdemo_site/cache/designbase_e9cf5ecd5ac461977ad3639c58b5fbc6.php', 'd9b6fdcd5805b811eeb9f673e767b411', 'php', 'designbases', '654', 1376422454, '0')
      1 : ORA-00001: unique constraint (EZP.SYS_C00169727) violated
      [ Aug 13 2013 21:34:14 ] [192.168.3.4] :
      Failed to insert file metadata while storing contents. Possible race condition
      1: ORA-00001: unique constraint (EZP.SYS_C00169727) violated
      

        Issue Links

          Activity

          Hide
          Bertrand Dunogier added a comment -
          Show
          Bertrand Dunogier added a comment - Pull request: https://github.com/ezsystems/ezoracle/pull/15 .
          Show
          Yannick Roger (Inactive) added a comment - Fixed in: ezoracle master : https://github.com/ezsystems/ezoracle/commit/5fb896f404602414d75617784ed8c7fc4d7a0202 ezpublish-legacy master : https://github.com/ezsystems/ezpublish-legacy/commit/08ee40a59b2433d5979268030a201e306de1e1bb
          Hide
          Bertrand Dunogier added a comment -

          @QA Here's a summary of the information I have that you can use:

          Using different DB schemas/links

          The unable to connect errors do vanish if I use a different DB link for the cluster & eZ Publish schemas. I've done that using MySQL for the eZ schema and Oracle for the cluster schema. I think you should test with different schemas on oracle.

          Enabling persistent connections

          Since Gaetano suggested it, I have tried with cluster & ez tables on the same schema BUT with persistent connections enabled on both cluster & ez connections. I don't get any Unable to connect errors, but I once got an "error taking over timed out cache generation", out of three attempts.

          Show
          Bertrand Dunogier added a comment - @QA Here's a summary of the information I have that you can use: Using different DB schemas/links The unable to connect errors do vanish if I use a different DB link for the cluster & eZ Publish schemas. I've done that using MySQL for the eZ schema and Oracle for the cluster schema. I think you should test with different schemas on oracle. Enabling persistent connections Since Gaetano suggested it, I have tried with cluster & ez tables on the same schema BUT with persistent connections enabled on both cluster & ez connections. I don't get any Unable to connect errors, but I once got an "error taking over timed out cache generation", out of three attempts.

            People

            • Assignee:
              Unassigned
              Reporter:
              Joaquim Cavalleri (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 3 days, 3 hours, 5 minutes
                3d 3h 5m