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.
Hi Mrggutz
Hopefully I'm doing this right as I am. We to the group. If I'm not
supposed to reply to the group my apologies I won't do it again.
So performance issues on a 6.2.1 instance. Are you a WebSphere or
Weblogic environment?
One problem I have run into with performance in our environment is due
to use (or overuse) of the "Download" (to Excel) option within the
list screens. This especially causes problems when users try to
retrieve large (10,000s of records) data sets this way. From my
understanding (having done some Java customization of 6.2.x it would
appear loading data this way causes Maximo to load all data for said
records into memory in the form of Maximo Business Objects (or MBOs.).
In our environment we originally had this unrestricted which would
eventually lead to JVM out of memory exceptions (i.e. flat out
crashes.). If you are on WebSphere evidence of this would be javacore
and heapdump files in amongst you Maximo.log files.
I'm not in front of my workstation right now so I don't have the exact
.properties file in mind but this functionality can be capped at a set
number of records (to the dismay of you users) which will prevent this
issue.
Without more information on your environment this is one of the things
that kind of "stuck out" in my experience.
I'll get back to you with the exact parameter / properties file once I
get near a workstation or laptop.
Greg
If you have a possible answer to the question, absolutely you can post it.
That's what the group's for!
Christopher (the owner of this group) will probably reply in his own time,
but I'm pretty sure he would say the same.
Shannon
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
Greg Aluise
Sent: February-22-12 6:24 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: Maximo 6.2.1 Issues
Hi Mrggutz
Hopefully I'm doing this right as I am. We to the group. If I'm not
supposed to reply to the group my apologies I won't do it again.
So performance issues on a 6.2.1 instance. Are you a WebSphere or
Weblogic environment?
One problem I have run into with performance in our environment is due
to use (or overuse) of the "Download" (to Excel) option within the
list screens. This especially causes problems when users try to
retrieve large (10,000s of records) data sets this way. From my
understanding (having done some Java customization of 6.2.x it would
appear loading data this way causes Maximo to load all data for said
records into memory in the form of Maximo Business Objects (or MBOs.).
In our environment we originally had this unrestricted which would
eventually lead to JVM out of memory exceptions (i.e. flat out
crashes.). If you are on WebSphere evidence of this would be javacore
and heapdump files in amongst you Maximo.log files.
I'm not in front of my workstation right now so I don't have the exact
.properties file in mind but this functionality can be capped at a set
number of records (to the dismay of you users) which will prevent this
issue.
Without more information on your environment this is one of the things
that kind of "stuck out" in my experience.
I'll get back to you with the exact parameter / properties file once I
get near a workstation or laptop.
Greg
"If you have a possible answer to the question, absolutely you can post it.
That's what the group's for!"
Ditto!
Wes Williams
(The Moderator)
http://www.weswilliams.net
From: Shannon Rotz <shannonrotz@yahoo.ca>
To: MAXIMO@yahoogroups.com
Sent: Wednesday, February 22, 2012 9:34 PM
Subject: RE: [MAXIMO List] Re: Maximo 6.2.1 Issues
If you have a possible answer to the question, absolutely you can post it.
That's what the group's for!
Christopher (the owner of this group) will probably reply in his own time,
but I'm pretty sure he would say the same.
Shannon
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
Greg Aluise
Sent: February-22-12 6:24 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: Maximo 6.2.1 Issues
Hi Mrggutz
Hopefully I'm doing this right as I am. We to the group. If I'm not
supposed to reply to the group my apologies I won't do it again.
So performance issues on a 6.2.1 instance. Are you a WebSphere or
Weblogic environment?
One problem I have run into with performance in our environment is due
to use (or overuse) of the "Download" (to Excel) option within the
list screens. This especially causes problems when users try to
retrieve large (10,000s of records) data sets this way. From my
understanding (having done some Java customization of 6.2.x it would
appear loading data this way causes Maximo to load all data for said
records into memory in the form of Maximo Business Objects (or MBOs.).
In our environment we originally had this unrestricted which would
eventually lead to JVM out of memory exceptions (i.e. flat out
crashes.). If you are on WebSphere evidence of this would be javacore
and heapdump files in amongst you Maximo.log files.
I'm not in front of my workstation right now so I don't have the exact
.properties file in mind but this functionality can be capped at a set
number of records (to the dismay of you users) which will prevent this
issue.
Without more information on your environment this is one of the things
that kind of "stuck out" in my experience.
I'll get back to you with the exact parameter / properties file once I
get near a workstation or laptop.
Greg
Sorry Wes: for some reason I thought Christopher was the moderator. Are you guys co-moderators, or am I spaced out or something?
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of wwilliams@rocketmail.com
Sent: February-23-12 4:18 AM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Re: Maximo 6.2.1 Issues
"If you have a possible answer to the question, absolutely you can post it.
That's what the group's for!"
Ditto!
Wes Williams
(The Moderator)
http://www.weswilliams.net
From: Shannon Rotz <shannonrotz@yahoo.ca <mailto:shannonrotz%40yahoo.ca> >
To: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
Sent: Wednesday, February 22, 2012 9:34 PM
Subject: RE: [MAXIMO List] Re: Maximo 6.2.1 Issues
If you have a possible answer to the question, absolutely you can post it.
That's what the group's for!
Christopher (the owner of this group) will probably reply in his own time,
but I'm pretty sure he would say the same.
Shannon
From: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> [mailto:MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> ] On Behalf Of
Greg Aluise
Sent: February-22-12 6:24 PM
To: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
Subject: [MAXIMO List] Re: Maximo 6.2.1 Issues
Hi Mrggutz
Hopefully I'm doing this right as I am. We to the group. If I'm not
supposed to reply to the group my apologies I won't do it again.
So performance issues on a 6.2.1 instance. Are you a WebSphere or
Weblogic environment?
One problem I have run into with performance in our environment is due
to use (or overuse) of the "Download" (to Excel) option within the
list screens. This especially causes problems when users try to
retrieve large (10,000s of records) data sets this way. From my
understanding (having done some Java customization of 6.2.x it would
appear loading data this way causes Maximo to load all data for said
records into memory in the form of Maximo Business Objects (or MBOs.).
In our environment we originally had this unrestricted which would
eventually lead to JVM out of memory exceptions (i.e. flat out
crashes.). If you are on WebSphere evidence of this would be javacore
and heapdump files in amongst you Maximo.log files.
I'm not in front of my workstation right now so I don't have the exact
.properties file in mind but this functionality can be capped at a set
number of records (to the dismay of you users) which will prevent this
issue.
Without more information on your environment this is one of the things
that kind of "stuck out" in my experience.
I'll get back to you with the exact parameter / properties file once I
get near a workstation or laptop.
Greg
Chris is the owner I am the lowly moderator
Wes Williams
http://www.weswilliams.net
http://www.williamsconnell.com
________________________________
From: Shannon Rotz <shannonrotz@yahoo.ca>
To: MAXIMO@yahoogroups.com
Sent: Thursday, February 23, 2012 2:28 PM
Subject: RE: [MAXIMO List] Re: Maximo 6.2.1 Issues
Sorry Wes: for some reason I thought Christopher was the moderator. Are you guys co-moderators, or am I spaced out or something?
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of wwilliams@rocketmail.com
Sent: February-23-12 4:18 AM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Re: Maximo 6.2.1 Issues
"If you have a possible answer to the question, absolutely you can post it.
That's what the group's for!"
Ditto!
Wes Williams
(The Moderator)
http://www.weswilliams.net
From: Shannon Rotz <shannonrotz@yahoo.ca <mailto:shannonrotz%40yahoo.ca> >
To: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
Sent: Wednesday, February 22, 2012 9:34 PM
Subject: RE: [MAXIMO List] Re: Maximo 6.2.1 Issues
If you have a possible answer to the question, absolutely you can post it.
That's what the group's for!
Christopher (the owner of this group) will probably reply in his own time,
but I'm pretty sure he would say the same.
Shannon
From: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> [mailto:MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> ] On Behalf Of
Greg Aluise
Sent: February-22-12 6:24 PM
To: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
Subject: [MAXIMO List] Re: Maximo 6.2.1 Issues
Hi Mrggutz
Hopefully I'm doing this right as I am. We to the group. If I'm not
supposed to reply to the group my apologies I won't do it again.
So performance issues on a 6.2.1 instance. Are you a WebSphere or
Weblogic environment?
One problem I have run into with performance in our environment is due
to use (or overuse) of the "Download" (to Excel) option within the
list screens. This especially causes problems when users try to
retrieve large (10,000s of records) data sets this way. From my
understanding (having done some Java customization of 6.2.x it would
appear loading data this way causes Maximo to load all data for said
records into memory in the form of Maximo Business Objects (or MBOs.).
In our environment we originally had this unrestricted which would
eventually lead to JVM out of memory exceptions (i.e. flat out
crashes.). If you are on WebSphere evidence of this would be javacore
and heapdump files in amongst you Maximo.log files.
I'm not in front of my workstation right now so I don't have the exact
.properties file in mind but this functionality can be capped at a set
number of records (to the dismay of you users) which will prevent this
issue.
Without more information on your environment this is one of the things
that kind of "stuck out" in my experience.
I'll get back to you with the exact parameter / properties file once I
get near a workstation or laptop.
Greg