Hello Mahesh Kannan,
Hello Siraj Ghaffar,
Hello GF) Dev Teams,
Hello Everyone,
I'm am got confused by monitoring EJB on glassfish.
The monitor log gives me some images bleow.
1, The instance of EJB3.0 Stateful Session bean is always not
removed from passivation store when timeout.
#I think it should be removed when timeout.
2, When deploy an SFSB application on GF, monitor it without
running it, and find out that the passavation store is not empty.
#I think it should be empty.
3, The RemoveCount of SFSB will not be increased when calling
an @Remove method
#I think it should be increased.
4, When deploy a module which contains several beans(for
assumption Bean1, Bean2, Bean3), when one request for Bean1,
and there is no available instance of Bean1 in the pool, EJB
Container will create some new instances for each bean(why not
Bean1 only), the number of new instance is equals to Resize
Quantity the setting in GUI for pool and cache.
#I think EJB Container should create new instance for Bean1 only,
it will improve GF's availability for more beans.
5, When customize Initial and Minimum Pool Size and leave the other
setting for default(600 for Pool Idle Timeout), the setting for Initial
and Minimum Pool Size will not take effect. But when customize 30
for Pool Idle Timeout, the setting will take effect.
#I am eager to know why.
Did anyone get the same situation? and anyone's help will be appreciated.
Thanks.
Wu.
--
A new email address of FJWAN is launched from Apr.1 2007.
The updated address is: wujie_at_cn.fujitsu.com
--------------------------------------------------
Wu Jie
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
8/F., Civil Defense Building, No.189 Guangzhou Road,
Nanjing, 210029, China
TEL: +86+25-86630566-918
FAX: +86+25-83317685
EMAIL: wujie_at_cn.fujitsu.com
--------------------------------------------------
This communication is for use by the intended recipient(s) only and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not an intended recipient of this communication, you are hereby notified that any dissemination, distribution or copying hereof is strictly prohibited. If you have received this communication in error, please notify me by reply e-mail, permanently delete this communication from your system, and destroy any hard copies you may have printed