I am using weblogic 9 for deployment. I use java.util.Timer to schedule tasks for intervals.. It is working fine in usual cases. But It is noticed an increase in thread count when we hold the server trace console in quick edit mode.. But the same is not happening in pure java console(not Weblogic). The issue makes the projuct unstable.. I know that it will not occur in unix machine.. coz we canot catch a thread there.. But If we deployed the appln in windows enviroment the issue may arise if the quick edit mode is enabled in console.. By console I dont mean weblogic web cosle.. What I mean is trace console.. Can Anybody help me to solve this issue.. More details.. I have used javas socket.setSoTimeout(int) to schedukle tasks. then also same issue arises... Is it a weblogic related issue..? Please help me.....
It is unclear what tasks you are scheduling. Do you want the timer service to run within a Weblogic Server execute thread? If so, then use the WebLogic timer service, which extends the standard JMX timer service.
i have tried using weblogic.utils.time.Timer Even now also the same issue rises.. When I view thread dump it shows threads like this.. [ACTIVE] ExecuteThread: '87' for queue: 'weblogic.kernel.Default (self-tuning)'" id= 129 idx=0xea tid=2864 prio=5 alive, in native, waiting, daemon -- Waiting for notification on: weblogic/work/ExecuteThread@0x09586CF0[fat lock] at jrockit/vm/Threads.waitForSignal(J)Z(Native Method) at jrockit/vm/Locks.wait(Ljava/lang/Object;J)V(Unknown Source) at java/lang/Object.wait()V(Native Method) at weblogic/work/ExecuteThread.waitForRequest()V(ExecuteThread.java:165) ^-- Lock released while waiting: weblogic/work/ExecuteThread@0x09586CF0[fat lock]
at weblogic/work/ExecuteThread.run()V(ExecuteThread.java:186) at jrockit/vm/RNI.c2java(IIII)V(Native Method) -- end of trace