Re: [6.0] CouldNotLockPageException

2013-01-28 Thread Pierre Goupil 
Sure things men. But I need to raise this timeout in dev mode since I want
to have the graphical result of my (Ajax) request after having browsed
through the code: when the browser throws an error, I have no way to know
if what I have seen in my debugger is correct or not.

Anyway: +1 for Application#usesDevelopmentMode()

Best regards,

Pierre


On Mon, Jan 28, 2013 at 5:01 PM, Paul Bors  wrote:

> Nice, thanks for that Martin.
>
> We've carried this webapp since early versions of wicket and we haven't yet
> upgraded older utility methods.
> Goes to shows how nicely some of the API carried forward in Wicket :)
>
> ~ Thank you,
>Paul Bors
>
> On Mon, Jan 28, 2013 at 10:57 AM, Martin Grigorov  >wrote:
>
> > I don't see a reason why this setting should be modified at all.
> > It is normal that while debugging it will take more time. This exception
> is
> > harmless while you debug another (a real) problem.
> >
> > I'd change the value of this setting only if I know that there are paths
> in
> > the code which need more time and there is no way to improve it.
> >
> > Additionally there is Application#usesDevelopmentMode(), so no need to
> > create your own method ;-)
> >
> >
> > On Mon, Jan 28, 2013 at 5:52 PM, Paul Bors  wrote:
> >
> > > Well I would recommend adding this in your Application class:
> > >
> > > @Override
> > > protected void init() {
> > > ...
> > > if(isDevelopmentMode()) {
> > > ...
> > > IRequestCycleSettings#**setTimeout();
> > > ...
> > > }
> > > ...
> > > }
> > >
> > > public boolean isDevelopmentMode() {
> > > return (getConfigurationType() ==
> > > RuntimeConfigurationType.DEVELOPMENT);
> > > }
> > >
> > > At least you won't have to change your code when going between
> deployment
> > > and development mode :)
> > >
> > > ~ Thank you,
> > > Paul Bors
> > > On Sun, Jan 27, 2013 at 8:13 AM, Pierre Goupil  > > >wrote:
> > >
> > > > As I said, it's only when using (Eclipse) debugger. When I go from
> > > methods
> > > > to breakpoints and back again, only one minute is a bit short.
> > > >
> > > > But with Sven's solution, I have what I need.
> > > >
> > > > Cheers, men!
> > > >
> > > > Pierre
> > > >
> > > >
> > > > On Sun, Jan 27, 2013 at 12:35 PM, Martin Grigorov <
> > mgrigo...@apache.org
> > > > >wrote:
> > > >
> > > > > Better find out why it takes that long and try to make the request
> > > > > processing faster.
> > > > >
> > > > >
> > > > > On Sat, Jan 26, 2013 at 9:21 PM, Pierre Goupil <
> > goupilpie...@gmail.com
> > > > > >wrote:
> > > > >
> > > > > > Thanks a lot, it works!
> > > > > >
> > > > > > Cheers,
> > > > > >
> > > > > > Pierre
> > > > > >
> > > > > >
> > > > > > On Sat, Jan 26, 2013 at 7:00 PM, Sven Meier 
> > wrote:
> > > > > >
> > > > > > > You can adjust IRequestCycleSettings#**setTimeout().
> > > > > > >
> > > > > > > Sven
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On 01/26/2013 06:03 PM, Pierre Goupil wrote:
> > > > > > >
> > > > > > >> Good afternoon,
> > > > > > >>
> > > > > > >> When debugging through my Wicket code, I often get this
> > exception:
> > > > > > >>
> > > > > > >> CouldNotLockPageException: Could not lock page 1. Attempt
> > lasted 1
> > > > > > minute
> > > > > > >>
> > > > > > >> Is there anything I can do to rise up this timeout, please?
> > > > > > >>
> > > > > > >> Regards,
> > > > > > >>
> > > > > > >> Pierre Goupil
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > >
> > >
> --**--**-
> > > > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<
> > > > > > users-unsubscr...@wicket.apache.org>
> > > > > > > For additional commands, e-mail: users-h...@wicket.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > "Parce que c'est la nuit qu'il est beau de croire à la lumière."
> > > > > >
> > > > > > Edmond Rostand
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Martin Grigorov
> > > > > jWeekend
> > > > > Training, Consulting, Development
> > > > > http://jWeekend.com 
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > "Parce que c'est la nuit qu'il est beau de croire à la lumière."
> > > >
> > > > Edmond Rostand
> > > >
> > >
> >
> >
> >
> > --
> > Martin Grigorov
> > jWeekend
> > Training, Consulting, Development
> > http://jWeekend.com 
> >
>



-- 
"Parce que c'est la nuit qu'il est beau de croire à la lumière."

Edmond Rostand

Re: [6.0] CouldNotLockPageException

2013-01-28 Thread Paul Bors 
Nice, thanks for that Martin.

We've carried this webapp since early versions of wicket and we haven't yet
upgraded older utility methods.
Goes to shows how nicely some of the API carried forward in Wicket :)

~ Thank you,
   Paul Bors

On Mon, Jan 28, 2013 at 10:57 AM, Martin Grigorov wrote:

> I don't see a reason why this setting should be modified at all.
> It is normal that while debugging it will take more time. This exception is
> harmless while you debug another (a real) problem.
>
> I'd change the value of this setting only if I know that there are paths in
> the code which need more time and there is no way to improve it.
>
> Additionally there is Application#usesDevelopmentMode(), so no need to
> create your own method ;-)
>
>
> On Mon, Jan 28, 2013 at 5:52 PM, Paul Bors  wrote:
>
> > Well I would recommend adding this in your Application class:
> >
> > @Override
> > protected void init() {
> > ...
> > if(isDevelopmentMode()) {
> > ...
> > IRequestCycleSettings#**setTimeout();
> > ...
> > }
> > ...
> > }
> >
> > public boolean isDevelopmentMode() {
> > return (getConfigurationType() ==
> > RuntimeConfigurationType.DEVELOPMENT);
> > }
> >
> > At least you won't have to change your code when going between deployment
> > and development mode :)
> >
> > ~ Thank you,
> > Paul Bors
> > On Sun, Jan 27, 2013 at 8:13 AM, Pierre Goupil  > >wrote:
> >
> > > As I said, it's only when using (Eclipse) debugger. When I go from
> > methods
> > > to breakpoints and back again, only one minute is a bit short.
> > >
> > > But with Sven's solution, I have what I need.
> > >
> > > Cheers, men!
> > >
> > > Pierre
> > >
> > >
> > > On Sun, Jan 27, 2013 at 12:35 PM, Martin Grigorov <
> mgrigo...@apache.org
> > > >wrote:
> > >
> > > > Better find out why it takes that long and try to make the request
> > > > processing faster.
> > > >
> > > >
> > > > On Sat, Jan 26, 2013 at 9:21 PM, Pierre Goupil <
> goupilpie...@gmail.com
> > > > >wrote:
> > > >
> > > > > Thanks a lot, it works!
> > > > >
> > > > > Cheers,
> > > > >
> > > > > Pierre
> > > > >
> > > > >
> > > > > On Sat, Jan 26, 2013 at 7:00 PM, Sven Meier 
> wrote:
> > > > >
> > > > > > You can adjust IRequestCycleSettings#**setTimeout().
> > > > > >
> > > > > > Sven
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 01/26/2013 06:03 PM, Pierre Goupil wrote:
> > > > > >
> > > > > >> Good afternoon,
> > > > > >>
> > > > > >> When debugging through my Wicket code, I often get this
> exception:
> > > > > >>
> > > > > >> CouldNotLockPageException: Could not lock page 1. Attempt
> lasted 1
> > > > > minute
> > > > > >>
> > > > > >> Is there anything I can do to rise up this timeout, please?
> > > > > >>
> > > > > >> Regards,
> > > > > >>
> > > > > >> Pierre Goupil
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >
> > > > > >
> > > >
> > --**--**-
> > > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<
> > > > > users-unsubscr...@wicket.apache.org>
> > > > > > For additional commands, e-mail: users-h...@wicket.apache.org
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > "Parce que c'est la nuit qu'il est beau de croire à la lumière."
> > > > >
> > > > > Edmond Rostand
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Martin Grigorov
> > > > jWeekend
> > > > Training, Consulting, Development
> > > > http://jWeekend.com 
> > > >
> > >
> > >
> > >
> > > --
> > > "Parce que c'est la nuit qu'il est beau de croire à la lumière."
> > >
> > > Edmond Rostand
> > >
> >
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com 
>

Re: [6.0] CouldNotLockPageException

2013-01-28 Thread Martin Grigorov 
I don't see a reason why this setting should be modified at all.
It is normal that while debugging it will take more time. This exception is
harmless while you debug another (a real) problem.

I'd change the value of this setting only if I know that there are paths in
the code which need more time and there is no way to improve it.

Additionally there is Application#usesDevelopmentMode(), so no need to
create your own method ;-)


On Mon, Jan 28, 2013 at 5:52 PM, Paul Bors  wrote:

> Well I would recommend adding this in your Application class:
>
> @Override
> protected void init() {
> ...
> if(isDevelopmentMode()) {
> ...
> IRequestCycleSettings#**setTimeout();
> ...
> }
> ...
> }
>
> public boolean isDevelopmentMode() {
> return (getConfigurationType() ==
> RuntimeConfigurationType.DEVELOPMENT);
> }
>
> At least you won't have to change your code when going between deployment
> and development mode :)
>
> ~ Thank you,
> Paul Bors
> On Sun, Jan 27, 2013 at 8:13 AM, Pierre Goupil  >wrote:
>
> > As I said, it's only when using (Eclipse) debugger. When I go from
> methods
> > to breakpoints and back again, only one minute is a bit short.
> >
> > But with Sven's solution, I have what I need.
> >
> > Cheers, men!
> >
> > Pierre
> >
> >
> > On Sun, Jan 27, 2013 at 12:35 PM, Martin Grigorov  > >wrote:
> >
> > > Better find out why it takes that long and try to make the request
> > > processing faster.
> > >
> > >
> > > On Sat, Jan 26, 2013 at 9:21 PM, Pierre Goupil  > > >wrote:
> > >
> > > > Thanks a lot, it works!
> > > >
> > > > Cheers,
> > > >
> > > > Pierre
> > > >
> > > >
> > > > On Sat, Jan 26, 2013 at 7:00 PM, Sven Meier  wrote:
> > > >
> > > > > You can adjust IRequestCycleSettings#**setTimeout().
> > > > >
> > > > > Sven
> > > > >
> > > > >
> > > > >
> > > > > On 01/26/2013 06:03 PM, Pierre Goupil wrote:
> > > > >
> > > > >> Good afternoon,
> > > > >>
> > > > >> When debugging through my Wicket code, I often get this exception:
> > > > >>
> > > > >> CouldNotLockPageException: Could not lock page 1. Attempt lasted 1
> > > > minute
> > > > >>
> > > > >> Is there anything I can do to rise up this timeout, please?
> > > > >>
> > > > >> Regards,
> > > > >>
> > > > >> Pierre Goupil
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >
> > > > >
> > >
> --**--**-
> > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<
> > > > users-unsubscr...@wicket.apache.org>
> > > > > For additional commands, e-mail: users-h...@wicket.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > "Parce que c'est la nuit qu'il est beau de croire à la lumière."
> > > >
> > > > Edmond Rostand
> > > >
> > >
> > >
> > >
> > > --
> > > Martin Grigorov
> > > jWeekend
> > > Training, Consulting, Development
> > > http://jWeekend.com 
> > >
> >
> >
> >
> > --
> > "Parce que c'est la nuit qu'il est beau de croire à la lumière."
> >
> > Edmond Rostand
> >
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

Re: [6.0] CouldNotLockPageException

2013-01-28 Thread Paul Bors 
Well I would recommend adding this in your Application class:

@Override
protected void init() {
...
if(isDevelopmentMode()) {
...
IRequestCycleSettings#**setTimeout();
...
}
...
}

public boolean isDevelopmentMode() {
return (getConfigurationType() == RuntimeConfigurationType.DEVELOPMENT);
}

At least you won't have to change your code when going between deployment
and development mode :)

~ Thank you,
Paul Bors
On Sun, Jan 27, 2013 at 8:13 AM, Pierre Goupil wrote:

> As I said, it's only when using (Eclipse) debugger. When I go from methods
> to breakpoints and back again, only one minute is a bit short.
>
> But with Sven's solution, I have what I need.
>
> Cheers, men!
>
> Pierre
>
>
> On Sun, Jan 27, 2013 at 12:35 PM, Martin Grigorov  >wrote:
>
> > Better find out why it takes that long and try to make the request
> > processing faster.
> >
> >
> > On Sat, Jan 26, 2013 at 9:21 PM, Pierre Goupil  > >wrote:
> >
> > > Thanks a lot, it works!
> > >
> > > Cheers,
> > >
> > > Pierre
> > >
> > >
> > > On Sat, Jan 26, 2013 at 7:00 PM, Sven Meier  wrote:
> > >
> > > > You can adjust IRequestCycleSettings#**setTimeout().
> > > >
> > > > Sven
> > > >
> > > >
> > > >
> > > > On 01/26/2013 06:03 PM, Pierre Goupil wrote:
> > > >
> > > >> Good afternoon,
> > > >>
> > > >> When debugging through my Wicket code, I often get this exception:
> > > >>
> > > >> CouldNotLockPageException: Could not lock page 1. Attempt lasted 1
> > > minute
> > > >>
> > > >> Is there anything I can do to rise up this timeout, please?
> > > >>
> > > >> Regards,
> > > >>
> > > >> Pierre Goupil
> > > >>
> > > >>
> > > >>
> > > >>
> > > >
> > > >
> > --**--**-
> > > > To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<
> > > users-unsubscr...@wicket.apache.org>
> > > > For additional commands, e-mail: users-h...@wicket.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > "Parce que c'est la nuit qu'il est beau de croire à la lumière."
> > >
> > > Edmond Rostand
> > >
> >
> >
> >
> > --
> > Martin Grigorov
> > jWeekend
> > Training, Consulting, Development
> > http://jWeekend.com 
> >
>
>
>
> --
> "Parce que c'est la nuit qu'il est beau de croire à la lumière."
>
> Edmond Rostand
>

Re: [6.0] CouldNotLockPageException

2013-01-27 Thread Pierre Goupil 
As I said, it's only when using (Eclipse) debugger. When I go from methods
to breakpoints and back again, only one minute is a bit short.

But with Sven's solution, I have what I need.

Cheers, men!

Pierre


On Sun, Jan 27, 2013 at 12:35 PM, Martin Grigorov wrote:

> Better find out why it takes that long and try to make the request
> processing faster.
>
>
> On Sat, Jan 26, 2013 at 9:21 PM, Pierre Goupil  >wrote:
>
> > Thanks a lot, it works!
> >
> > Cheers,
> >
> > Pierre
> >
> >
> > On Sat, Jan 26, 2013 at 7:00 PM, Sven Meier  wrote:
> >
> > > You can adjust IRequestCycleSettings#**setTimeout().
> > >
> > > Sven
> > >
> > >
> > >
> > > On 01/26/2013 06:03 PM, Pierre Goupil wrote:
> > >
> > >> Good afternoon,
> > >>
> > >> When debugging through my Wicket code, I often get this exception:
> > >>
> > >> CouldNotLockPageException: Could not lock page 1. Attempt lasted 1
> > minute
> > >>
> > >> Is there anything I can do to rise up this timeout, please?
> > >>
> > >> Regards,
> > >>
> > >> Pierre Goupil
> > >>
> > >>
> > >>
> > >>
> > >
> > >
> --**--**-
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<
> > users-unsubscr...@wicket.apache.org>
> > > For additional commands, e-mail: users-h...@wicket.apache.org
> > >
> > >
> >
> >
> > --
> > "Parce que c'est la nuit qu'il est beau de croire à la lumière."
> >
> > Edmond Rostand
> >
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com 
>



-- 
"Parce que c'est la nuit qu'il est beau de croire à la lumière."

Edmond Rostand

Re: [6.0] CouldNotLockPageException

2013-01-27 Thread Martin Grigorov 
Better find out why it takes that long and try to make the request
processing faster.


On Sat, Jan 26, 2013 at 9:21 PM, Pierre Goupil wrote:

> Thanks a lot, it works!
>
> Cheers,
>
> Pierre
>
>
> On Sat, Jan 26, 2013 at 7:00 PM, Sven Meier  wrote:
>
> > You can adjust IRequestCycleSettings#**setTimeout().
> >
> > Sven
> >
> >
> >
> > On 01/26/2013 06:03 PM, Pierre Goupil wrote:
> >
> >> Good afternoon,
> >>
> >> When debugging through my Wicket code, I often get this exception:
> >>
> >> CouldNotLockPageException: Could not lock page 1. Attempt lasted 1
> minute
> >>
> >> Is there anything I can do to rise up this timeout, please?
> >>
> >> Regards,
> >>
> >> Pierre Goupil
> >>
> >>
> >>
> >>
> >
> > --**--**-
> > To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org<
> users-unsubscr...@wicket.apache.org>
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
>
>
> --
> "Parce que c'est la nuit qu'il est beau de croire à la lumière."
>
> Edmond Rostand
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

Re: [6.0] CouldNotLockPageException

2013-01-26 Thread Pierre Goupil 
Thanks a lot, it works!

Cheers,

Pierre


On Sat, Jan 26, 2013 at 7:00 PM, Sven Meier  wrote:

> You can adjust IRequestCycleSettings#**setTimeout().
>
> Sven
>
>
>
> On 01/26/2013 06:03 PM, Pierre Goupil wrote:
>
>> Good afternoon,
>>
>> When debugging through my Wicket code, I often get this exception:
>>
>> CouldNotLockPageException: Could not lock page 1. Attempt lasted 1 minute
>>
>> Is there anything I can do to rise up this timeout, please?
>>
>> Regards,
>>
>> Pierre Goupil
>>
>>
>>
>>
>
> --**--**-
> To unsubscribe, e-mail: 
> users-unsubscribe@wicket.**apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


-- 
"Parce que c'est la nuit qu'il est beau de croire à la lumière."

Edmond Rostand

Re: [6.0] CouldNotLockPageException

2013-01-26 Thread Sven Meier 

You can adjust IRequestCycleSettings#setTimeout().

Sven


On 01/26/2013 06:03 PM, Pierre Goupil wrote:

Good afternoon,

When debugging through my Wicket code, I often get this exception:

CouldNotLockPageException: Could not lock page 1. Attempt lasted 1 minute

Is there anything I can do to rise up this timeout, please?

Regards,

Pierre Goupil






-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

[6.0] CouldNotLockPageException

2013-01-26 Thread Pierre Goupil 
Good afternoon,

When debugging through my Wicket code, I often get this exception:

CouldNotLockPageException: Could not lock page 1. Attempt lasted 1 minute

Is there anything I can do to rise up this timeout, please?

Regards,

Pierre Goupil



-- 
"Parce que c'est la nuit qu'il est beau de croire à la lumière."

Edmond Rostand