starting LEA tomcat error

Hi,

I have installed Livelink Enterprise server LEA 10. I coud not log in withe Administration client as I have the failed error starting tomcat for Livelink . i don't have changed tomcat6 (JDK 1.6) parameter.

Could you please provide some help ? thanks

Thomas Bailleul

error :

java.lang.OutOfMemoryError: PermGen space

2012-08-29 17:47:18,492 ERROR [main] otx.SystemOut : com.opentext.ecm.services.kernel.j2ee.tomcat.TomcatServerLifecycleListener - Exception:
com.opentext.ecm.exceptions.ECMRuntimeException: Critical service (OtdsService) failed to start. Aborting startup! Required status is RUNNING, actual status is:INSTALLED<Wed Aug 29 17:47:18 CEST 2012|ub1odywsv1;node001> [{}]
   at com.opentext.ecm.services.kernel.RunlevelController.start(RunlevelController.java:181)
   at com.opentext.ecm.services.kernel.j2ee.tomcat.TomcatSpecifics.startRunlevelsAfterTomcat(TomcatSpecifics.java:145)
   at com.opentext.ecm.services.kernel.j2ee.tomcat.TomcatServerLifecycleListener.lifecycleEvent(TomcatServerLifecycleListener.java:92)
   at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
   at org.apache.catalina.core.StandardServer.start(StandardServer.java:759)
   at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
   at java.lang.reflect.Method.invoke(Unknown Source)
   at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
2012-08-29 17:48:05,921 WARN [CS-WorkerThread #25 QueueManager$QueueMetering] otx.smessage : com.opentext.ecm.services.smessage.SMessage - Error serializing object
java.lang.OutOfMemoryError: PermGen space
2012-08-29 17:48:05,922 ERROR [SMessage Receive Queue Popper 3] otx.SystemOut : com.opentext.ecm.components.logging.LoggerStream - Exception:
java.lang.NullPointerException
   at com.opentext.ecm.services.smessage.impl.SMessageServiceAbstractImpl.fireMessageReceived(SMessageServiceAbstractImpl.java:268)
   at com.opentext.ecm.services.smessage.impl.SMessageServiceAbstractImpl$ReceiveQueuePopper.run(SMessageServiceAbstractImpl.java:109)
   at java.lang.Thread.run(Unknown Source)
2012-08-29 17:48:05,922 ERROR [SMessage Send Queue Popper 0] otx.smessage : com.opentext.ecm.services.smessage.impl.SMessageServiceAbstractImpl$SendQueuePopper - Error sending managed message
java.lang.NullPointerException
   at com.opentext.ecm.services.smessage.impl.SMessageServiceAbstractImpl$SendQueuePopper.run(SMessageServiceAbstractImpl.java:143)
   at java.lang.Thread.run(Unknown Source)
2012-08-29 17:48:05,923 ERROR [SMessage Receive Queue Popper 3] otx.SystemOut : com.opentext.ecm.components.logging.LoggerStream - Exception in thread "SMessage Receive Queue Popper 3"    at com.opentext.ecm.services.smessage.impl.SMessageServiceAbstractImpl.fireMessageReceived(SMessageServiceAbstractImpl.java:268)

2012-08-29 17:48:08,527 WARN [Thread-5] otx.smessage : com.opentext.ecm.services.smessage.SMessage - Error serializing object
java.lang.OutOfMemoryError: PermGen space
2012-08-29 17:48:08,528 ERROR [SMessage Send Queue Popper 0] otx.smessage : com.opentext.ecm.services.smessage.impl.SMessageServiceAbstractImpl$SendQueuePopper - Error sending managed message
java.lang.NullPointerException
   at com.opentext.ecm.services.smessage.impl.SMessageServiceAbstractImpl$SendQueuePopper.run(SMessageServiceAbstractImpl.java:143)
   at java.lang.Thread.run(Unknown Source)
2012-08-29 17:48:08,528 ERROR [SMessage Receive Queue Popper 0] otx.SystemOut : com.opentext.ecm.components.logging.LoggerStream - Exception:
java.lang.NullPointerException
   at com.opentext.ecm.services.smessage.impl.SMessageServiceAbstractImpl.fireMessageReceived(SMessageServiceAbstractImpl.java:268)
   at com.opentext.ecm.services.smessage.impl.SMessageServiceAbstractImpl$ReceiveQueuePopper.run(SMessageServiceAbstractImpl.java:109)
   at java.lang.Thread.run(Unknown Source)
2012-08-29 17:48:08,528 ERROR [SMessage Receive Queue Popper 0] otx.SystemOut : com.opentext.ecm.components.logging.LoggerStream - Exception in thread "SMessage Receive Queue Popper 0"    at com.opentext.ecm.services.smessage.impl.SMessageServiceAbstractImpl.fireMessageReceived(SMessageServiceAbstractImpl.java:268)

2012-08-29 17:48:35,922 WARN [CS-WorkerThread #12 QueueManager$QueueMetering] otx.smessage : com.opentext.ecm.services.smessage.SMessage - Error serializing object
java.lang.OutOfMemoryError: PermGen space

rss.txt

Find more posts tagged with

Comments

Tural Salahov

Did you get any solution to this problem? If yes, please let me know. I am also facing same issue.

Evan_Bench

Hi, You've posted in the Portal forum (should be in the Content Server forum). But you can fix these kind of errors with tomcat by increasing MaxPermSize. Assuming sun JRE do something like this in your tomcatw.exe on the java tab in the parms field:

JAVA_OPTS

This will give you a good nursery and room to grow, then a nice perm space w/ room to grow (that won't get purged during gc).

Evan

Tural Salahov

Tried to increase maxpermsize. Did not help. Anything else that we can try?

Evan_Bench

yes, but not fun. When an app is using up perm space and adding more perm space doesn't help, then we need to look at why (memory leak, application code is not releasing objects, thread pool configuration, et al)..

1. Using a heap monitor tool (tomcat comes with a basic one) monitor the heap during startup and look at what objects are filling up perm space.

2. once you know what objects cause problem you can then do something about it.

Some example:

If you're seeing lots of classes filling up perm space you could enable class unloading (which would help during startup) and even turn on a basic gc sweep for generational space. But these could also cause performance problems!

It's weird when an app is trying to put more than 256m of objects in perm space. Just to check you could add a bit more memory to perm and see if you get same problem. I suspect you have some custom code that is for some reason generating alot of objects. Can you show me what other java arguments are being used? (perhaps someone has disable class gc?).

Or consider posting this in the Content Server forum where someone might have seen this before (I'm more of a portal/cms guy).

Tural Salahov

We fixed it. There was an issue with installer and it did not install the Directory Services component properly. We had to run the directory services setup from the master setup separately and install all the latest patches for RCS, DS and admin client.