Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
OD UI OutOfMemory?
CRB
hello,
OD 6.1 W2k3 SP1
i experienced an issue with Opendeploy UI couple times last week...
when i log in it says it throws an exception with java.OutOfMemory error... the first time it happend when i was watching large deployment and i was refresh the logs from OD admin UI, till i got to outofmemory error.
i had to reboot OD access service and OD admin UI service to get it back to nromal.
and today i tried to login in the morning and it justsays OutOfMemory so i had to reboot the OD admin services again..
is this a known issue for OD admin? has anybody experience this before?
i had this box running for 5 months and never experienced this issue till last week and this week!
Find more posts tagged with
Comments
Silix
Try increasing the amount of memory available for the Java process.
More info:
https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=49582
Quarterly Indicators.rptdesign
CRB
that might be one of the solutions... the article talks about teamsite servlt on solaris, but i am on opendeploy on windows. so i think i need to edit the value in the registery:
Local_machine>system>currentControlSet>services>iwodadmin>parameters>JVM option # 7
right now it is set to -Xmx256m so i might change it to -Xmx512m or 1024m
i will watch and verify how much memory it is using next time it throws that error, if it reachs 256mb then i will increase it, if it doesnt get close to that then it will be something else...
CRB
i also noticed that the process iwuiservletd.exe doesnt release memory... since i restarted the ODadmin UI services, the process is consuming memory as we are using it, but i was expecting the memory that it is holding to go down over night (when nobody is using it) but, it didnt release a single byte... is this known issue?
i say issue, because we will eventually have to restart services again if the users keep reading logs using the admin interface...
i know that i can increase the JVM -xmx to 1024 but there is no point, if i am still going to have to restart the service at one point.
how does anybody on here handle this?