Bug: Incorrect user being recorded for a post

Help
2010-08-27
2013-05-01
  • Manfred Wolff
    Manfred Wolff
    2010-08-30

    Thank you very much. I can submit the bug (after a testing period if evrything will go well) but it is not possible for me to build an 2.1.1 release. I can also submit it into the main branch.

     

  • Anonymous
    2012-07-13

    Hi Tony,

    We are facing the exact same issue with our Jtrac. Thanks for your patch, but could you let us know how to apply this patch.

    Thanks,
    Vinoy

     
  • Tony Hughes
    Tony Hughes
    2012-07-13

    Hi Vinoy

    The patch (included below for reference) just makes the change identified in the Resolution section of the bug.

    Resolution (extracted from Bug id = 3054238)
    - - - - - - - - - - - -
    To resolve this bug, use Wicket 1.3.7 (latest version of 1.3) which handles Exceptions when calling response.close( ) in WicketFilter.doGet( ).
    And therefore the Session is correctly cleared from the thread's memory.
    - - - - - - - - - - - -

    So you can apply this 'patch' manually if you prefer.

    Just open pom.xml and change the wicket and wicket-extensions version from 1.3.1 to 1.3.7.

    All the best.

    Cheers
    Tony

    Index: pom.xml
    ===================================================================
    --- pom.xml (revision 1351)
    +++ pom.xml (working copy)
    @@ -329,12 +329,12 @@
             <dependency>
                 <groupId>org.apache.wicket</groupId>
                 <artifactId>wicket</artifactId>
    -            <version>1.3.1</version>            
    +            <version>1.3.7</version>            
             </dependency>        
             <dependency>
                 <groupId>org.apache.wicket</groupId>
                 <artifactId>wicket-extensions</artifactId>
    -            <version>1.3.1</version>           
    +            <version>1.3.7</version>           
             </dependency>
             <dependency>
                 <groupId>org.slf4j</groupId>
    
     

  • Anonymous
    2012-07-16

    Thanks Tony,

    I searched the installation folder fully but couldn't find the pom.xml file anywhere.
    Could you please let us know how to find and do it step by step.

    Thanks a lot,
    Vinoy

     

  • Anonymous
    2012-07-16

    Hi Tony,

    Could you please help us fixing this bug.
    We have installed version 2.1.0 on our server. As I am not much familiar with compiling these packages, could you please send us a compiled installation package based on 2.1.0 version with this bug fixed.

    email: vinoykr (at) gmail.com

    Thanks in advance,
    Vinoy

     
  • Tony Hughes
    Tony Hughes
    2012-07-16

    Hi Vinoy

    Sorry, I had presumed you have been building your own JTrac.

    To "patch" an already installed JTrac, you could try the following:

    ** PLEASE PERFORM THIS ON A TEST INSTALL FIRST **

    1. Download the 1.3.7 jars, eg from
    http://repo1.maven.org/maven2/org/apache/wicket/wicket/1.3.7/wicket-1.3.7.jar
    http://repo1.maven.org/maven2/org/apache/wicket/wicket-extensions/1.3.7/wicket-extensions-1.3.7.jar

    2. For standard tomcat deploy, cd to the following dir:
    /webapps/jtrac/WEB-INF/lib

    3. Backup the following to another location:
    wicket-1.3.1.jar
    wicket-extensions-1.3.1.jar

    4. Replace the 1.3.1 jars referenced in step 3 above, with the 1.3.7 jars you downloaded in step 1 above.

    5. Restart JTrac.

    (For pre-compiled builds with this bug fixed, you should contact the project admins.)

    Cheers
    Tony