Maximo List Archive

This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.

CPU Starvation Detected

From: Basant M Kumar (2015-04-06 15:05)

Do following:Increase JVM memory.Fine Tune JVM setting.Look at log for any error to find out what exactly is using so much memory or cpu time
Thanks, Basant M Kumar
From: "twabuko@yahoo.com [MAXIMO]" <MAXIMO@yahoogroups.com>
To: MAXIMO@yahoogroups.com
Sent: Saturday, April 4, 2015 6:59 PM
Subject: [MAXIMO List] CPU Starvation Detected

Has anyone encountered this issue ,

' Did not receive adequate CPU time slice. Last known CPU usage time at 08:08:24:629 EDT. Inactivity duration was 67 seconds.'

This happening every 2 hours

This been detected both on our PROD and DEV servers.
We recently upgraded from maximo71 to maximo75.This was not an issue in maxim71 using Weblogic Server

- 64 bit server running Windows server 2008
- Oracle 11g DB
- Maximo Asset Management 7505 IFXBLD023
- Websphere Server 70015
-12GB memory.
- 2 JVMs

Any help will be greatly appreciated

#yiv7892099115 #yiv7892099115 -- #yiv7892099115ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv7892099115 #yiv7892099115ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv7892099115 #yiv7892099115ygrp-mkp #yiv7892099115hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv7892099115 #yiv7892099115ygrp-mkp #yiv7892099115ads {margin-bottom:10px;}#yiv7892099115 #yiv7892099115ygrp-mkp .yiv7892099115ad {padding:0 0;}#yiv7892099115 #yiv7892099115ygrp-mkp .yiv7892099115ad p {margin:0;}#yiv7892099115 #yiv7892099115ygrp-mkp .yiv7892099115ad a {color:#0000ff;text-decoration:none;}#yiv7892099115 #yiv7892099115ygrp-sponsor #yiv7892099115ygrp-lc {font-family:Arial;}#yiv7892099115 #yiv7892099115ygrp-sponsor #yiv7892099115ygrp-lc #yiv7892099115hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv7892099115 #yiv7892099115ygrp-sponsor #yiv7892099115ygrp-lc .yiv7892099115ad {margin-bottom:10px;padding:0 0;}#yiv7892099115 #yiv7892099115actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv7892099115 #yiv7892099115activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv7892099115 #yiv7892099115activity span {font-weight:700;}#yiv7892099115 #yiv7892099115activity span:first-child {text-transform:uppercase;}#yiv7892099115 #yiv7892099115activity span a {color:#5085b6;text-decoration:none;}#yiv7892099115 #yiv7892099115activity span span {color:#ff7900;}#yiv7892099115 #yiv7892099115activity span .yiv7892099115underline {text-decoration:underline;}#yiv7892099115 .yiv7892099115attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv7892099115 .yiv7892099115attach div a {text-decoration:none;}#yiv7892099115 .yiv7892099115attach img {border:none;padding-right:5px;}#yiv7892099115 .yiv7892099115attach label {display:block;margin-bottom:5px;}#yiv7892099115 .yiv7892099115attach label a {text-decoration:none;}#yiv7892099115 blockquote {margin:0 0 0 4px;}#yiv7892099115 .yiv7892099115bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv7892099115 .yiv7892099115bold a {text-decoration:none;}#yiv7892099115 dd.yiv7892099115last p a {font-family:Verdana;font-weight:700;}#yiv7892099115 dd.yiv7892099115last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv7892099115 dd.yiv7892099115last p span.yiv7892099115yshortcuts {margin-right:0;}#yiv7892099115 div.yiv7892099115attach-table div div a {text-decoration:none;}#yiv7892099115 div.yiv7892099115attach-table {width:400px;}#yiv7892099115 div.yiv7892099115file-title a, #yiv7892099115 div.yiv7892099115file-title a:active, #yiv7892099115 div.yiv7892099115file-title a:hover, #yiv7892099115 div.yiv7892099115file-title a:visited {text-decoration:none;}#yiv7892099115 div.yiv7892099115photo-title a, #yiv7892099115 div.yiv7892099115photo-title a:active, #yiv7892099115 div.yiv7892099115photo-title a:hover, #yiv7892099115 div.yiv7892099115photo-title a:visited {text-decoration:none;}#yiv7892099115 div#yiv7892099115ygrp-mlmsg #yiv7892099115ygrp-msg p a span.yiv7892099115yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv7892099115 .yiv7892099115green {color:#628c2a;}#yiv7892099115 .yiv7892099115MsoNormal {margin:0 0 0 0;}#yiv7892099115 o {font-size:0;}#yiv7892099115 #yiv7892099115photos div {float:left;width:72px;}#yiv7892099115 #yiv7892099115photos div div {border:1px solid #666666;height:62px;overflow:hidden;width:62px;}#yiv7892099115 #yiv7892099115photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv7892099115 #yiv7892099115reco-category {font-size:77%;}#yiv7892099115 #yiv7892099115reco-desc {font-size:77%;}#yiv7892099115 .yiv7892099115replbq {margin:4px;}#yiv7892099115 #yiv7892099115ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv7892099115 #yiv7892099115ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv7892099115 #yiv7892099115ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv7892099115 #yiv7892099115ygrp-mlmsg select, #yiv7892099115 input, #yiv7892099115 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv7892099115 #yiv7892099115ygrp-mlmsg pre, #yiv7892099115 code {font:115% monospace;}#yiv7892099115 #yiv7892099115ygrp-mlmsg * {line-height:1.22em;}#yiv7892099115 #yiv7892099115ygrp-mlmsg #yiv7892099115logo {padding-bottom:10px;}#yiv7892099115 #yiv7892099115ygrp-msg p a {font-family:Verdana;}#yiv7892099115 #yiv7892099115ygrp-msg p#yiv7892099115attach-count span {color:#1E66AE;font-weight:700;}#yiv7892099115 #yiv7892099115ygrp-reco #yiv7892099115reco-head {color:#ff7900;font-weight:700;}#yiv7892099115 #yiv7892099115ygrp-reco {margin-bottom:20px;padding:0px;}#yiv7892099115 #yiv7892099115ygrp-sponsor #yiv7892099115ov li a {font-size:130%;text-decoration:none;}#yiv7892099115 #yiv7892099115ygrp-sponsor #yiv7892099115ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv7892099115 #yiv7892099115ygrp-sponsor #yiv7892099115ov ul {margin:0;padding:0 0 0 8px;}#yiv7892099115 #yiv7892099115ygrp-text {font-family:Georgia;}#yiv7892099115 #yiv7892099115ygrp-text p {margin:0 0 1em 0;}#yiv7892099115 #yiv7892099115ygrp-text tt {font-size:120%;}#yiv7892099115 #yiv7892099115ygrp-vital ul li:last-child {border-right:none !important;}#yiv7892099115

From: vijay kumar (2015-04-06 22:16)

Hi,
CPU starvation mainly due to heap memory issue. Can be caused due to
various reasons.
1. How many concurrent users are logged in during this period.?
2. What is the minimum and maximum heap memory allotted for each JVM.?
3. Is load balancing happening between these two JVM's.?
4. Is there any specific transactions users are trying out during this
period..?
Best starting point would be stderr and stdout logfile. We even faced this
issue during our implementation. Could help you fixing the issue.
Thanks and Regards,
On 5 April 2015 at 05:29, twabuko@yahoo.com [MAXIMO] <MAXIMO@yahoogroups.com
> wrote:
>
>
> Has anyone encountered this issue ,
>
>
> ' Did not receive adequate CPU time slice. Last known CPU usage time at
> 08:08:24:629 EDT. Inactivity duration was 67 seconds.'
>
>
> This happening every 2 hours
>
>
> This been detected both on our PROD and DEV servers.
> We recently upgraded from maximo71 to maximo75.This was not an issue in
> maxim71 using Weblogic Server
>
>
> - 64 bit server running Windows server 2008
> - Oracle 11g DB
> - Maximo Asset Management 7505 IFXBLD023
> - Websphere Server 70015
> -12GB memory.
> - 2 JVMs
>
>
> Any help will be greatly appreciated
>
>
>
>
>
>
--
Yours;
Vijay Kumar Giliyar

From: twabuko (2015-04-07 19:47)

Hi .. Thanks for response

1. How many concurrent users are logged in during this period.?

PROD has at least 20+ on each JVM
DEV 3 users or less ( Mostly developers) but issue still persists

2. What is the minimum and maximum heap memory allotted for each JVM.?

minimum - 4096
maximum - 4096

3. Is load balancing happening between these two JVM's.?

Load balancing has yet to be set up.

4. Is there any specific transactions users are trying out during this
period..?

No specific transactions users

---In MAXIMO@yahoogroups.com, <viji2kinna@...> wrote :
Hi,

CPU starvation mainly due to heap memory issue. Can be caused due to
various reasons.

1. How many concurrent users are logged in during this period.?
2. What is the minimum and maximum heap memory allotted for each JVM.?
3. Is load balancing happening between these two JVM's.?
4. Is there any specific transactions users are trying out during this
period..?

Best starting point would be stderr and stdout logfile. We even faced this
issue during our implementation. Could help you fixing the issue.

Thanks and Regards,

On 5 April 2015 at 05:29, twabuko@... mailto:twabuko@... [MAXIMO] <MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com
> wrote:

>
>
> Has anyone encountered this issue ,
>
>
> ' Did not receive adequate CPU time slice. Last known CPU usage time at
> 08:08:24:629 EDT. Inactivity duration was 67 seconds.'
>
>
> This happening every 2 hours
>
>
> This been detected both on our PROD and DEV servers.
> We recently upgraded from maximo71 to maximo75.This was not an issue in
> maxim71 using Weblogic Server
>
>
> - 64 bit server running Windows server 2008
> - Oracle 11g DB
> - Maximo Asset Management 7505 IFXBLD023
> - Websphere Server 70015
> -12GB memory.
> - 2 JVMs
>
>
> Any help will be greatly appreciated
>
>
>
>
>
>

--
Yours;
Vijay Kumar Giliyar

From: Chris Lawless (2015-04-14 10:59)

For the most part I have only seen CPU saturation occur when the heap is
exhausted, the heaviest use of CPU is the garbage collector and when there
is little to no heap available it tries and tries to free up space until it
spirals away and crashes. Leading up to the CPU starvation events(s) what
memory availability is Maximo reporting in the SystemOut.log file?
I suspect that if you enable verboseGC logging in the WAS console then
analyze the log you will see "available heap after collection" getting less
and less and GC pause times increasing until you hit CPU starvation, it
sounds like you have a memory leak of some sort, probably due to java or
automation script customization.
Chris.
On Tue, Apr 7, 2015 at 10:47 PM, twabuko@yahoo.com [MAXIMO] <
MAXIMO@yahoogroups.com> wrote:
>
>
> Hi .. Thanks for response
>
>
> 1. How many concurrent users are logged in during this period.?
>
> PROD has at least 20+ on each JVM
> DEV 3 users or less ( Mostly developers) but issue still persists
>
> 2. What is the minimum and maximum heap memory allotted for each JVM.?
>
> minimum - 4096
> maximum - 4096
>
> 3. Is load balancing happening between these two JVM's.?
>
> Load balancing has yet to be set up.
>
> 4. Is there any specific transactions users are trying out during this
> period..?
>
>
> No specific transactions users
>
>
> ---In MAXIMO@yahoogroups.com, <viji2kinna@...> wrote :
>
> Hi,
>
> CPU starvation mainly due to heap memory issue. Can be caused due to
> various reasons.
>
> 1. How many concurrent users are logged in during this period.?
> 2. What is the minimum and maximum heap memory allotted for each JVM.?
> 3. Is load balancing happening between these two JVM's.?
> 4. Is there any specific transactions users are trying out during this
> period..?
>
> Best starting point would be stderr and stdout logfile. We even faced this
> issue during our implementation. Could help you fixing the issue.
>
> Thanks and Regards,
>
> On 5 April 2015 at 05:29, twabuko@... mailto:twabuko@... [MAXIMO] <
> MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com
> > wrote:
>
> >
> >
> > Has anyone encountered this issue ,
> >
> >
> > ' Did not receive adequate CPU time slice. Last known CPU usage time at
> > 08:08:24:629 EDT. Inactivity duration was 67 seconds.'
> >
> >
> > This happening every 2 hours
> >
> >
> > This been detected both on our PROD and DEV servers.
> > We recently upgraded from maximo71 to maximo75.This was not an issue in
> > maxim71 using Weblogic Server
> >
> >
> > - 64 bit server running Windows server 2008
> > - Oracle 11g DB
> > - Maximo Asset Management 7505 IFXBLD023
> > - Websphere Server 70015
> > -12GB memory.
> > - 2 JVMs
> >
> >
> > Any help will be greatly appreciated
> >
> >
> >
> >
> >
> >
>
>
>
> --
> Yours;
> Vijay Kumar Giliyar
>
>
>
>
>
>
>
>

From: Hanna, Christopher A CTR (2015-04-14 16:59)

While I doubt it is causing your CPU issue, I'm not a fan of IBMs recommendation to set the min/max on the heap size to 4gb. It actually contradicts the WebSphere tuning advisor (as well as my personal experience with Java heap sizing). I run my UI JVMs at 1/2.5 and have never had issues. I give the MIF JVMs a little more headroom, setting the max at 4, although the reality is we very rarely exceed 2gb allocation. For the UI, I prefer to have more JVMs using a little less heap (so long as you have cores to support it) so the GC doesn't have as big of a heap to try and keep clean. Of course in my experience, the only real way to get these settings right is through load testing.

If heap exhaustion is causing your CPU issues, you should see indications in the stdout logs as well. Maximo spits the memory usage out every minute or so. If that is the case with such a low user count, I'd say it's highly likely you have a leak.

-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com]
Sent: Tuesday, April 14, 2015 11:00 AM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] CPU Starvation Detected

For the most part I have only seen CPU saturation occur when the heap is exhausted, the heaviest use of CPU is the garbage collector and when there is little to no heap available it tries and tries to free up space until it spirals away and crashes. Leading up to the CPU starvation events(s) what memory availability is Maximo reporting in the SystemOut.log file?

I suspect that if you enable verboseGC logging in the WAS console then analyze the log you will see "available heap after collection" getting less and less and GC pause times increasing until you hit CPU starvation, it sounds like you have a memory leak of some sort, probably due to java or automation script customization.

Chris.

On Tue, Apr 7, 2015 at 10:47 PM, twabuko@yahoo.com [MAXIMO] < MAXIMO@yahoogroups.com> wrote:

>
>
> Hi .. Thanks for response
>
>
> 1. How many concurrent users are logged in during this period.?
>
> PROD has at least 20+ on each JVM
> DEV 3 users or less ( Mostly developers) but issue still persists
>
> 2. What is the minimum and maximum heap memory allotted for each JVM.?
>
> minimum - 4096
> maximum - 4096
>
> 3. Is load balancing happening between these two JVM's.?
>
> Load balancing has yet to be set up.
>
> 4. Is there any specific transactions users are trying out during this
> period..?
>
>
> No specific transactions users
>
>
> ---In MAXIMO@yahoogroups.com, <viji2kinna@...> wrote :
>
> Hi,
>
> CPU starvation mainly due to heap memory issue. Can be caused due to
> various reasons.
>
> 1. How many concurrent users are logged in during this period.?
> 2. What is the minimum and maximum heap memory allotted for each JVM.?
> 3. Is load balancing happening between these two JVM's.?
> 4. Is there any specific transactions users are trying out during this
> period..?
>
> Best starting point would be stderr and stdout logfile. We even faced
> this issue during our implementation. Could help you fixing the issue.
>
> Thanks and Regards,
>
> On 5 April 2015 at 05:29, twabuko@... mailto:twabuko@... [MAXIMO] <
> MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com
> > wrote:
>
> >
> >
> > Has anyone encountered this issue ,
> >
> >
> > ' Did not receive adequate CPU time slice. Last known CPU usage time
> > at
> > 08:08:24:629 EDT. Inactivity duration was 67 seconds.'
> >
> >
> > This happening every 2 hours
> >
> >
> > This been detected both on our PROD and DEV servers.
> > We recently upgraded from maximo71 to maximo75.This was not an issue
> > in
> > maxim71 using Weblogic Server
> >
> >
> > - 64 bit server running Windows server 2008
> > - Oracle 11g DB
> > - Maximo Asset Management 7505 IFXBLD023
> > - Websphere Server 70015
> > -12GB memory.
> > - 2 JVMs
> >
> >
> > Any help will be greatly appreciated
> >
> >
> >
> >
> >
> >
>
>
>
> --
> Yours;
> Vijay Kumar Giliyar
>
>
>
>
>
>
>
>

From: vijay kumar (2015-04-15 10:07)

Did you tried sending the heapdumps to IBM for analysis..? What did they
said..?
On 8 April 2015 at 08:17, twabuko@yahoo.com [MAXIMO] <MAXIMO@yahoogroups.com
> wrote:
>
>
> Hi .. Thanks for response
>
>
> 1. How many concurrent users are logged in during this period.?
>
> PROD has at least 20+ on each JVM
> DEV 3 users or less ( Mostly developers) but issue still persists
>
> 2. What is the minimum and maximum heap memory allotted for each JVM.?
>
> minimum - 4096
> maximum - 4096
>
> 3. Is load balancing happening between these two JVM's.?
>
> Load balancing has yet to be set up.
>
> 4. Is there any specific transactions users are trying out during this
> period..?
>
>
> No specific transactions users
>
>
> ---In MAXIMO@yahoogroups.com, <viji2kinna@...> wrote :
>
> Hi,
>
> CPU starvation mainly due to heap memory issue. Can be caused due to
> various reasons.
>
> 1. How many concurrent users are logged in during this period.?
> 2. What is the minimum and maximum heap memory allotted for each JVM.?
> 3. Is load balancing happening between these two JVM's.?
> 4. Is there any specific transactions users are trying out during this
> period..?
>
> Best starting point would be stderr and stdout logfile. We even faced this
> issue during our implementation. Could help you fixing the issue.
>
> Thanks and Regards,
>
> On 5 April 2015 at 05:29, twabuko@... mailto:twabuko@... [MAXIMO] <
> MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com
> > wrote:
>
> >
> >
> > Has anyone encountered this issue ,
> >
> >
> > ' Did not receive adequate CPU time slice. Last known CPU usage time at
> > 08:08:24:629 EDT. Inactivity duration was 67 seconds.'
> >
> >
> > This happening every 2 hours
> >
> >
> > This been detected both on our PROD and DEV servers.
> > We recently upgraded from maximo71 to maximo75.This was not an issue in
> > maxim71 using Weblogic Server
> >
> >
> > - 64 bit server running Windows server 2008
> > - Oracle 11g DB
> > - Maximo Asset Management 7505 IFXBLD023
> > - Websphere Server 70015
> > -12GB memory.
> > - 2 JVMs
> >
> >
> > Any help will be greatly appreciated
> >
> >
> >
> >
> >
> >
>
>
>
> --
> Yours;
> Vijay Kumar Giliyar
>
>
>
>
>
>
>
>
--
Yours;
Vijay Kumar Giliyar

From: Hanna, Christopher A CTR (2015-04-15 12:10)

You should probably patch your WAS just to eliminate that as a possible cause of the problem. You said you are at .15 and the current rev is .37 so you are pretty far behind the curve.

-Chris H

From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com]
Sent: Wednesday, April 15, 2015 12:38 AM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] CPU Starvation Detected

Did you tried sending the heapdumps to IBM for analysis..? What did they
said..?

On 8 April 2015 at 08:17, twabuko@yahoo.com [MAXIMO] <MAXIMO@yahoogroups.com
> wrote:

>
>
> Hi .. Thanks for response
>
>
> 1. How many concurrent users are logged in during this period.?
>
> PROD has at least 20+ on each JVM
> DEV 3 users or less ( Mostly developers) but issue still persists
>
> 2. What is the minimum and maximum heap memory allotted for each JVM.?
>
> minimum - 4096
> maximum - 4096
>
> 3. Is load balancing happening between these two JVM's.?
>
> Load balancing has yet to be set up.
>
> 4. Is there any specific transactions users are trying out during this
> period..?
>
>
> No specific transactions users
>
>
> ---In MAXIMO@yahoogroups.com, <viji2kinna@...> wrote :
>
> Hi,
>
> CPU starvation mainly due to heap memory issue. Can be caused due to
> various reasons.
>
> 1. How many concurrent users are logged in during this period.?
> 2. What is the minimum and maximum heap memory allotted for each JVM.?
> 3. Is load balancing happening between these two JVM's.?
> 4. Is there any specific transactions users are trying out during this
> period..?
>
> Best starting point would be stderr and stdout logfile. We even faced this
> issue during our implementation. Could help you fixing the issue.
>
> Thanks and Regards,
>
> On 5 April 2015 at 05:29, twabuko@... mailto:twabuko@... [MAXIMO] <
> MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com
> > wrote:
>
> >
> >
> > Has anyone encountered this issue ,
> >
> >
> > ' Did not receive adequate CPU time slice. Last known CPU usage time at
> > 08:08:24:629 EDT. Inactivity duration was 67 seconds.'
> >
> >
> > This happening every 2 hours
> >
> >
> > This been detected both on our PROD and DEV servers.
> > We recently upgraded from maximo71 to maximo75.This was not an issue in
> > maxim71 using Weblogic Server
> >
> >
> > - 64 bit server running Windows server 2008
> > - Oracle 11g DB
> > - Maximo Asset Management 7505 IFXBLD023
> > - Websphere Server 70015
> > -12GB memory.
> > - 2 JVMs
> >
> >
> > Any help will be greatly appreciated
> >
> >
> >
> >
> >
> >
>
>
>
> --
> Yours;
> Vijay Kumar Giliyar
>
>
>
>
>
>
>
>

--
Yours;
Vijay Kumar Giliyar

From: vijay kumar (2015-04-15 18:23)

Hi,
Following things you check if you had not already done this.
1. Setting gcpolicy to gencon. ( -Xgcpolicy:gencon). I have seen
improvement in the performance after doing this. Might help in your case
too.
2. doclinks where clause which comes with OOB maximo is pathetic. Just
cross verify whether this query consuming lot of memory.
3.Its almost sure that memory leak is happening in your maximo system. Need
to check your code if you have done any customization. Especially with
respect to data base connections. Is data base connections are closed
properly..? Can you check how many connections you are having at the time
when you face this issue..?
Hope this helps..!!
Thanks and Regards,
Vijay Kumar
On 15 April 2015 at 17:40, 'Hanna, Christopher A CTR'
christopher.a.hanna@uscg.mil [MAXIMO] <MAXIMO@yahoogroups.com> wrote:
>
>
> You should probably patch your WAS just to eliminate that as a possible
> cause of the problem. You said you are at .15 and the current rev is .37 so
> you are pretty far behind the curve.
>
> -Chris H
>
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com]
> Sent: Wednesday, April 15, 2015 12:38 AM
> To: MAXIMO@yahoogroups.com
> Subject: Re: [MAXIMO List] CPU Starvation Detected
>
>
>
> Did you tried sending the heapdumps to IBM for analysis..? What did they
> said..?
>
> On 8 April 2015 at 08:17, twabuko@yahoo.com [MAXIMO] <
> MAXIMO@yahoogroups.com
> > wrote:
>
> >
> >
> > Hi .. Thanks for response
> >
> >
> > 1. How many concurrent users are logged in during this period.?
> >
> > PROD has at least 20+ on each JVM
> > DEV 3 users or less ( Mostly developers) but issue still persists
> >
> > 2. What is the minimum and maximum heap memory allotted for each JVM.?
> >
> > minimum - 4096
> > maximum - 4096
> >
> > 3. Is load balancing happening between these two JVM's.?
> >
> > Load balancing has yet to be set up.
> >
> > 4. Is there any specific transactions users are trying out during this
> > period..?
> >
> >
> > No specific transactions users
> >
> >
> > ---In MAXIMO@yahoogroups.com, <viji2kinna@...> wrote :
> >
> > Hi,
> >
> > CPU starvation mainly due to heap memory issue. Can be caused due to
> > various reasons.
> >
> > 1. How many concurrent users are logged in during this period.?
> > 2. What is the minimum and maximum heap memory allotted for each JVM.?
> > 3. Is load balancing happening between these two JVM's.?
> > 4. Is there any specific transactions users are trying out during this
> > period..?
> >
> > Best starting point would be stderr and stdout logfile. We even faced
> this
> > issue during our implementation. Could help you fixing the issue.
> >
> > Thanks and Regards,
> >
> > On 5 April 2015 at 05:29, twabuko@... mailto:twabuko@... [MAXIMO] <
> > MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com
> > > wrote:
> >
> > >
> > >
> > > Has anyone encountered this issue ,
> > >
> > >
> > > ' Did not receive adequate CPU time slice. Last known CPU usage time
> at
> > > 08:08:24:629 EDT. Inactivity duration was 67 seconds.'
> > >
> > >
> > > This happening every 2 hours
> > >
> > >
> > > This been detected both on our PROD and DEV servers.
> > > We recently upgraded from maximo71 to maximo75.This was not an issue
> in
> > > maxim71 using Weblogic Server
> > >
> > >
> > > - 64 bit server running Windows server 2008
> > > - Oracle 11g DB
> > > - Maximo Asset Management 7505 IFXBLD023
> > > - Websphere Server 70015
> > > -12GB memory.
> > > - 2 JVMs
> > >
> > >
> > > Any help will be greatly appreciated
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> > --
> > Yours;
> > Vijay Kumar Giliyar
> >
> >
> >
> >
> >
> >
> >
> >
>
> --
> Yours;
> Vijay Kumar Giliyar
>
>
>
>
>
>
>
>
--
Yours;
Vijay Kumar Giliyar