Uploaded image for project: 'RESTEasy'
  1. RESTEasy
  2. RESTEASY-3155

Concurrency issues in ResteasyViolationException

XMLWordPrintable

    • Hide
      • For 3.15.3 version:
      unzip resteasyviolationexception-3.15.zip
      cd resteasyviolationexception-3.15
      mvn clean test
      ...
      [ERROR] Errors: 
      [ERROR]   ResteasyViolationExceptionToStringReproducerTests.execBruteforce:119 » Execution
      [INFO] 
      [ERROR] Tests run: 4, Failures: 0, Errors: 2, Skipped: 0
      
      • For main 6.1.0.Beta2:
      unzip resteasyviolationexception-6.zip
      cd resteasyviolationexception-6
      mvn clean test
      ...
      [ERROR] Errors: 
      [ERROR]   ResteasyViolationExceptionToStringReproducerTests.execBruteforce:119 » Execution
      [INFO] 
      [ERROR] Tests run: 3, Failures: 0, Errors: 1, Skipped: 0
      
      Show
      For 3.15.3 version: unzip resteasyviolationexception-3.15.zip cd resteasyviolationexception-3.15 mvn clean test ... [ERROR] Errors: [ERROR] ResteasyViolationExceptionToStringReproducerTests.execBruteforce:119 » Execution [INFO] [ERROR] Tests run: 4, Failures: 0, Errors: 2, Skipped: 0 For main 6.1.0.Beta2: unzip resteasyviolationexception-6.zip cd resteasyviolationexception-6 mvn clean test ... [ERROR] Errors: [ERROR] ResteasyViolationExceptionToStringReproducerTests.execBruteforce:119 » Execution [INFO] [ERROR] Tests run: 3, Failures: 0, Errors: 1, Skipped: 0

      This is a continuation of RESTEASY-2914. The previous JIRA fixed a ConcurrentModificationException but the attached reproducer shows that there are still concurrency issues and the exception sometimes return the empty String when calling concurrently the toString method.

      There are two separate reproducers for 3.15.3 and 6.1.0.Beta2 versions (there are differences between both versions).

            rhn-support-rmartinc Ricardo Martin Camarero
            rhn-support-rmartinc Ricardo Martin Camarero
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: