|
Home > Archive > WebSphere Application Server > August 2005 > Upgrade Issues to WAS 5.1.1.4 on IBM Iseries
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Upgrade Issues to WAS 5.1.1.4 on IBM Iseries
|
|
| Dave Jones 2005-08-09, 5:57 pm |
| FYI...this is being posted by a "newbie", not an technology expert, so
please let me know if there are details that I'm not providing.
My company is currently having upgrade issues going from 4.0.5 to 5.1.1.4 on
an IBM Iseries Model 270. The system is having memory issues and is
grinding to a halt, so far no luck from support. Hoping to see if anyone
else has a similar configuration as us and can provide some help as to if it
is a hardware issue. The box has a dedicated 1.2GB memory pool for WAS, and
a total of 4GB available. From what I have seen, 1GB is the minimum
requirement for version 5.1.1. We are running a fairly complex application,
but did not have this memory problem using 4.0.5.
Any help would be much appreciated.
Thanks.
David
| |
| Paul Ilechko 2005-08-09, 5:57 pm |
| Dave Jones wrote:
> FYI...this is being posted by a "newbie", not an technology expert, so
> please let me know if there are details that I'm not providing.
>
> My company is currently having upgrade issues going from 4.0.5 to 5.1.1.4 on
> an IBM Iseries Model 270. The system is having memory issues and is
> grinding to a halt, so far no luck from support. Hoping to see if anyone
> else has a similar configuration as us and can provide some help as to if it
> is a hardware issue. The box has a dedicated 1.2GB memory pool for WAS, and
> a total of 4GB available. From what I have seen, 1GB is the minimum
> requirement for version 5.1.1. We are running a fairly complex application,
> but did not have this memory problem using 4.0.5.
I don't know anything about iSeries, but in general I wouldn't think of
running WAS 5+ with less than 2G of memory in development, and less than
4G in production.
| |
| Dave Jones 2005-08-09, 5:57 pm |
| This may be the case, however, the IBM hardware requirements state:
WebSphere Application Server Network Deployment 5.1.1
OS/400:
a.. AS/400e server 170 with processor feature 2385 or
b.. AS/400e server 720 with processor feature 2062 or
c.. iSeries Model 270 with processor feature 2252 or
d.. iSeries Model 820 with processor feature 2396
e.. Minimum 381 MB free disk space for installation
f.. Minimum 750 MB physical memory; 1 GB recommended
I guess this is something I can suggest. Thank you Paul.
"Paul Ilechko" <paul.ilechko@us.ibm.com> wrote in message
news:ddarvi$5bge$1@news.boulder.ibm.com...
> Dave Jones wrote:
>
5.1.1.4 on[vbcol=seagreen]
anyone[vbcol=seagreen]
if it[vbcol=seagreen]
and[vbcol=seagreen]
application,[vbcol=seagreen]
>
> I don't know anything about iSeries, but in general I wouldn't think of
> running WAS 5+ with less than 2G of memory in development, and less than
> 4G in production.
>
| |
| Paul Ilechko 2005-08-09, 5:57 pm |
| Dave Jones wrote:
> This may be the case, however, the IBM hardware requirements state:
>
> WebSphere Application Server Network Deployment 5.1.1
>
> OS/400:
>
> a.. AS/400e server 170 with processor feature 2385 or
> b.. AS/400e server 720 with processor feature 2062 or
> c.. iSeries Model 270 with processor feature 2252 or
> d.. iSeries Model 820 with processor feature 2396
> e.. Minimum 381 MB free disk space for installation
> f.. Minimum 750 MB physical memory; 1 GB recommended
> I guess this is something I can suggest.
In my experience WAS will *run* (just) with 1G memory - as long as your
applications don't do anything ;-) But then you need to look at the
memory consumed by your apps, such as HTTP session data. Remember, those
numbers are bare minimums. Typically you don't want to be running at
100% of any resource out of the box.
| |
|
| Hello,
What are the symptoms ? ("memory issues and is grinding to a halt" is not
what I would call an accurate and usefull description of the issue :-)
Do you mean that the application is logging OutOfMemoryErrors all the time ?
And what for halts ? Does the JVM die with a core crash or is getting
unresponsive ?
Obviously, a bit more RAM would not be useless... Be sure to check the java
process are not swapped, because GC cycles on a swapped process are slow and
lengthy...
|
|
|
|
|