Database Reference
In-Depth Information
Configure the WebLogic user soft and hard file descriptor limits as follows
(please use the value appropriate for your environment):
$ vi /etc/security/limits.conf
weblogic soft nofile 32768
weblogic hard nofile 32768
Please make sure that the system-level file descriptor limit is higher than
the user value. The following command provides the system-level file
descriptor limit:
$ cat /proc/sys/fs/file-max
•
Stuckthread error messages
: Runtime Stuckthread must be analyzed
for its root cause and you correct them as these consume the threads
that are permanently not doing any work for us and impacts the system's
scalability. You can take the thread dump to identify the threads that are
stuck and its reason. It is a leading practice to perform periodic restart of
the application server(s) as a temporary fix for freeing system's resources
consumed by Stuckthread(s) in a JVM of an application server(s). It is
highly recommended that you handle the Stuckthread(s) events and ex-
ceptions gracefully for better availability and scalability. In other words,
onemust identify andimplement the permanent fix for the Stuckthread(s).
MoststuckthreadissuesoccurduetoanexternalsystemholdingtheWe-
bLogic thread for processing. For example, if an SOA Suite or WebLogic
connects to an external database or a system for data retrieval and it did
not receive a response within a certain limit and also there is no time out
configured, then the WebLogic thread goes to the stuck state. Eventually,
WebLogic will run out of threads.
