The issue was solved after log4j was replaces with logback I can create PR with this change, is this OK?
On Fri, Jan 12, 2018 at 11:37 PM, Maxim Solodovnik <solomax...@gmail.com> wrote: > I can confirm "Reload" of "vanilla" quick-start application in Tomcat > caused memory leak (reported using "Find leak" button) > Same time this is fixed after removing log4j-*.jar from WEB-INF/lib > fixes this issue > > I'll check if this is reproducible using logback ... > > On Fri, Jan 12, 2018 at 10:09 PM, Maxim Solodovnik <solomax...@gmail.com> > wrote: >> According to [1] the behavior I'm observing is correct: "As of Maven >> Archetype Plugin 3.0.0 the archetype resolution has changed. It is not >> possible anymore to specify the repository via the commandline" >> >> @Andrea maybe you have custom settings.xml ? >> >> [1] >> https://maven.apache.org/archetype/maven-archetype-plugin/archetype-repository.html >> >> On Fri, Jan 12, 2018 at 9:59 PM, Maxim Solodovnik <solomax...@gmail.com> >> wrote: >>> Good to know, will try to investigate why it fail for me ... >>> >>> On Fri, Jan 12, 2018 at 9:40 PM, Andrea Del Bene <an.delb...@gmail.com> >>> wrote: >>>> I've tried to run the generate quickstart command after deleting the local >>>> repository as you suggested but I didn't have any problem :-/. >>>> >>>> >>>> >>>> On 12/01/2018 15:18, Maxim Solodovnik wrote: >>>>> >>>>> Hello All, >>>>> >>>>> According to >>>>> https://maven.apache.org/archetype/maven-archetype-plugin/generate-mojo.html >>>>> >>>>> -DarchetypeRepository=https://repository.apache.org/content/repositories/snapshots/ >>>>> is not valid attribute for archetype:generate >>>>> >>>>> This is why I'm getting >>>>> >>>>> The desired archetype does not exist >>>>> (org.apache.wicket:wicket-archetype-quickstart:8.0.0-SNAPSHOT) >>>>> >>>>> error after deleting ~/.m2/repository/org/apache/wicket >>>>> >>>>> Is it known issue? >>>>> >>>>> On Wed, Jan 10, 2018 at 8:27 PM, Sebastien <seb...@gmail.com> wrote: >>>>>> >>>>>> Hi Andrea, >>>>>> >>>>>> Actually, I still have the memory leak issue on my Tomcat server using >>>>>> the >>>>>> wicket-jquery-ui samples. I've to restart once a week... :( >>>>>> I thought it could come from the debug-bar so I've removed it, but the >>>>>> problem still persists and logs are not useful at this point (only that >>>>>> the >>>>>> server is dying...) >>>>>> I need to find a way to increase logs and/or investigate this deeper... >>>>>> >>>>>> I also wanted to deploy my wicket 7.x because it used to be very stable >>>>>> at >>>>>> that time, I will try this asap... >>>>>> >>>>>> Thanks, >>>>>> Sebastien. >>>>>> >>>>>> >>>>>> On Wed, Jan 10, 2018 at 11:29 AM, Andrea Del Bene <an.delb...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I've noticed that with a quickstart project and with a permanent >>>>>>> session, >>>>>>> with Tomcat I get the same behavior described here >>>>>>> https://issues.apache.org/jira/browse/WICKET-6046. >>>>>>> Is something we should worry about? >>>>>>> >>>>>>> Andrea. >>>>>>> >>>>> >>>>> >>>> >>> >>> >>> >>> -- >>> WBR >>> Maxim aka solomax >> >> >> >> -- >> WBR >> Maxim aka solomax > > > > -- > WBR > Maxim aka solomax -- WBR Maxim aka solomax
