You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Marcel Schepers <ma...@gmail.com> on 2008/01/30 19:47:35 UTC
scary error messages
Hello,
Tapestry (or more likely Javassist) generated scary error messages, such as
'compile error: no such class: $StampCatalogue_23'. StampCatalogue is an
abstract Tapestry page. In case these messages show up, Jetty has to be
restarted in order to restore from this chaos.
I am using Tapestry version 4.1.3 (from the Maven repository).
Any ideas what might cause this?
Marcel
Re: scary error messages
Posted by Jesse Kuhnert <jk...@gmail.com>.
Hmm...Javassist does have a couple static methods for things but I
hope that doesn't have anything to do with this.
For now, I would recommend trying out the new 3.6ga release of
javassist to see if that doesn't resolve the problem. I may try and
sneak that version in as a dependency for the 4.1.4 tapestry release.
On Thu, Jan 31, 2008 at 2:54 PM, Marcel Schepers
<ma...@gmail.com> wrote:
> well, yes and no.
>
> Both Tapestry applications are deployed in a separate war file and they both
> contain javaassist version 3.4.GA. The Spring Web Services application is
> also deployed in a separate war file containing version 3.3. So yes, Jetty
> has loaded different versions of javassist. And no, these versions are not
> loaded in the same context.
>
> Marcel
>
>
>
> On Jan 31, 2008 6:55 PM, Jesse Kuhnert <jk...@gmail.com> wrote:
>
> > Thanks for the in depth analysis. The EntityManager requiring
> > javassist does provide some hope.
> >
> > Just to confirm things - is your app running with both javassist 3.3
> > and 3.4 on the classpath?
> >
> > On Thu, Jan 31, 2008 at 11:21 AM, Marcel Schepers
> > <ma...@gmail.com> wrote:
> > > The problem occured on a dedicated production server, it never ever
> > occured
> > > on a development server.
> > >
> > > The server runs 4 websites: a "normal" customer website, two
> > redirection
> > > websites whose only goal is to redirected the user to the normal
> > website and
> > > a webservices website. All these websites are part of one Maven
> > project,
> > > divided into 5 submodules.
> > > - a core module providing generic application services as well as data
> > > related services
> > > - a core-web module providing the normal customer website
> > > - a core-redirect module consisting of only one single JSP page for
> > > redirection
> > > - a catalogue-web module consisting of one single Tapestry page (just
> > to
> > > show a difference frontpage) and some custom redirect logic
> > > - and, a ws module providing Spring Web Services based web services.
> > These
> > > webservice are primarily used with a custom Flex application.
> > >
> > > The core module has a Maven dependency to Hibernate Entitymanager
> > (version
> > > 3.3.1.javafabric, a custom made pom consisting of Hibernate 3.2.5.GA,
> > > Hibernate Annotations 3.3.0 and Hibernate Entitymanager 3.3.1). And
> > there is
> > > also a Maven dependency to Spring (version 2.0.7).
> > >
> > > All webapplications, excluding the single page JSP redirection, have
> > > dependency on this core module.
> > >
> > > I am using Tapestry 4.1.3 for the two Tapestry submodules.
> > >
> > > Hibernate Entitymanager (or some of its submodules) has a dependency on
> > > Javassist version 3.3, Tapestry Project 4.1.3 has a dependency on
> > Javassist
> > > 3.4.GA.
> > >
> > > All webapplications are deployed using (in Jetty terms) WebAppContext.
> > (I am
> > > deploying 4 ROOT.war files in 4 difference directories).
> > >
> > > The server was under a heavy load when the problem occured. If my
> > memory
> > > serves me well, I think the CPU had zero idle time and the general
> > server
> > > load was about 4. All these numbers come from the 'top' util.
> > >
> > > This morning I checked the server log, generated by AWStats. During the
> > > evening hours the server had about 3GB data traffic per hour. Perhaps
> > it is
> > > possible that the server was not able to handle such load. On the other
> > > hand, 3GB per hour is about 1MB per second. That isn't that much, is
> > it? (My
> > > main expertise is Java. I am able to deal with basic Linux
> > administration,
> > > but I am unable to determine if such a load is exceptional high.)
> > >
> > > Last but not least, some deployment settings. I am using Jetty version
> > > 6.1.5along with Java
> > > 1.5.0_14-b03 on a Linux Fedora Core 6 (linux kernel 2.6.22.7) server.
> > The
> > > server has 2GB RAM and Jetty is started with '-Xms512M -Xmx768M'.
> > Alongside
> > > with Jetty, PostgreSQL (8.1.9) is used as RDBMS.
> > >
> > > As said before, the problem never occured on a development server. My
> > first
> > > thought when it happened was pure panic, my second thought this morning
> > > wanders about a serious server overload. I've googled already who to
> > handle
> > > a Jetty server overload, but did not find anything. I will continue to
> > > google for a while and if nothing comes up, I will contact WebTide on
> > this
> > > issue.
> > >
> > > Thank you for your time!
> > >
> > > Marcel
> > >
> >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry / OGNL / Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
>
>
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
--
Jesse Kuhnert
Tapestry / OGNL / Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: scary error messages
Posted by Marcel Schepers <ma...@gmail.com>.
well, yes and no.
Both Tapestry applications are deployed in a separate war file and they both
contain javaassist version 3.4.GA. The Spring Web Services application is
also deployed in a separate war file containing version 3.3. So yes, Jetty
has loaded different versions of javassist. And no, these versions are not
loaded in the same context.
Marcel
On Jan 31, 2008 6:55 PM, Jesse Kuhnert <jk...@gmail.com> wrote:
> Thanks for the in depth analysis. The EntityManager requiring
> javassist does provide some hope.
>
> Just to confirm things - is your app running with both javassist 3.3
> and 3.4 on the classpath?
>
> On Thu, Jan 31, 2008 at 11:21 AM, Marcel Schepers
> <ma...@gmail.com> wrote:
> > The problem occured on a dedicated production server, it never ever
> occured
> > on a development server.
> >
> > The server runs 4 websites: a "normal" customer website, two
> redirection
> > websites whose only goal is to redirected the user to the normal
> website and
> > a webservices website. All these websites are part of one Maven
> project,
> > divided into 5 submodules.
> > - a core module providing generic application services as well as data
> > related services
> > - a core-web module providing the normal customer website
> > - a core-redirect module consisting of only one single JSP page for
> > redirection
> > - a catalogue-web module consisting of one single Tapestry page (just
> to
> > show a difference frontpage) and some custom redirect logic
> > - and, a ws module providing Spring Web Services based web services.
> These
> > webservice are primarily used with a custom Flex application.
> >
> > The core module has a Maven dependency to Hibernate Entitymanager
> (version
> > 3.3.1.javafabric, a custom made pom consisting of Hibernate 3.2.5.GA,
> > Hibernate Annotations 3.3.0 and Hibernate Entitymanager 3.3.1). And
> there is
> > also a Maven dependency to Spring (version 2.0.7).
> >
> > All webapplications, excluding the single page JSP redirection, have
> > dependency on this core module.
> >
> > I am using Tapestry 4.1.3 for the two Tapestry submodules.
> >
> > Hibernate Entitymanager (or some of its submodules) has a dependency on
> > Javassist version 3.3, Tapestry Project 4.1.3 has a dependency on
> Javassist
> > 3.4.GA.
> >
> > All webapplications are deployed using (in Jetty terms) WebAppContext.
> (I am
> > deploying 4 ROOT.war files in 4 difference directories).
> >
> > The server was under a heavy load when the problem occured. If my
> memory
> > serves me well, I think the CPU had zero idle time and the general
> server
> > load was about 4. All these numbers come from the 'top' util.
> >
> > This morning I checked the server log, generated by AWStats. During the
> > evening hours the server had about 3GB data traffic per hour. Perhaps
> it is
> > possible that the server was not able to handle such load. On the other
> > hand, 3GB per hour is about 1MB per second. That isn't that much, is
> it? (My
> > main expertise is Java. I am able to deal with basic Linux
> administration,
> > but I am unable to determine if such a load is exceptional high.)
> >
> > Last but not least, some deployment settings. I am using Jetty version
> > 6.1.5along with Java
> > 1.5.0_14-b03 on a Linux Fedora Core 6 (linux kernel 2.6.22.7) server.
> The
> > server has 2GB RAM and Jetty is started with '-Xms512M -Xmx768M'.
> Alongside
> > with Jetty, PostgreSQL (8.1.9) is used as RDBMS.
> >
> > As said before, the problem never occured on a development server. My
> first
> > thought when it happened was pure panic, my second thought this morning
> > wanders about a serious server overload. I've googled already who to
> handle
> > a Jetty server overload, but did not find anything. I will continue to
> > google for a while and if nothing comes up, I will contact WebTide on
> this
> > issue.
> >
> > Thank you for your time!
> >
> > Marcel
> >
>
>
>
> --
> Jesse Kuhnert
> Tapestry / OGNL / Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: scary error messages
Posted by Jesse Kuhnert <jk...@gmail.com>.
You may also want to try out whatever is in this new 3.6 javassist
release. Sounds like a bug in hibernate or javassist to me but it's
hard to tell for sure.
http://mirrors.ibiblio.org/pub/mirrors/maven2/jboss/javassist/3.6.ga/
On Thu, Jan 31, 2008 at 12:55 PM, Jesse Kuhnert <jk...@gmail.com> wrote:
> Thanks for the in depth analysis. The EntityManager requiring
> javassist does provide some hope.
>
> Just to confirm things - is your app running with both javassist 3.3
> and 3.4 on the classpath?
>
> On Thu, Jan 31, 2008 at 11:21 AM, Marcel Schepers
>
> <ma...@gmail.com> wrote:
>
>
> > The problem occured on a dedicated production server, it never ever occured
> > on a development server.
> >
> > The server runs 4 websites: a "normal" customer website, two redirection
> > websites whose only goal is to redirected the user to the normal website and
> > a webservices website. All these websites are part of one Maven project,
> > divided into 5 submodules.
> > - a core module providing generic application services as well as data
> > related services
> > - a core-web module providing the normal customer website
> > - a core-redirect module consisting of only one single JSP page for
> > redirection
> > - a catalogue-web module consisting of one single Tapestry page (just to
> > show a difference frontpage) and some custom redirect logic
> > - and, a ws module providing Spring Web Services based web services. These
> > webservice are primarily used with a custom Flex application.
> >
> > The core module has a Maven dependency to Hibernate Entitymanager (version
> > 3.3.1.javafabric, a custom made pom consisting of Hibernate 3.2.5.GA,
> > Hibernate Annotations 3.3.0 and Hibernate Entitymanager 3.3.1). And there is
> > also a Maven dependency to Spring (version 2.0.7).
> >
> > All webapplications, excluding the single page JSP redirection, have
> > dependency on this core module.
> >
> > I am using Tapestry 4.1.3 for the two Tapestry submodules.
> >
> > Hibernate Entitymanager (or some of its submodules) has a dependency on
> > Javassist version 3.3, Tapestry Project 4.1.3 has a dependency on Javassist
> > 3.4.GA.
> >
> > All webapplications are deployed using (in Jetty terms) WebAppContext. (I am
> > deploying 4 ROOT.war files in 4 difference directories).
> >
> > The server was under a heavy load when the problem occured. If my memory
> > serves me well, I think the CPU had zero idle time and the general server
> > load was about 4. All these numbers come from the 'top' util.
> >
> > This morning I checked the server log, generated by AWStats. During the
> > evening hours the server had about 3GB data traffic per hour. Perhaps it is
> > possible that the server was not able to handle such load. On the other
> > hand, 3GB per hour is about 1MB per second. That isn't that much, is it? (My
> > main expertise is Java. I am able to deal with basic Linux administration,
> > but I am unable to determine if such a load is exceptional high.)
> >
> > Last but not least, some deployment settings. I am using Jetty version
> > 6.1.5along with Java
> > 1.5.0_14-b03 on a Linux Fedora Core 6 (linux kernel 2.6.22.7) server. The
> > server has 2GB RAM and Jetty is started with '-Xms512M -Xmx768M'. Alongside
> > with Jetty, PostgreSQL (8.1.9) is used as RDBMS.
> >
> > As said before, the problem never occured on a development server. My first
> > thought when it happened was pure panic, my second thought this morning
> > wanders about a serious server overload. I've googled already who to handle
> > a Jetty server overload, but did not find anything. I will continue to
> > google for a while and if nothing comes up, I will contact WebTide on this
> > issue.
> >
> > Thank you for your time!
> >
> > Marcel
> >
>
>
>
> --
>
>
> Jesse Kuhnert
> Tapestry / OGNL / Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
--
Jesse Kuhnert
Tapestry / OGNL / Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: scary error messages
Posted by Jesse Kuhnert <jk...@gmail.com>.
Thanks for the in depth analysis. The EntityManager requiring
javassist does provide some hope.
Just to confirm things - is your app running with both javassist 3.3
and 3.4 on the classpath?
On Thu, Jan 31, 2008 at 11:21 AM, Marcel Schepers
<ma...@gmail.com> wrote:
> The problem occured on a dedicated production server, it never ever occured
> on a development server.
>
> The server runs 4 websites: a "normal" customer website, two redirection
> websites whose only goal is to redirected the user to the normal website and
> a webservices website. All these websites are part of one Maven project,
> divided into 5 submodules.
> - a core module providing generic application services as well as data
> related services
> - a core-web module providing the normal customer website
> - a core-redirect module consisting of only one single JSP page for
> redirection
> - a catalogue-web module consisting of one single Tapestry page (just to
> show a difference frontpage) and some custom redirect logic
> - and, a ws module providing Spring Web Services based web services. These
> webservice are primarily used with a custom Flex application.
>
> The core module has a Maven dependency to Hibernate Entitymanager (version
> 3.3.1.javafabric, a custom made pom consisting of Hibernate 3.2.5.GA,
> Hibernate Annotations 3.3.0 and Hibernate Entitymanager 3.3.1). And there is
> also a Maven dependency to Spring (version 2.0.7).
>
> All webapplications, excluding the single page JSP redirection, have
> dependency on this core module.
>
> I am using Tapestry 4.1.3 for the two Tapestry submodules.
>
> Hibernate Entitymanager (or some of its submodules) has a dependency on
> Javassist version 3.3, Tapestry Project 4.1.3 has a dependency on Javassist
> 3.4.GA.
>
> All webapplications are deployed using (in Jetty terms) WebAppContext. (I am
> deploying 4 ROOT.war files in 4 difference directories).
>
> The server was under a heavy load when the problem occured. If my memory
> serves me well, I think the CPU had zero idle time and the general server
> load was about 4. All these numbers come from the 'top' util.
>
> This morning I checked the server log, generated by AWStats. During the
> evening hours the server had about 3GB data traffic per hour. Perhaps it is
> possible that the server was not able to handle such load. On the other
> hand, 3GB per hour is about 1MB per second. That isn't that much, is it? (My
> main expertise is Java. I am able to deal with basic Linux administration,
> but I am unable to determine if such a load is exceptional high.)
>
> Last but not least, some deployment settings. I am using Jetty version
> 6.1.5along with Java
> 1.5.0_14-b03 on a Linux Fedora Core 6 (linux kernel 2.6.22.7) server. The
> server has 2GB RAM and Jetty is started with '-Xms512M -Xmx768M'. Alongside
> with Jetty, PostgreSQL (8.1.9) is used as RDBMS.
>
> As said before, the problem never occured on a development server. My first
> thought when it happened was pure panic, my second thought this morning
> wanders about a serious server overload. I've googled already who to handle
> a Jetty server overload, but did not find anything. I will continue to
> google for a while and if nothing comes up, I will contact WebTide on this
> issue.
>
> Thank you for your time!
>
> Marcel
>
--
Jesse Kuhnert
Tapestry / OGNL / Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: scary error messages
Posted by Marcel Schepers <ma...@gmail.com>.
The problem occured on a dedicated production server, it never ever occured
on a development server.
The server runs 4 websites: a "normal" customer website, two redirection
websites whose only goal is to redirected the user to the normal website and
a webservices website. All these websites are part of one Maven project,
divided into 5 submodules.
- a core module providing generic application services as well as data
related services
- a core-web module providing the normal customer website
- a core-redirect module consisting of only one single JSP page for
redirection
- a catalogue-web module consisting of one single Tapestry page (just to
show a difference frontpage) and some custom redirect logic
- and, a ws module providing Spring Web Services based web services. These
webservice are primarily used with a custom Flex application.
The core module has a Maven dependency to Hibernate Entitymanager (version
3.3.1.javafabric, a custom made pom consisting of Hibernate 3.2.5.GA,
Hibernate Annotations 3.3.0 and Hibernate Entitymanager 3.3.1). And there is
also a Maven dependency to Spring (version 2.0.7).
All webapplications, excluding the single page JSP redirection, have
dependency on this core module.
I am using Tapestry 4.1.3 for the two Tapestry submodules.
Hibernate Entitymanager (or some of its submodules) has a dependency on
Javassist version 3.3, Tapestry Project 4.1.3 has a dependency on Javassist
3.4.GA.
All webapplications are deployed using (in Jetty terms) WebAppContext. (I am
deploying 4 ROOT.war files in 4 difference directories).
The server was under a heavy load when the problem occured. If my memory
serves me well, I think the CPU had zero idle time and the general server
load was about 4. All these numbers come from the 'top' util.
This morning I checked the server log, generated by AWStats. During the
evening hours the server had about 3GB data traffic per hour. Perhaps it is
possible that the server was not able to handle such load. On the other
hand, 3GB per hour is about 1MB per second. That isn't that much, is it? (My
main expertise is Java. I am able to deal with basic Linux administration,
but I am unable to determine if such a load is exceptional high.)
Last but not least, some deployment settings. I am using Jetty version
6.1.5along with Java
1.5.0_14-b03 on a Linux Fedora Core 6 (linux kernel 2.6.22.7) server. The
server has 2GB RAM and Jetty is started with '-Xms512M -Xmx768M'. Alongside
with Jetty, PostgreSQL (8.1.9) is used as RDBMS.
As said before, the problem never occured on a development server. My first
thought when it happened was pure panic, my second thought this morning
wanders about a serious server overload. I've googled already who to handle
a Jetty server overload, but did not find anything. I will continue to
google for a while and if nothing comes up, I will contact WebTide on this
issue.
Thank you for your time!
Marcel
Re: scary error messages
Posted by Marcel Schepers <ma...@gmail.com>.
At this time I am not able to provide a detailed description of the setup.
However I can provide a fragment of the console/error log. I will provide
the details tomorrow.
Thanks for your kind words!
Marcel
On Jan 30, 2008 8:31 PM, Jesse Kuhnert <jk...@gmail.com> wrote:
> This has come up before but I've never been able to see it happen
> myself so am still in the dark as to the cause.
>
> Does anything happen in your app just before this error shows up?
> Has jetty re-deployed your context? Are you running with caching
> enabled or disabled? Are you running with something else that might
> use javassist, like jboss or similar?
>
> Any additional information you can provide would be greatly
> appreciated. I'd really like to find and fix whatever the problem is
> so it'll be given top priority if any additional info can be had.
>
> On Wed, Jan 30, 2008 at 1:47 PM, Marcel Schepers
> <ma...@gmail.com> wrote:
> > Hello,
> >
> > Tapestry (or more likely Javassist) generated scary error messages,
> such as
> > 'compile error: no such class: $StampCatalogue_23'. StampCatalogue is
> an
> > abstract Tapestry page. In case these messages show up, Jetty has to be
> > restarted in order to restore from this chaos.
> >
> > I am using Tapestry version 4.1.3 (from the Maven repository).
> >
> > Any ideas what might cause this?
> >
> > Marcel
> >
>
>
>
> --
> Jesse Kuhnert
> Tapestry / OGNL / Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: scary error messages
Posted by Jesse Kuhnert <jk...@gmail.com>.
This has come up before but I've never been able to see it happen
myself so am still in the dark as to the cause.
Does anything happen in your app just before this error shows up?
Has jetty re-deployed your context? Are you running with caching
enabled or disabled? Are you running with something else that might
use javassist, like jboss or similar?
Any additional information you can provide would be greatly
appreciated. I'd really like to find and fix whatever the problem is
so it'll be given top priority if any additional info can be had.
On Wed, Jan 30, 2008 at 1:47 PM, Marcel Schepers
<ma...@gmail.com> wrote:
> Hello,
>
> Tapestry (or more likely Javassist) generated scary error messages, such as
> 'compile error: no such class: $StampCatalogue_23'. StampCatalogue is an
> abstract Tapestry page. In case these messages show up, Jetty has to be
> restarted in order to restore from this chaos.
>
> I am using Tapestry version 4.1.3 (from the Maven repository).
>
> Any ideas what might cause this?
>
> Marcel
>
--
Jesse Kuhnert
Tapestry / OGNL / Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org