On Jan 26, 2012, at 11:25 PM, AndyG wrote: > Also +1. Thanks David. > > As mentioned before, in production adding something like > -Dopenejb.log.factory=log4j is not as easy as it sounds. Especially if has > to be done by a 'user' over the wire.
Note, log4j will likely be cut from the distro so there'd still be a step for adding it. Two possible solutions there: 1) Find some way to easily add log4j either via another server binary or via network install at startup. 2) Find a way to easily get the log output of JULI to match the existing logging so you could switch. I am curious on which log messages you parse. We might want to test them. I've also had the thought more than once that it would be nice to issue CDI events during the various internal processes that OpenEJB does. Being able to consume those events could be all sorts of useful. > I don't just drop trunk into production on a whim, but if all my tests pass > and the changes are significant and stable then I usually push out the > updates pretty quickly with an Install4j patch. > > As things progress there is a current potential of pushing out well over 200 > servers and thousands of clients. I swear I will find time for a descriptive > article on how I am successfully using OpenEJB in a real world high volume > AOI scenario!!! That's awesome! I'm super curious as to which parts of OpenEJB you use the most aside from JMS. -David
