• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Jesse Silverman
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Al Hobbs
  • salvin francis

Time causes thread count increase.

 
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.....
 
Ranch Hand
Posts: 1683
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Reji RNair
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hii..I am using java.util.timer and java.util.TimerTask
 
Reji RNair
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
 
reply
    Bookmark Topic Watch Topic
  • New Topic