That property will shutdown the local openejb instance that you have created with the InitialContext... I suspect that is not what you are after. The property is most useful when running unit tests where you need to restart the container to check with some other initial conditions
-Stephe 2009/12/4 rtselvan <[email protected]> > > I am looking up ejbs from my web app running on a tomcat server and openEJB > running as standalone, when the openEJB server is restarted, the web > application JNDI lookups fails with "Invalid response from server: -1", so > I > am trying to close the JNDI context and re-open it but still getting the > same "Invalid response from server: -1" error. It seems that the jndi > context.close doesn't do anything seems due to caching. Is there a setting > that can be passed to the "RemoteInitialContextFactory" to force close it? > > I just tried to use the embedded setting > "openejb.embedded.initialcontext.close=destroy" but doesn't appear to be > the > correct property for the purpose. > > Thanks > /selvan > > -- > View this message in context: > http://old.nabble.com/InitialContext-Close-doesn%27t-do-anything-tp26635749p26635749.html > Sent from the OpenEJB User mailing list archive at Nabble.com. > >
