Hi Dave,
I am also facing a similar issue of Blocked thread. We have increased file
descriptor from 1024 to 2048 as suggested by you still the issue persists. Do
we need to increase file descriptor to 65000 to resolve this issue. Is there
any adverse effect on weblogic after increasing the file descriptor. Your
suggestion is appreciated. Below are the thread dumps from managed server which
shows the blocked thread.
###<Jul 21, 2015 9:23:58 AM IST> <Info> <Server> <aukpczbr.dc-dublin.de>
<aukpczbr_p2> <[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default
(self-tuning)'> <<WLS Kernel>> <> <> <1437467038573> <BEA-002634> <The server
"pci_p2_ad_admin" disconnected from this server.>
####<Jul 21, 2015 9:23:58 AM IST> <Error> <WebLogicServer>
<aukpczbr.dc-dublin.de> <aukpczbr_p2> <[STANDBY] ExecuteThread: '11' for queue:
'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1437467038600>
<BEA-000337> <[STUCK] ExecuteThread: '16' for queue: 'weblogic.kernel.Default
(self-tuning)' has been busy for "652" seconds working on the request
"weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl@58887aee", which is
more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack
trace:
Thread-3471 "[STUCK] ExecuteThread: '16' for queue: 'weblogic.kernel.Default
(self-tuning)'" <alive, suspended, blocked, priority=1, DAEMON> {
-- Blocked trying to get lock: org.apache.log4j.spi.RootLogger@21cb1369[not
locked]
org.apache.log4j.Category.callAppenders(Category.java:204)
org.apache.log4j.Category.forcedLog(Category.java:391)
org.apache.log4j.Category.log(Category.java:856)
org.slf4j.impl.Log4jLoggerAdapter.error(Log4jLoggerAdapter.java:541)
com.vodafone.pciadaptor.core.emis.HttpConnectionProbe.onRun(HttpConnectionProbe.java:105)
com.vodafone.pciadaptor.core.scheduling.AbstractScheduledTask.run(AbstractScheduledTask.java:42)
org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:51)
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
org.springframework.scheduling.commonj.TimerManagerTaskScheduler$TimerScheduledFuture.timerExpired(TimerManagerTaskScheduler.java:112)
org.springframework.scheduling.commonj.TimerManagerTaskScheduler$ReschedulingTimerListener.timerExpired(TimerManagerTaskScheduler.java:165)
weblogic.timers.internal.commonj.ListenerWrap.timerExpired(ListenerWrap.java:37)
weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
}
>
Thanks in Advance.
Regards,
Aakash Lodha
============================================================================================================================
Disclaimer: This message and the information contained herein is proprietary
and confidential and subject to the Tech Mahindra policy statement, you may
review the policy at http://www.techmahindra.com/Disclaimer.html externally
http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra.
============================================================================================================================
