plaubscher Respected Contributor.
Respected Contributor.
4463 views

Server memory is too low" error on GroupWise WebAccess 2014

We installed GroupWise 2014 SP2, on SLES 11SP3 with 12GB memory on a Virtual Machine, for our WebAccess. We are getting a "9520 - Server memory is too low" error on GroupWise WebAccess.We did edit the /etc/sysconfig/tomcat6 file as in the forum, see under-mentioned.We also created a restart tomcat script, to restart novell-tomcat6 automatically but this is not fixing the problem.

https://forums.novell.com/showthread.php/479218-9520-Server-Memory-is-too-low

What else can we do ?
Labels (1)
0 Likes
7 Replies
Knowledge Partner
Knowledge Partner

Re: Server memory is too low" error on GroupWise WebAccess 2014

In article <plaubscher.71vl5e@no-mx.forums.microfocus.com>, Plaubscher
wrote:
> We installed GroupWise 2014 SP2, on SLES 11SP3 with 12GB memory on a
> Virtual Machine, for our WebAccess. We are getting a "9520 - Server
> memory is too low" error on GroupWise WebAccess.We did edit the
> /etc/sysconfig/tomcat6 file as in the forum, see under-mentioned.We also
> created a restart tomcat script, to restart novell-tomcat6 automatically
> but this is not fixing the problem.


Lets start with reviewing the basics
What does "free -m" show? Does it show all 12GB? Are you using much of
swap? If you are using more than half then something is eating real
memory, use "top" to see what are the top users ("M" and "c" are helpful
toggles here)
In "top", how much memory is Tomcat using (this is where the "c" option
and a wide window helps as it is a java line with the tomcat call being
about 150+ characters over)

What errors are showing in the Tomcat/catalina logs?

What did you set Tomcat's memory to? And as per previous question is it
actually using that much?



Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
plaubscher Respected Contributor.
Respected Contributor.

Re: Server memory is too low" error on GroupWise WebAccess 2

I have gatthered the following information from the supportconfig that I run on the server.

1. Memory stats

# /usr/bin/vmstat 1 4
procs -----------memory---------- ---swap-- -----io---- -system-- -----cpu------
r b swpd free buff cache si so bi bo in cs us sy id wa st
6 0 624 1347992 1324972 5463060 0 0 1 89 5 5 12 1 87 0 0
0 0 624 1347736 1324972 5463092 0 0 0 0 2320 2421 19 2 79 0 0
1 0 624 1347876 1324972 5462964 0 0 0 0 2013 2254 24 1 75 0 0
1 0 624 1348256 1324972 5462488 0 0 0 12 2370 2415 38 1 61 0 0
Memory stats

#==[ Command ]======================================#
# /usr/bin/free -k
total used free shared buffers cached
Mem: 12199684 10850972 1348712 1116 1324972 5462488
-/+ buffers/cache: 4063512 8136172
Swap: 4192252 624 4191628

user PID PPID %CPU %MEM VSZ RSS TIME CMD
wwwrun 1103 1 43.9 6.3 989952 779644 SNl 01:37:18 /usr/lib64/jvm/jre-1.6.0-ibm/bin/java -Djava.library.path=/opt/novell/eDirectory/lib64

2. This is what I see in the tomcat.catalina log file

2. 1. web application [/gw] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.

2.2. Aug 20, 2015 6:45:45 AM
u04833393 - 08/12/2015, 22:15:55
java.lang.Throwable: [33025] Memory error. Memory function failure
at com.novell.webaccess.providers.soap.utils.SOAPUtils.dumpStack(SOAPUtils.java:2835)
at com.novell.webaccess.providers.soap.GWPortTypeFacade.xlatError(GWPortTypeFacade.java:182)
at com.novell.webaccess.providers.soap.GWPortTypeFacade.getSIDs(GWPortTypeFacade.java:863)
at com.novell.webaccess.providers.soap.GWPortTypeFacade.getSIDs(GWPortTypeFacade.java:803)
at com.novell.webaccess.providers.soap.GWPortTypeFacade.getContactSIDs(GWPortTypeFacade.java:780)
at com.novell.webaccess.providers.soap.GWPortTypeFacade.getContactSIDs(GWPortTypeFacade.java:768)
at com.novell.webaccess.providers.soap.actions.SOAPActionHandlerContacts.contactFind(SOAPActionHandlerContacts.

3. Tomcat's current memory is :

#CATALINA_OPTS=""
CATALINA_OPTS="-Xthr:minimizeUserCPU -Xms1024M -Xmx4096M"
0 Likes
Knowledge Partner
Knowledge Partner

Re: Server memory is too low" error on GroupWise WebAccess 2014

In article <plaubscher.71x9so@no-mx.forums.microfocus.com>, Plaubscher
wrote:
> user PID PPID %CPU %MEM VSZ RSS TIME CMD
> wwwrun 1103 1 43.9 6.3 989952 779644 SNl 01:37:18
> /usr/lib64/jvm/jre-1.6.0-ibm/bin/java
> -Djava.library.path=/opt/novell/eDirectory/lib64


do you have eDirectory running on this box?
That is certainly enough resource use to impact a box, perhaps some
basic eDir health checking there.

> CATALINA_OPTS="-Xthr:minimizeUserCPU -Xms1024M -Xmx4096M"

That looks like it might be the problem, that Xthr bit isn't in any of
the examples I've seen, try either
CATALINA_OPTS="-Xms1024M -Xmx4096M"
or
CATALINA_OPTS="-Xms2048M -Xmx4096M"


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
plaubscher Respected Contributor.
Respected Contributor.

Re: Server memory is too low" error on GroupWise WebAccess 2

Yes we do have eDirectory running on this Server.There is no problem with eDirectory.I did made the change in the CATALINA_OPTS="-Xms1024M -Xmx4096M" from to CATALINA_OPTS="-Xms2048M -Xmx4096M".It seems better now for this week.I am not getting the memory error anymore, but the WebAccess login page seems to be very slow now ( takes about 2 - 4 minutes to open the WebAccess login page ).Restarting tomcat solves this issue.This will occur 2 to 3 times a week.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Server memory is too low" error on GroupWise WebAccess 2014

In article <plaubscher.72hmnz@no-mx.forums.microfocus.com>, Plaubscher
wrote:
> to CATALINA_OPTS="-Xms2048M -Xmx4096M".It seems better
> now for this week.I am not getting the memory error anymore, but the
> WebAccess login page seems to be very slow now ( takes about 2 - 4
> minutes to open the WebAccess login page ).Restarting tomcat solves this
> issue.This will occur 2 to 3 times a week.


How much memory does tomcat appear to be using now as seen in top?
What do the catalina logs show now?
/var/opt/novell/tomcat6/logs/catalina.out


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
plaubscher Respected Contributor.
Respected Contributor.

Re: Server memory is too low" error on GroupWise WebAccess 2

I think we solved our problem.You need to read carefully the difference in paths for Tomcat6.See the following line in the following URL, https://www.novell.com/support/kb/doc.php?id=7010804.The default configuration file for tomcat6 is in the following path, /etc/sysconfig/tomcat6.We did the default change whithout any impact.And if you do an ps -eaf | grep java it does not show the -Xthr:minimizeUserCPU -Xms2048M -Xmx4096M change.

Read the next URL https://www.novell.com/support/kb/doc.php?id=7010804

NOTE: The config file to modify on OES11 is /etc/opt/novell/tomcat6/conf/novell-tomcat6.conf

Do an ps -eaf | grep java, and it now shows the -Xthr:minimizeUserCPU -Xms2048M -Xmx4096M change.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Server memory is too low" error on GroupWise WebAccess 2014

In article <plaubscher.72ouun@no-mx.forums.microfocus.com>, Plaubscher
wrote:
> I think we solved our problem.You need to read carefully the difference
> in paths for Tomcat6.


Ah yes, the whole 'Which tomcat are we using' issue.
So easy to forget to check that.
Glad you got it working and thank you for reporting back so we all learn,
and hopefully remember to check for the appropriate tomcat to work on.


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.