Just for interest sake, were you able to reproduce it again? And, how did you notify OpenEJB of the LocalClient? Via the application-client.jar or initialContext bind?
Quintin Beukes On Tue, Sep 29, 2009 at 2:41 AM, David Blevins <[email protected]> wrote: > > On Sep 28, 2009, at 5:29 PM, Laird Nelson wrote: > >> On Mon, Sep 28, 2009 at 8:08 PM, David Blevins >> <[email protected]>wrote: >> >>> Could be some edge case that makes this fail or else it was just that >>> your >>> @LocalClient wasn't getting discovered. If you have something that >>> reproduces it, I'll definitely give it a look ASAP. >>> >> >> OK, I'll check again (I "fixed" the issue by--at least from what I >> remember--including all the fields; I'll try removing them again). Your >> idea that it was simply that the LocalClient wasn't being discovered is >> also >> possible; I may have been inadvertently burned by this. >> >> Thanks for the due diligence. :-) > > No worries. At the very least it's a "lack of information" issue. I just > added some logging there so right after "Created Ejb..." it will print out > every LocalClient it processed. So hopefully that will help protect against > situations like this. > > > -David > >
