On Mar 11, 2009, at 8:45 PM, Kedar Mhaswade wrote:
>
>
> Kenneth Saks wrote:
>>
>> sun-ejb-jar.xml
>> called use-thread-pool-id. The value is set by the ejb container
>> on the underlying
>> remote object associated with the bean. The value is used by the
>> orb since it's their
>> code that's choosing threads to handle the remote invocations.
>
> This is a little weird in that we refer to something in domain.xml
> from
> within sun-ejb-jar.xml, by name.
That's a good part of what our sun-*.xmls do. How is this any
different from mapping a
logical application resource like a resource-ref to the physical name
of a jdbc-resource?
>
>
>> I don't know whether there's some other orb-related thread-pool
>> usage.
>
>
>>> and connectors?
>> Don't know. Isn't there an admin API for retrieving the thread
>> pools that are defined
>> in domain.xml? Maybe just search for usages.
>
> That would only tell me how runtime accesses the data in domain.xml.
> My question was regarding creating/deleting/listing the thread pools
> created.
>
> Also, since the server is now being more modular, we need to have
> someone
> who owns the configuration of these thread-pools.
>
> -Kedar
>
>>>
>>>>>
>>>>>
>>>>> I ask this for it relates to availability of asadmin commands
>>>>> such as create/delete/list-threadpool(s). Do we need to carry
>>>>> forward
>>>>> these commands for v3?
>>>> Yes. Is there some other way to create them?
>>>
>>> Regardless of what GUI/AMX do, we need a way in asadmin to achieve
>>> this.
>>>
>>> Looks like it is needed. So, we should have them for the September
>>> release.
>>>
>>>
>>> -Kedar
>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>> Kedar
>>>>>
>>>>> (PS - I haven't seen these commands being used by users).
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>