AMX MBeans are loaded asynchronously in a separate thread; they are
all queued and a thread empties the queue. Additions to the queue
are made in response to subsequent MBeanServerNotification of new
MBeans being registered (eg a com.sun.appserv MBean).
But I don't believe that the underlying com.sun.appserv MBeans do so.
What I don't "get" is why the other modules don't perform their
initialization in a separate thread, with suitable threading locks or
barriers when there are dependencies. The server *should* be able to
start up in about 2 seconds on my MacBook Pro.
Lloyd
On Aug 12, 2006, at 12:16 AM, Binod wrote:
> ORB doesnt start during AS startup. Perhaps classes may be getting
> loaded. MQ doesnt start. All resources are started on-demand.
> Admin mbeans, as I understand are loaded parallelly. There
> might be other things in admin that can come up parallelly?
>
> We need to concentrate on web container and classloading.
>
> - Binod.
>
>> Good point. Can parallelize some dis-joint modules (like admin and
>> orb) and achieve some speedup?
>>
>> thanks
>> -Sridatta
>>
>> ---------------------------------------------------------------------
>> ---
>>
>> Subject:
>> why is CPU usage so poor on Glassfish startup?
>> From:
>> Lloyd L Chambers <Lloyd.Chambers_at_Sun.COM>
>> Date:
>> Fri, 11 Aug 2006 15:40:31 -0700
>> To:
>> dev_at_glassfish.dev.java.net
>>
>> To:
>> dev_at_glassfish.dev.java.net
>>
>>
>> CPU utilization suggests that Glassfish startup is single-threaded.
>>
>> Seems like there ought to be plenty of stuff that can be done in
>> parallel.
>>
>>
>> ---------------------------------------------------------------------
>> ---
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> ---
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>