Tapestry 5
  1. Tapestry 5
  2. TAP5-403

OneShotLock tests fail under JDK 1.6 because of JVM differences

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.0, 5.0.18
    • Fix Version/s: 5.1.0.0
    • Component/s: tapestry-ioc
    • Labels:
      None

      Description

      The failures are due to an incorrect error message generated by org.apache.tapestry5.ioc.internal.util.OneShotLock

      As mentioned in the comments of that method, Thread.currentThread().getStackTrace[4] is used instead of
      Thread.currentThread().getStackTrace[3] and this was found by trial and error... in java1.6 however,
      Thread.currentThread().getStackTrace[3] is indeed the correct choice for the caller method

        Activity

        Andreas Andreou created issue -
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Assignee Howard M. Lewis Ship [ hlship ]
        Howard M. Lewis Ship made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Howard M. Lewis Ship made changes -
        Summary Test failures under jdk1.6 OneShotLock tests fail under JDK 1.6 because of JVM differences
        Howard M. Lewis Ship made changes -
        Resolution Fixed [ 1 ]
        Fix Version/s 5.1.0.0 [ 12313428 ]
        Status In Progress [ 3 ] Closed [ 6 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        25d 2h 57m 1 Howard M. Lewis Ship 30/Dec/08 00:23
        In Progress In Progress Closed Closed
        10m 26s 1 Howard M. Lewis Ship 30/Dec/08 00:33

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Andreas Andreou
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development