JVM heap- OutOfMemoryError: unable to create new native thread

Hello,

We having issue with JVM heap size where we are getting error as "OutOfMemoryError: unable to create new native thread” in servletd_out.log and we got frequent Teamsite UI down due to this.

Currently JVM setting under windows registry as : -Xms128m – Xmx256 -XXermSize64m , we need to confirm what setting need to be required to setup for JVM to avoid the out of memory issue.

servletd key : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iwservletd\Parameters

System Details :

Server - Windows

TeamSite - TS 6.7.2 SP2

System Type : 32-Bit operating system

Available memory (RAM) : 12 GB

Please help. Thank you.

Find more posts tagged with

Comments

Adam Stoller

Is that 12GB RAM "available" or "free"?

What else is running on the server?

Have you looked through the process stats on the Task Manager to see what process(es) are using the most memory?

Maximus_V

Thanks Ghoti for checking on it.

Server have 12GB available memory also server running OpenDeploy and Reporting as well.

iwserver services utilising more memory. I can not see any other process which really eating up. Please refer attached screenshot for details.

Thank you.

Adam Stoller

Between iwserver and servletd - you're accounting for roughly 1 of 12 gb of RAM - so it is difficult to tell from what's been offered here what the source of your problem is.

Garth McMillan

I had the same issue and raised a ticket with support. They advised that the default parameters that shipped with TeamSite 7.4.1.1 we incorrect and that -Xss128k should be specified.

Eg.

Open the registry using regedit.exe and add an additional property (JVM Option Number 18) and alter the property (JVM Option Count) to 19 in the following key:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iwjbossd\Parameters]

“JVM Option Number 18”=REG_SZ:-Xss128k

“JVM Option Count”=REG_DWORD:19

Note: The number 18, in JVM Option Number 18, should be whatever the next available number is (18 in our installation). The JVM Option Count should be incremented (options are 0-indexed hence JVM Option Number 18 is the 19th option).

Maximus_V

Thanks Zaarin for your inputs. appricated!!

We have teamSite 6.7.2 , so do not have "iwjbossd" service.Does that mean we need to check with eventsubsytem? any thoughts?

Rick Poulin

Disregard Zaarin's comment, it doesn't apply until TS 7.1+.

Memory leaks are much harder to diagnose than implied so far in this thread, so I'll just help you bandaid the problem, per your original query. In 32-bit JVM, you can allocate up to 1.5GB of memory to the JVM, assuming you have plenty left over for the operating system. And then you can start it up at something more reasonable (512MB in the example below) so you're not constantly reallocating mem space.

-Xms512m -Xmx1536

Note that if you're on a 32bit OS, you might want to allocate somewhat less than that so you leave enough for other services on the box. Maybe try with a max of 768MB to start and see if that helps delay the issue for large enough intervals to satisfy the users/management.