It fixed.
I accessed EJB through appClientContainer,
Just as your said, it had failed because I had not restarted the server,
Thank you very much!
Thanks,
henrry_china
----- Original Message -----
From: <glassfish_at_javadesktop.org>
To: <users_at_glassfish.dev.java.net>
Sent: Thursday, August 09, 2007 12:09 PM
Subject: Re: The use of use-thread-pool-id element in sun-ejb-jar.xml
> Did you restart the server after creating the thread-pool? You need to
> restart the server for this thread pool to take effect.
>
> If you did, then how are you accessing the EJB? Is it through (a)
> AppClientContainer or (b) from a stand-alone java client OR (c) from
> another EJB?
>
> If you are accessing it from another EJB, then because of the way our ORB
> optimizes the request dispatch, the EJB may not be invoked with new
> 'threadpool3'
>
> Let me know.
> [Message sent by forum member 'mk111283' (mk111283)]
>
> http://forums.java.net/jive/thread.jspa?messageID=230162
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
>