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