Also, if one int was changed to AtomicInteger, shouldn't the rest also? It's obviously a concurrency issue.
-- Jeremy Thomerson http://www.wickettraining.com On Thu, Jun 5, 2008 at 4:38 PM, Jeremy Thomerson <[EMAIL PROTECTED]> wrote: > If you enable the default request logger (in 1.4-*), it throws a > NullPointerException. > > The problem comes from this commit from Johan: > > http://fisheye6.atlassian.com/browse/wicket/trunk/wicket/src/main/java/org/apache/wicket/protocol/http/RequestLogger.java?r1=646020&r2=646810 > > The field "active" was changed from an int to an AtomicInteger. Just > changing that line to instantiate a new AtomicInteger should fix it. > > -- > Jeremy Thomerson > http://www.wickettraining.com
