Or you can use Dynamic Proxy to wrap around the Context reference your holding in your SB; if Context.lookup() throws a NamingException, have the DP reconstruct the Context. Here's an example of writing DP intercepts at the Context, EJBHome and EJBObject levels, without a single mod to client code:
http://dima.dhs.org/misc/ejbproxy.jsp Gene --- Nicholas <[EMAIL PROTECTED]> wrote: > Using WebSphere 3.5.4 on Solaris 2.6. > We have an LDAP utility session bean.Upon the > setSessionContext(), the instances of the bean acquire > a connection to LDAP and then issue lookups on behalf > of the client. > > What happens is that the LDAP server is restarted and > all of a sudden, these LDAP connections in the pooled > beans are invalid. > > What I would like to do is invalidate all pooled > instances of the bean, and have subsequent activations > fail util the LDAP server becomes available. > > Anyone have any ideas ? > > //Nicholas > > ===== > Nicholas Whitehead > Home: (973) 377 9335 > Cell: (201) 615 2716 > Work: (212) 235 5783 > [EMAIL PROTECTED] > > __________________________________________________ > Do You Yahoo!? > Try FREE Yahoo! Mail - the world's greatest free email! > http://mail.yahoo.com/ > > =========================================================================== > To unsubscribe, send email to [EMAIL PROTECTED] and include in the body > of the message "signoff EJB-INTEREST". For general help, send email to > [EMAIL PROTECTED] and include in the body of the message "help". > __________________________________________________ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/ =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
