You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Dmitriy Vsekhvalnov <dv...@gmail.com> on 2013/04/10 12:51:47 UTC
What does it mean? java.lang.IllegalStateException: Page was stored
into the page pool in a dirty state.
We started to get exceptions in production like this:
java.lang.IllegalStateException: Page Page[report/Info en] was stored into
the page pool in a dirty state. This should never happen, and may indicate
that a reference to the page (or component within the page) was retained
past the end of a request.
What does it mean?
Re: What does it mean? java.lang.IllegalStateException: Page was
stored into the page pool in a dirty state.
Posted by Dmitriy Vsekhvalnov <dv...@gmail.com>.
well, no can't confirm it. Page class is not used anywhere according to
IDE.
All services and model are in separate jar, do not have dependencies on T5
at pom level. So, it's unlikely.
May be it is related to heavy load? Can't observe it in dev/test env.
On Wed, Apr 10, 2013 at 4:40 PM, Thiago H de Paula Figueiredo <
thiagohp@gmail.com> wrote:
> On Wed, 10 Apr 2013 07:51:47 -0300, Dmitriy Vsekhvalnov <
> dvsekhvalnov@gmail.com> wrote:
>
> We started to get exceptions in production like this:
>>
>> java.lang.**IllegalStateException: Page Page[report/Info en] was stored
>> into the page pool in a dirty state. This should never happen, and may
>> indicate that a reference to the page (or component within the page) was
>> retained
>> past the end of a request.
>>
>
> You probably passed a page or component instance as a parameter to a
> method belonging to a class which isn't a page, component or mixin and kept
> a reference (aka variable) pointing to it, and that's something you
> shouldn't do. Please check your code and tell us whether I got it right.
>
> About 5.3: yeah, released many years after 5.1.0.8 was, so it's more
> stable, has less bugs, performs better and uses less memory. But Tapestry
> 5.1.0.x was never unstable.
>
> --
> Thiago H. de Paula Figueiredo
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.org<us...@tapestry.apache.org>
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: What does it mean? java.lang.IllegalStateException: Page was
stored into the page pool in a dirty state.
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Wed, 10 Apr 2013 07:51:47 -0300, Dmitriy Vsekhvalnov
<dv...@gmail.com> wrote:
> We started to get exceptions in production like this:
>
> java.lang.IllegalStateException: Page Page[report/Info en] was stored
> into the page pool in a dirty state. This should never happen, and may
> indicate that a reference to the page (or component within the page) was
> retained
> past the end of a request.
You probably passed a page or component instance as a parameter to a
method belonging to a class which isn't a page, component or mixin and
kept a reference (aka variable) pointing to it, and that's something you
shouldn't do. Please check your code and tell us whether I got it right.
About 5.3: yeah, released many years after 5.1.0.8 was, so it's more
stable, has less bugs, performs better and uses less memory. But Tapestry
5.1.0.x was never unstable.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: What does it mean? java.lang.IllegalStateException: Page was
stored into the page pool in a dirty state.
Posted by Dmitriy Vsekhvalnov <dv...@gmail.com>.
well, i'd like to hear from someone that 5.3 or whatever is more stable,
before taking any steps to upgrade.
On Wed, Apr 10, 2013 at 3:31 PM, Muhammad Gelbana <m....@gmail.com>wrote:
> If there is a chance to use a newer version, please do. Page pooling isn't
> enabled by default anymore in newer versions.
> Sorry I don't think I can help much but hopefully this page could:
> http://tapestry.apache.org/page-life-cycle.html. Or probably someone else
> can.
>
>
> On Wed, Apr 10, 2013 at 1:26 PM, Dmitriy Vsekhvalnov <
> dvsekhvalnov@gmail.com
> > wrote:
>
> > 5.1.0.8-SNAPSHOT
> >
> > No other version in classpath for sure.
> >
> > On Wed, Apr 10, 2013 at 3:21 PM, Muhammad Gelbana <m.gelbana@gmail.com
> > >wrote:
> >
> > > What tapestry version are you using ? Also please make sure only this
> > > version is in your classpath so there is no conflict between different
> > > version or something
> > >
> > >
> > > On Wed, Apr 10, 2013 at 12:51 PM, Dmitriy Vsekhvalnov <
> > > dvsekhvalnov@gmail.com> wrote:
> > >
> > > > We started to get exceptions in production like this:
> > > >
> > > > java.lang.IllegalStateException: Page Page[report/Info en] was stored
> > > into
> > > > the page pool in a dirty state. This should never happen, and may
> > > indicate
> > > > that a reference to the page (or component within the page) was
> > retained
> > > > past the end of a request.
> > > >
> > > >
> > > > What does it mean?
> > > >
> > >
> >
>
Re: What does it mean? java.lang.IllegalStateException: Page was
stored into the page pool in a dirty state.
Posted by Muhammad Gelbana <m....@gmail.com>.
If there is a chance to use a newer version, please do. Page pooling isn't
enabled by default anymore in newer versions.
Sorry I don't think I can help much but hopefully this page could:
http://tapestry.apache.org/page-life-cycle.html. Or probably someone else
can.
On Wed, Apr 10, 2013 at 1:26 PM, Dmitriy Vsekhvalnov <dvsekhvalnov@gmail.com
> wrote:
> 5.1.0.8-SNAPSHOT
>
> No other version in classpath for sure.
>
> On Wed, Apr 10, 2013 at 3:21 PM, Muhammad Gelbana <m.gelbana@gmail.com
> >wrote:
>
> > What tapestry version are you using ? Also please make sure only this
> > version is in your classpath so there is no conflict between different
> > version or something
> >
> >
> > On Wed, Apr 10, 2013 at 12:51 PM, Dmitriy Vsekhvalnov <
> > dvsekhvalnov@gmail.com> wrote:
> >
> > > We started to get exceptions in production like this:
> > >
> > > java.lang.IllegalStateException: Page Page[report/Info en] was stored
> > into
> > > the page pool in a dirty state. This should never happen, and may
> > indicate
> > > that a reference to the page (or component within the page) was
> retained
> > > past the end of a request.
> > >
> > >
> > > What does it mean?
> > >
> >
>
Re: What does it mean? java.lang.IllegalStateException: Page was
stored into the page pool in a dirty state.
Posted by Dmitriy Vsekhvalnov <dv...@gmail.com>.
5.1.0.8-SNAPSHOT
No other version in classpath for sure.
On Wed, Apr 10, 2013 at 3:21 PM, Muhammad Gelbana <m....@gmail.com>wrote:
> What tapestry version are you using ? Also please make sure only this
> version is in your classpath so there is no conflict between different
> version or something
>
>
> On Wed, Apr 10, 2013 at 12:51 PM, Dmitriy Vsekhvalnov <
> dvsekhvalnov@gmail.com> wrote:
>
> > We started to get exceptions in production like this:
> >
> > java.lang.IllegalStateException: Page Page[report/Info en] was stored
> into
> > the page pool in a dirty state. This should never happen, and may
> indicate
> > that a reference to the page (or component within the page) was retained
> > past the end of a request.
> >
> >
> > What does it mean?
> >
>
Re: What does it mean? java.lang.IllegalStateException: Page was
stored into the page pool in a dirty state.
Posted by Muhammad Gelbana <m....@gmail.com>.
What tapestry version are you using ? Also please make sure only this
version is in your classpath so there is no conflict between different
version or something
On Wed, Apr 10, 2013 at 12:51 PM, Dmitriy Vsekhvalnov <
dvsekhvalnov@gmail.com> wrote:
> We started to get exceptions in production like this:
>
> java.lang.IllegalStateException: Page Page[report/Info en] was stored into
> the page pool in a dirty state. This should never happen, and may indicate
> that a reference to the page (or component within the page) was retained
> past the end of a request.
>
>
> What does it mean?
>