AW: [opencms-dev] excessive load and errormessage
Andreas Zahner
A.Zahner at alkacon.com
Wed Mar 26 14:07:56 CET 2003
Sven,
You have activated the static export of your pages. Using the method
getOriginalRequest() in the getContent() methods for your templates is
not possible for pages which should be exported. Every time OpenCms
tries to export such a page while publishing, the exception is thrown.
Change the export property for these pages to "dynamic" or "false" or
disable the static export feature in the opencms.properties.
Regards,
Andreas Zahner
Alkacon Software - The OpenCms Experts
http://www.alkacon.com
-----Ursprüngliche Nachricht-----
Von: owner-opencms-dev at www.opencms.org
[mailto:owner-opencms-dev at www.opencms.org] Im Auftrag von Sven Dittmar
Gesendet: Mittwoch, 26. März 2003 14:01
An: 'Opencms'
Betreff: [opencms-dev] excessive load and errormessage
Hi all,
we upgraded to RC2 yesterday, and now we have a massive load (> 6) on
the machine when we started publishing a project.
catalina.out shows this errormessage repeating every 3-10 seconds (maybe
according to the publishing of the pages):
java.lang.UnsupportedOperationException: Method getOriginalRequest not
supported in StaticExport.
at
com.opencms.core.CmsExportRequest.getOriginalRequest(CmsExportRequest.ja
va:88)
at
com.opencms.template.CmsXmlTemplate.getFrameQueryString(CmsXmlTemplate.j
ava:230)
at sun.reflect.GeneratedMethodAccessor519.invoke(Unknown
Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
com.opencms.template.cache.CmsMethodElement.getContent(CmsMethodElement.
java:148)
at
com.opencms.template.cache.A_CmsElement.resolveVariant(A_CmsElement.java
:553)
at
com.opencms.template.CmsXmlTemplate.startProcessing(CmsXmlTemplate.java:
1314)
at
com.opencms.template.CmsXmlTemplate.getContent(CmsXmlTemplate.java:164)
at
com.opencms.template.cache.CmsElementXml.getContent(CmsElementXml.java:1
71)
at
com.opencms.template.cache.A_CmsElement.resolveVariant(A_CmsElement.java
:467)
at
com.opencms.template.CmsXmlTemplate.startProcessing(CmsXmlTemplate.java:
1314)
at
com.opencms.template.CmsXmlTemplate.getContent(CmsXmlTemplate.java:164)
at
com.opencms.template.cache.CmsElementXml.getContent(CmsElementXml.java:1
71)
at
com.opencms.template.cache.CmsUri.callCanonicalRoot(CmsUri.java:185)
at
com.opencms.template.cache.CmsElementCache.callCanonicalRoot(CmsElementC
ache.java:149)
at
com.opencms.launcher.CmsXmlLauncher.generateOutput(CmsXmlLauncher.java:2
85)
at
com.opencms.launcher.CmsXmlLauncher.launch(CmsXmlLauncher.java:341)
at
com.opencms.launcher.A_CmsLauncher.initlaunch(A_CmsLauncher.java:275)
at
com.opencms.file.CmsStaticExport.exportLink(CmsStaticExport.java:731)
at
com.opencms.file.CmsStaticExport.<init>(CmsStaticExport.java:259)
at
com.opencms.file.genericSql.CmsResourceBroker.exportStaticResources(CmsR
esourceBroker.java:4652)
at
com.opencms.file.CmsObject.exportStaticResources(CmsObject.java:1551)
at
com.opencms.file.CmsObject.publishProject(CmsObject.java:2483)
at
com.opencms.workplace.CmsAdminPublishProjectThread.run(CmsAdminPublishPr
ojectThread.java:65
Any idea how to handle this without restarting the webapp in tomcat?
Our system:
JDK 1.4.1_01, MySQL 3.23.49-log, tomcat 4.1.12 on a 1GHz linuxbox and 1
GB RAM
Thanks!
Sven
More information about the opencms-dev
mailing list