Hi Ruben,
thank you for your answer. (In the second half the answer to Grégory
[Thank you, too!!!])
Am 14.07.2009 um 19:51 schrieb Ruben Reusser:
are you able to export the node to an xml file instead of activating
it? You can then (but not recommended I believe import the node on
the public side as a quick fix.
Doesn't work to. Another log-file snippet:
2009-07-15 11:17:56,465 ERROR
info.magnolia.cms.servlets.MVCServletHandlerImpl : can't call
command: exportxml
java.lang.OutOfMemoryError: Java heap space
at
java
.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:
99)
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:
575)
at java.lang.StringBuffer.append(StringBuffer.java:321)
at org.apache.xml.serialize.IndentPrinter.printText(Unknown Source)
at org.apache.xml.serialize.XMLSerializer.printXMLChar(Unknown Source)
at org.apache.xml.serialize.XMLSerializer.printText(Unknown Source)
at org.apache.xml.serialize.BaseMarkupSerializer.characters(Unknown
Source)
at org.xml.sax.helpers.XMLFilterImpl.characters(XMLFilterImpl.java:564)
at
info
.magnolia
.importexport
.filters.MetadataUuidFilter.characters(MetadataUuidFilter.java:89)
at org.apache.xerces.parsers.AbstractSAXParser.characters(Unknown
Source)
at
org
.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanContent(Unknown
Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl
$FragmentContentDispatcher.dispatch(Unknown Source)
at
org
.apache
.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333)
at
info
.magnolia
.importexport.DataTransporter.readFormatted(DataTransporter.java:506)
at
info
.magnolia
.importexport.DataTransporter.readFormatted(DataTransporter.java:482)
at
info
.magnolia
.importexport.DataTransporter.parseAndFormat(DataTransporter.java:464)
at
info
.magnolia
.importexport.DataTransporter.executeExport(DataTransporter.java:401)
at
info
.magnolia
.module.admininterface.pages.ExportPage.exportxml(ExportPage.java:268)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun
.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
39)
at
sun
.reflect
.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
info
.magnolia
.cms.servlets.MVCServletHandlerImpl.execute(MVCServletHandlerImpl.java:
123)
at
info
.magnolia
.cms
.servlets
.CommandBasedMVCServletHandler
.execute(CommandBasedMVCServletHandler.java:87)
at info.magnolia.cms.servlets.MVCServlet.doPost(MVCServlet.java:122)
at info.magnolia.cms.servlets.MVCServlet.doGet(MVCServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:627)
Also try to activate single nodes without the subnodes and see if
that helps :-)
Yes, I made this experience before. But this doesn't help in this
case, too. Sorry!
On another note:
tomcat suggests to create a setenv.bat or setenv.sh file in the
tomcat/bin folder and set your custom parameters there instead of
the magnolia_control.sh file (the setenv is recommended to handle
setting parameters in order to better run multiple instances of
tomcat on one server)
I will control it.
Grégory:
Hartmut: Again, just to make sure your parameters are correctly taken
into account:
* could check if you have a setenv(.sh) ? As Ruben suggests, it's
another approach to set the environment for Tomcat.. if you had such a
file, it could be interfering with the settings you made in
magnolia_control.sh
No, it is not. No setenv.sh in tomcat/bin and tomcat/conf
* what do you get if you do
echo $JAVA_OPTS
echo $CATALINA_OPTS
in your shell, *before* starting Magnolia ?
Sorry, nothing. Empty echo.
xserve07:~ admin$ echo $JAVA_OPTS
xserve07:~ admin$ echo $CATALINA_OPTS
-----
Hm, Hartmut
Ruben
Hartmut Kern wrote:
Hi Grégory,
yes, that's obvious. So, the context as I can see it:
I used magnolia_control.sh and changed the standard opts into mine.
Then I started tomcat with the shell-scriüpt: magnolia_control.sh.
(Downloaded and used the normal bundle with tomcat, installed it
in /usr/local/...)
Is there anything in the background I do not have contol of, if I
do as described?
Best
Hartmut
Am 14.07.2009 um 18:47 schrieb Grégory Joseph:
On Jul 14, 2009, at 6:40 PM, Hartmut Kern (It-Gruppe) wrote:
Hey Grégory,
not quite sure what you mean.
What I mean is that if the CATALINA_OPTS has an existing value,
of, say "-Xmx1M", there's a little chance your setting will
useless (I'm not sure how (in which) the jvm reads the command
line parameters)
If that's still not clear, all I mean is, supposing CATALINA_OPTS
has a value of "-Xmx 128M" before the line you pasted here, in
effect, your CATALINA_OPTS will be "-Xmx 128M -XX:MaxPermSize=256M
-Xms1024M -Xmx2048M -Djava.awt.headless=false -d64".
In short, your option line looks correct, but depending on the
context (where is it? is it taken into account at all?) it might
not necessarily do what you think it does.
... as I was saying, just trying to put the obvious mistakes
aside ;)
-g
But obvious I tried to test, what I had done. Increase the Opts,
when increasing the file size I tested.
MaxPermSize, Xmx, Xms tested beginning with the standards.
Increased Xmx first, let Xms follow. Increase file size, etc.
Thats, what you asked for as obvious?
Allways looked on the used Ram, and used harddisk I got as infos
from the monitor programm.
What I forgot: Version 4.0 Magnolia.
Best
Hartmut
Am 14.07.2009 um 17:58 schrieb Grégory Joseph:
On Jul 14, 2009, at 5:29 PM, Hartmut Kern (It-Gruppe) wrote:
My Catalina-Opts:
export CATALINA_OPTS="$CATALINA_OPTS -XX:MaxPermSize=256M -
Xms1024M -Xmx2048M -Djava.awt.headless=false -d64"
To put the obvious aside first: I suppose you've checked the
value of $CATALINA prior to this export line ?
-g
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-
cms.com>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
