Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6190873

JMX lacks thread control interface

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Resolved
    • Priority: P2
    • Resolution: Fixed
    • Affects Version/s: 5.0
    • Fix Version/s: 5.0u2
    • Component/s: core-svc
    • Subcomponent:
    • Resolved In Build:
      b04
    • CPU:
      generic
    • OS:
      generic

      Backports

        Description

        It has been determined that JMX1.2 spawns a bunch of threads (could be 100's in large WLS deployments) which are taking up resources (i.e. thread pools, memory, and such) and these threads are not managed by the J2EE container. JMX1.2 doesn't provide a way for controlling of threads from outside of JMX. This has significant negative impact on performance, tuning, and scalability.

        The specific area where this is problematic for BEA is the thread that is created for each JMX Connector Client to pick up notifications from the remote server. If there were a way to execute the fetchNotifications request from within a thread in a user-supplied thread pool, that would suffice for the immediate problem.
        ###@###.### 11/4/04 18:55 GMT

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                emcmanus Eamonn McManus
                Reporter:
                mmma Marvin Ma (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: