Java.lang.outofmemory error with OD 5.5.1

We are experiencing a java.lang.outofmemory error invoking iwodstart (we think) from an external task (.ipl). It is a cumulative error. If we restart TeamSite and OpenDeploy, we are fine for approximately 1 week. After that we are getting this error. Once we start getting it, all deploys consistently fail.

The error also follows the following error, which is a known bug:

/usr/iw-home/OpenDeployNG/jre/bin/java[17]: too many open files.

and then:

/usr/iw-home/OpenDeployNG/jre/bin/java[17]: too many open files
***ERROR - Starting deployment.
Details: Error occurred in server thread; nested exception is: java.lang.OutOfMemoryError

This is what led us to believe it is a cumulative error. We receive a million of the too many open files errors in our trace log and then eventually get the java.lang error.

Our installation is as follows:

Server: Solaris 8
Opendeploy: Version 5.5.1 Build 11146 SYM Interwoven 20020829
TeamSite: iwserver: 5.5.2 Build 10716 Interwoven 20020811

We've contacted Tech support and have not gotten resolution yet. I'd like to know if anyone else has experienced this error.

Thanks,

Paul Rowe
Sr. Engineer
Gartner

Find more posts tagged with

Comments

Migrateduser

Are you invoking iwodstart from a TeamSite workflow? If so, this issue has been discussed previously on this forum.

I believe a fix is coming in TeamSite 5.5.2 SP3. Also, OD 5.6 SP1 will include a new CLT that eliminates the overhead of a JRE per CLT invocation, which should mitigate the problem.

Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

shotze

Todd,
We are experiecing this error message in the iwod.log file. Running OD 5.6 SP1...what CLT are you referring to?

OD 5.6 SP1/SunOS 5.8

Identified OutOfMemoryErrors in the od.log...restarted OD Receiver process which eventually resolved the issue.

Questions:
1) Is there a tuning guide for OD (base and receiver)?
2) How would I increase the cache for the JVM on OD receiver?
3) On DevNet, there was a mention of a CLT for 5.6 SP1 CLT that eliminates the overhead of a JRE per CLT invocation, which should mitigate the problem. Where is it and what is the name of the tool?

Regards,
Yama Shalizi

yama.shalizi@usps.gov
703 292 3733

Edited by shotze on 06/30/04 02:45 PM (server time).

Migrateduser

Hi Yama,

1) No separate tuning guide. There is, however, the ability to modify the completion queue size (see initiatorProperties element’s completedQueueSize attribute). Also, disabling event reporting and configuring OD to use the legacy in-memory log format will decrease required memory.

2) I don't know of a supported procedure for doing that.

3) iwodcmd

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com