EP Portal and ADS needs to be restarted every couple of weeks for cluster

[Former Member]

Hello,

We have a (clustered) EP portal and stand alone Adobe Document Services environments and every couple of weeks we have to restart the entire cluster(s) for Portal and ADS to resolve J2EE engine confusion issues. They range from 500 server errors to shared and semaphore memory issues.

Does anyone else have these issues?

Do you have to restart your Portal and ADS instances to resolve issues?

Is it good practice to restart your Portal and ADS instances on a regular schedule? (maybe every two or three weeks)

Here is our environment:

EP Portal SPS14 (upgrading to 21 shortly)

Server1=Central and Database instance

Server2= Two dialog instances with 3 server nodes each

Server3= Two dialog instances with 3 server nodes each

Load balanced so the user only connect to the 4 dialog instances

Adobe Document Services SPS14 (upgrading to 21 shortly)

Server1= Central, Database and one dialog instance

Server2= Two dialog instances

We have found that if the instances are all left up and running for longer that three weeks we start to see different errors that range from 500 server errors to page not found errors to issues with shared and semaphore memory. We have followed the SAP best practices for J2EE engine settings for memory and garbage collecting and even consulted with Solaris to specifically tune our servers for SAP NetWeaver Portal and ADS but still find we need to restart every few weeks. Please let me know if anyone has these issues.

Thank you,

Jim Viette

[former_member191062 · Accepted solution]

Hello Jim,

The SPS14 contained an ADS that was newly released / initialy delivered with SP13 /. There have been a lot of improvements including stablity fixes since SP14. You will have all of these with the new SP.

Best regards,

Dezso

[Former Member · Accepted solution]

Hello,

We upgraded to SPS21 but we still have to restart it at least every two weeks. If we don't restart, we start to see 500 errors and slowness.

Thank you,

Jim Viette