asked on

Application on Weblogic 8.1 SP6 stop responding

Hi everybody,

We've got peoplesoft 8.48 runing on Weblogic 8.1 SP6, from time to time application stops responding and nothing is found on weblogic server log files, the only solution is to restart the server.

I suppose it's something related with a hung thread, I didn't find suitable troubleshooting tools on weblogic8.1. A kill -3 gives no good information.

Regards,

Rachid,

D Patel

First check your registry....

System Key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters]
Value Name: MaxUserPort
Data Type = REG_DWORD
Data Range = 5000 - 65534 Port-Number
Data Default = 5000

Set this to 65534

System Key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters]
Value Name: TcpTimedWaitDelay
Data Type: REG_DWORD (DWORD Value)
Value Data: 30-300 seconds (decimal)

This defaults to ~240 AFAIK. This is too high for PIA. Set it between
30 and 60.

Next check your Application Server domains. Be sure the Jolt Client
Cleanup Timeout is set to about 10 minutes

Next, review all of your Web server and PIA timeouts for sanity purposes
(but leave the Jolt-related timeouts in the web profile alone!). The
shorter you can get away with these and still meet business
requirements, the better off you will be in terms of socket use. If
your implementation involves popping up new windows from PeopleCode, be
sure to set the "State Discard Interval" in your web profile. This is a
timeout that controls the connections and state-related JVM memory
associated with these new browser windows, and it defaults to 0; meaning
*never* discard states.

NOTE: be sure to read the doc on State Discard Interval setting...it is
*not* an idle timeout, so you need to pick a value that will suit your
purposes, but will not be so short as to kick users out of browser
windows that they are actively using.

And then finally...since you are Tools 8.48, it may be that the default
sizes for your Jolt Pools aren't large enough (although I think they
suffice for most people), which would cause new sessions to create new
socket connections when the pool of Jolt connections is exhausted. You
might want to consider increasing these. But I would only do this
*after* making the other changes above and seeing if those take care of
your problem.

Hope it helps

brachid

ASKER

Hi Patel,

I'm on AIX not windows, I will check other weblogic relative parameters.

Rachid,

This question needs an answer!

Become an EE member today

7 DAY FREE TRIAL

Members can start a 7-Day Free trial then enjoy unlimited access to the platform.

View membership options

Learn why we charge membership fees

We get it - no one likes a content blocker. Take one extra minute and find out why we block content.