well, ATM the 1.6.0-SNAPSHOT is pretty stable excepted regarding openjpa (we are waiting a commit from them to get back stable). So if you use openjpa stay on 1.5.x otherwise you can take the today snapshot.
*Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/5/30 vhubuo <[email protected]> > Yes. The RuntimeExceptions are wrapped into EJBException for the client. > And > I see the stack trace on client. But I don't see the stack trace in any of > server log files. > > So my question is how does TomEE log unexpected exceptions in stateless > beans exposed via remote annotation ? And is there any configuration > available. > > I use a "clean" installation of 1.5.2 of the server without any > configuration. > > >can you check with the snapshot, i just tried with 1.6.0-SNAPSHOT > > On 1.6.0-SNAPSHOT it works correctly. > > I get: > май 30, 2013 9:14:57 AM > org.apache.openejb.core.transaction.EjbTransactionUtil > handleSystemException > SEVERE: EjbTransactionUtil.handleSystemException: user defined exception > java.lang.UnsupportedOperationException: user defined exception > > What are your recommendations on production usage? > > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Remote-exceptions-logging-tp4663282p4663336.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
