i did just checkin a fix that moves the run and complete messages to trace level. however i could not reproduce the ERROR message. do you know what line of code produces it? or what the full message looks like in log?
-igor On 8/26/07, Korbinian Bachl <[EMAIL PROTECTED]> wrote: > > Hi, > > im not 100% sure, but it sounds familiar. You might want to check out > todays Beta3 of 1.3.0 where this should be fixed (according to Martijn). > > Best Regards, > > Korbinian > > Steve Hiller schrieb: > > I am attempting to upgrade from 1.2.6 to wicket-1.3.0-beta2. I keep > getting > > the following message > > in my log: > > > > [8/24/07 12:21:05:226 EDT] 702c702c SystemOut O DEBUG <2007-08-24 > > 12:21:05,226> [ModificationWatcher Task] - Run the job: > > [EMAIL PROTECTED] > > > > Is this similar to what you reported here? > > > > Thanks! > > > > > > > > > > > > Korbinian Bachl wrote: > >> Hi, > >> > >> i've noticed that in 1.3.0 you get repeatedly > >> > >> 13864 [ModificationWatcher Task] ERROR > >> org.apache.wicket.util.resource.UrlResourceStream 's > >> > >> wich really pollutes the logfiles. Im using the 1.3.0 Snapshot Daily > >> from 19th August, and get every second at leas one of these errors in > >> the logs... wich makes them hard to read, the logging is done by log4j, > >> properties: > >> > >> log4j.rootLogger=INFO, A1 > >> log4j.appender.A1=org.apache.log4j.ConsoleAppender > >> > >> log4j.appender.A1.layout=org.apache.log4j.PatternLayout > >> log4j.appender.A1.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n > >> > >> > >> > >> Best Regards, > >> > >> Korbinian > >> > >> > >> > > >
