Upgrading of WLS 6.1 from SP3 to SP5

Question

Can anyone help me.
I am going to upgrade WLS 6.1 from SP3 to SP5.
How can i do this ?
From where do i download the ServicePack (SP5) ?
Is there someting i have to be aware off, about the license ?

Answer 1

Hi Paul
This is a JVM bug, Upgrade to 1.3.1_08 jvm from sun
Contact weblogic support for temporary workaround
Paul Wilson wrote:
We've a client running 6.1 sp2 on Solaris, who is experiencing
Weblogic hanging for roughly 10 minutes at a time. On resumption they
get:
####<06-May-03 16:28:50 BST> <Critical> <WebLogicServer> <edox>
<Mendel> <ListenThread> <system> <> <000204> <Failed to listen on port
80, failure count: 1, failing for 1,052,234,928 seconds,
java.net.SocketException: Software caused connection abort>
####<06-May-03 16:28:51 BST> <Notice> <WebLogicServer> <edox> <Mendel>
<ListenThread> <system> <> <000205> <After having failed to listen,
the server is now listening on port 80>
The last time it occurred, I got them to take a thread dump and all
but one execution thread and the listener threads were idle. One
execution thread was busy reloading (or loading) a class from the war.
I've asked them to ensure that the reload period is -1, but that
shouldn't cause a 10 minute hang; plus nothing had changed. Red
herring?
As an experiment I wrote a servlet that just blocks its execution
thread: after about a thousand calls to this on our dev box, we get
<May 14, 2003 5:45:42 PM BST> <Critical> <WebLogicServer> <Failed to
listen on port 6001, failure count: 3, failing for 1,052,930,739
seconds, java.net.SocketException: Too many open files>
AFAIK this means that we've run out of file descriptors. Our client
doesn't get this, so I don't think that is happening to them.
A number of people on weblogic.* groups reported similar problems
about a year ago, but without any really definitive resolutions.
Anyone solved this, even by upgrading?