in-line On Fri, 28 Jan 2005 12:13:16 -0500, Chaikin, Yaakov Y. <[EMAIL PROTECTED]> wrote: > Eddie, > > How long it takes to look up things through JNDI? Loooooooong is the answer. > That's even if your JNDI is sitting on the same machine as your servlet/EJB > container. But if it's a distributed environment... see you later. :)
Seriously?! I've not experienced that, but I can certainly see why you might like to cache it, given the situation you describe. > As far as an administrator changing the DataSource while the application is > running... There are opportunities to take care of this without slowing your > application down for the rest of the time. > > Of course, restart the app is one obvious choice, but if that's not an > option... then one solution that come to is to redirect all incoming traffic > to a different machine for the time being, change your datasource and then > allow traffic again. Taking a given instance down isn't that huge of a deal, as I understand it. I'm not totally up-to-speed with how our admins handle this, but I get the impression they could take an instance off-line, modify it, and then put it back up ... and do the next one ... and the next one ... so it's not a huge impact. > I'd have to think about how to do this better if that's not an option for > whatever reason... But to always have to look up your DataSource through > JNDI just seems like a major slowdown just to take care of this one > situation where you would change the data source on the fly. I'll have to run some time trials. I was of the impression JNDI lookups happened quite fast. I don't do EJB, and each node in a cluster has JNDI info as I understand it - least, in our environment. > That's my understanding of the issue... > > Yaakov. Good talking points. I learned something. Thanks ;-) -- Eddie Bush --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
