This week's book giveaway is in the Cloud/Virtualization forum.
We're giving away four copies of Learning OpenStack Networking: Build a solid foundation in virtual networking technologies for OpenStack-based clouds and have James Denton on-line!
See this thread for details.
Win a copy of Learning OpenStack Networking: Build a solid foundation in virtual networking technologies for OpenStack-based clouds this week in the Cloud/Virtualization forum!
  • 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Knute Snortum
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Ganesh Patekar
  • Stephan van Hulst
  • Pete Letkeman
  • Carey Brown
Bartenders:
  • Tim Holloway
  • Ron McLeod
  • Vijitha Kumara

CPU increases over time when program is idle  RSS feed

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a program (test) running on Application 4.3 and Application 4.2
Test running on App. 4.2 has 19 threads and it's stable based on Jconsole monitoring

attach listner
com.ibm.logging.filehandler:EDMsgHandler
com.ibm.logging.filehandler:EDMsgHandler
com.ibm.logging.filehandler:EDTrcHandler
com.ibm.logging.filehandler:EDTrcHandler
finalizer
JMX server connection timeout 25
main
reference handler
rmi scheduler(0)
rmi tcp accept-0
rmi tcp connection(4)-127.0.0.1
rmi tcp connection(5)-127.0.0.1
rmi tcp connection(6)-127.0.0.1
thread-0
Thread-1
Thread-2
Thread-3
Thread-4

Test running on App. 4.3 has 21 threads and it's not stable based on Jconsole monitoring (fluctuates 19 - 21)

attach listner
com.ibm.logging.filehandle
com.ibm.logging.filehandle
com.ibm.logging.filehandle
com.ibm.logging.filehandle
finalizer
jmx server connection time
main
reference handler
rmi scheduler(0)
rmi tcp accept-0
rmi tcp connection(22)-12
rmi tcp connection(23)-12
rmi tcp connection(24)-12
rmi tcp connection(25)-12
rmi tcp connection(26)-12
thread-0
thread-1
thread-2
thread-3
thread-4

The only extra threads I've noticed in App. 4.3 are the following types
rmi tcp connection type (2 extra)

Problem
CPU resource is being consumed over time in App 4.3 even when program test is idle.

Question
What does this type of thread do and could you give me any pointers on where to look.

Thank You for any input
 
author
Sheriff
Posts: 23587
138
C++ Chrome Eclipse IDE Firefox Browser Java jQuery Linux VI Editor Windows
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Mike Gerrad wrote:
Question
What does this type of thread do and could you give me any pointers on where to look.



Those are not thread types, they are merely the name of the threads. And a Java program can name a thread anything that it wants to, so all you can do is speculate on what the threads does by its given name -- meaning it is related to RMI communications.

Henry
 
Ranch Hand
Posts: 73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator


rmi tcp connection

CPU resource is being consumed over time in App 4.3 even when program test is idle.



It is difficult to guess what the thread is doing unless we can see the code. My guess is the rmi thread is doing some thing in a periodic way. Do you see the CPU resource goes up and down or what pattern do you see??

 
Don't get me started about those stupid light bulbs.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!