Setting the Java thread stack size

[sascha_jaekel]

Hi experts,

I was just browsing thru a customers BI 4 landascape and I found out, that for some customized (copied) APS services the Java thread stack size isn't set to any value. Default APS shows -Xss1M, this value isn't set (even exists) on any copied APS.

Is that by design, or has this value to be set afterwards at all time?

cheers,

Sasha

[Former Member]

Hi Sascha,

Here's another note which might help: APS Sizing Guide

http://service.sap.com/sap/support/notes/1787088

Regards,

Sid

[sascha_jaekel]

thanks guys,

I'm familiar with customizing the APS.

as in the note obove stated, all manually entered parameters had to re-entered in the cloned APS.

Nevertheless, I'm just wondering why the default Java Stack Size parameter isn't also given in a copied APS.

[Former Member]

Dear Jaekel,

Please refer to this KBA "1792286 - General APS recommendations"

http://service.sap.com/sap/support/notes/1792286

I hope this help you.

Best and Kind Regards,

Ameni

[Former Member]

Hi Sascha,

Below doc might help which is for best practices for APS:

http://scn.sap.com/docs/DOC-31711

SAP note for reference:

1792285 - java.lang.OutOfMemoryError: unable to create new native thread when a high-volume publicat...

Regards,

aRun

[former_member142702]

Sascha,

Nice meeting you here 🙂

Cloning does not copy the command line at all. I guess thus is because the command line arguments contain a lot of info corresponding to the individual instance of the service (eg. Directories using partially the name of the instance). It would be too risky to clmne automatically the command line settings.

My observation is that during cloning the command line is set to contain some default settings derived from the type of the services included in the cloned server. Any custom settings like heap size should be applied again to the cloned instance.

Greetings from HH

Stratos