You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Craig McIlwee (JIRA)" <ji...@apache.org> on 2008/06/12 18:48:45 UTC

[jira] Created: (WICKET-1699) NPE in RequestLogger

NPE in RequestLogger
--------------------

                 Key: WICKET-1699
                 URL: https://issues.apache.org/jira/browse/WICKET-1699
             Project: Wicket
          Issue Type: Bug
          Components: wicket
    Affects Versions: 1.4-M2
            Reporter: Craig McIlwee
             Fix For: 1.4-M3


RequestLogger throws an NPE at line 200 because the field 'active' is never assigned a value when the class is instantiated.  In older versions (I am migrating from 1.3.3) this field was just a native int so the value would default to 0, but sometime between 1.3.3 and 1.4m2 it has changed to an AtomicInteger and never assigned a value via new AtomicInteger() or new AtomicInteger(someInt).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (WICKET-1699) NPE in RequestLogger

Posted by "James Carman (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604672#action_12604672 ] 

James Carman commented on WICKET-1699:
--------------------------------------

In case anyone's interested, it looks like this was fixed in revision 661205.

> NPE in RequestLogger
> --------------------
>
>                 Key: WICKET-1699
>                 URL: https://issues.apache.org/jira/browse/WICKET-1699
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4-M2
>            Reporter: Craig McIlwee
>             Fix For: 1.4-M3
>
>   Original Estimate: 0.08h
>  Remaining Estimate: 0.08h
>
> RequestLogger throws an NPE at line 200 because the field 'active' is never assigned a value when the class is instantiated.  In older versions (I am migrating from 1.3.3) this field was just a native int so the value would default to 0, but sometime between 1.3.3 and 1.4m2 it has changed to an AtomicInteger and never assigned a value via new AtomicInteger() or new AtomicInteger(someInt).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (WICKET-1699) NPE in RequestLogger

Posted by "James Carman (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604671#action_12604671 ] 

James Carman commented on WICKET-1699:
--------------------------------------

Looks like Igor already fixed this one.  Can someone please resolve/close it?

> NPE in RequestLogger
> --------------------
>
>                 Key: WICKET-1699
>                 URL: https://issues.apache.org/jira/browse/WICKET-1699
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4-M2
>            Reporter: Craig McIlwee
>             Fix For: 1.4-M3
>
>   Original Estimate: 0.08h
>  Remaining Estimate: 0.08h
>
> RequestLogger throws an NPE at line 200 because the field 'active' is never assigned a value when the class is instantiated.  In older versions (I am migrating from 1.3.3) this field was just a native int so the value would default to 0, but sometime between 1.3.3 and 1.4m2 it has changed to an AtomicInteger and never assigned a value via new AtomicInteger() or new AtomicInteger(someInt).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (WICKET-1699) NPE in RequestLogger

Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg resolved WICKET-1699.
-----------------------------------

    Resolution: Fixed
      Assignee: Igor Vaynberg

> NPE in RequestLogger
> --------------------
>
>                 Key: WICKET-1699
>                 URL: https://issues.apache.org/jira/browse/WICKET-1699
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4-M2
>            Reporter: Craig McIlwee
>            Assignee: Igor Vaynberg
>             Fix For: 1.4-M3
>
>   Original Estimate: 0.08h
>  Remaining Estimate: 0.08h
>
> RequestLogger throws an NPE at line 200 because the field 'active' is never assigned a value when the class is instantiated.  In older versions (I am migrating from 1.3.3) this field was just a native int so the value would default to 0, but sometime between 1.3.3 and 1.4m2 it has changed to an AtomicInteger and never assigned a value via new AtomicInteger() or new AtomicInteger(someInt).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.