Please let as know if the issue is still reproducible :)
On Fri, 26 Oct 2018 at 23:33, Rob Audenaerde
wrote:
> Will do, but after the weekend :D
>
> On Fri, Oct 26, 2018 at 5:58 PM Maxim Solodovnik
> wrote:
>
> > Hello Rob,
> >
> > The PR was merged, so you can verify the fix using
Will do, but after the weekend :D
On Fri, Oct 26, 2018 at 5:58 PM Maxim Solodovnik
wrote:
> Hello Rob,
>
> The PR was merged, so you can verify the fix using 8.2.0-SNAPSHOT (in ~30
> minutes or so ) :))
>
> On Wed, 24 Oct 2018 at 15:09, Maxim Solodovnik
> wrote:
>
> > BTW master branch of our
Hello Rob,
The PR was merged, so you can verify the fix using 8.2.0-SNAPSHOT (in ~30
minutes or so ) :))
On Wed, 24 Oct 2018 at 15:09, Maxim Solodovnik wrote:
> BTW master branch of our project is already uses wicket 8.2.0-SNAPSHOT
>
> On Wed, 24 Oct 2018 at 15:07, Maxim Solodovnik
> wrote:
>
BTW master branch of our project is already uses wicket 8.2.0-SNAPSHOT
On Wed, 24 Oct 2018 at 15:07, Maxim Solodovnik wrote:
> My steps were:
>
> 0) locate problem test (TestInstall in my case)
> 1) build updated wicket-core
> 2) Run problem test in a loop:
> reset && for i in `seq 0 200`; do
My steps were:
0) locate problem test (TestInstall in my case)
1) build updated wicket-core
2) Run problem test in a loop:
reset && for i in `seq 0 200`; do echo; echo; echo "--- ${i}
-"; echo; echo; echo; mvn clean test
-DgenerateReports=false -Dtest=TestInstall -o;
Thank you Maxim!
I'd gladly test this.
Is there an standard/easy (maven?) way to test this in my application?
-Rob
On Wed, Oct 24, 2018 at 9:52 AM Maxim Solodovnik
wrote:
> Here is the JIRA [1]
>
> I was able to reproduce this issue running one of our tests in a bash loop
> Original
Here is the JIRA [1]
I was able to reproduce this issue running one of our tests in a bash loop
Original 8.2.0-SNAPSHOT usually hang on <10th iteration
After this [1] fix, it flawlessly works 201 iterations
I would appreciate if you can review/test these changes
[1]
BTW: I currently worked around it by (very ugly) adding a
Thread.sleep(1000) between the last test-action in Wicket and the
Jetty-shutdown. So it seems a timing issue (which probably explains why
Maxim has been seeing Jenkins failing occasionally).
Thanks for checking into this!
-Rob
On Fri,
Is there a simple way to disable the AsynchronousDataStore (for now)?
On Fri, Oct 12, 2018 at 3:31 PM Maxim Solodovnik
wrote:
> I'm occasionally able to see this error on Apache Jenkins, but
> unfortunately there is no clear steps to reproduce
> I was unable to find what is wrong, will spend
I'm occasionally able to see this error on Apache Jenkins, but
unfortunately there is no clear steps to reproduce
I was unable to find what is wrong, will spend some more time on this next week
On Fri, 12 Oct 2018 at 17:20, Martin Grigorov wrote:
>
> Hi,
>
> When the application stops
Hi,
When the application stops Application#destroy() should call
AsynchronousDataStore#destroy() (
https://github.com/apache/wicket/blob/6ee5313d405fbbdd4ce9d9a03ccb526358834fca/wicket-core/src/main/java/org/apache/wicket/pageStore/AsynchronousDataStore.java#L101
)
There it will interrupt the
11 matches
Mail list logo
