> well i never use manager. i use tomee mvn plugin: mvn clean package > tomee:run [test phase] [quit, work, restart]
I don't use maven jet. But as I see it also uses server undeploy deploy actions. As my ant project does. Or drop in war does. Or manager. >From documentation: reloadOnUpdate means to reload the context (webapp). It means undeploying/redeploying it. > This imo indicates some nasty ClassLoader or scanning issue Maybe. It could be a bug in openejb threadpool unexpected exception handler. If it is redefined. > Afaik it's not defined whether you should get this log on the server at all. Most servers I know don't log it. You might work around it by writing a CDI Extension which adds an @LogExceptions kind of Interceptor to those beans. Or just add the interceptor to to those EJBs yourself manually. Before I used Glassfish and it loged all unexpected exceptions. The odd thing is that unexpected exceptions are loged to localhost.date file for JSP pages even when the app gets redeployed. I will try to do an CDI Extension. Thanks for advice. On Fri, May 31, 2013 at 9:15 AM, Mark Struberg <[email protected]> wrote: > > > There are imo two different things in the game here: > > 1.) This imo indicates some nasty ClassLoader or scanning issue > > 2.) Afaik it's not defined whether you should get this log on the server > at all. Most servers I know don't log it. You might work around it by > writing a CDI Extension which adds an @LogExceptions kind of Interceptor to > those beans. Or just add the interceptor to to those EJBs yourself manually. > > > LieGrue, > strub > > >________________________________ > > From: Dmitrijs Litajevs <[email protected]> > >To: [email protected] > >Sent: Thursday, 30 May 2013, 15:08 > >Subject: Re: Remote exceptions logging > > > > > >I start the server. Copy app.war to the webapps dir. It deploys > >Then call the @Remote bean form my se client. Error shows correctly in > >catalina.out > > > >Then i change something in the method that i called. For example error > >description. > >And copy app.war ti webapps dir again. It deploys. > >Then call the @Remote bean form my se client. Is does not show up in any > >log again. > > > > > > > >On Thu, May 30, 2013 at 4:03 PM, Romain Manni-Bucau > ><[email protected]>wrote: > > > >> i didn't get the issue... > >> > >> > >> *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 Dmitrijs Litajevs <[email protected]> > >> > >> > > On 1.6.0-SNAPSHOT-20130529.041208-84-plus the problem occurs when > the > >> app > >> > is redeployed. > >> > > >> > > I build app WAR with netbeans ant. And copy WAR to webapps folder. > >> > > If I reboot the server the logs are shown correctly again. > >> > > >> > Any way to fix this? > >> > > >> > > >> > > >> > On Thu, May 30, 2013 at 3:44 PM, Romain Manni-Bucau > >> > <[email protected]>wrote: > >> > > >> > > because you neevr know if the ejb is local or remote so it was the > >> > provided > >> > > solution to keep the same code i think > >> > > > >> > > *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 Chris.Christo <[email protected]> > >> > > > >> > > > sorry that meant to say 'custom runtime exception subclasses'. > >> > > > > >> > > > Chris Christo > >> > > > > >> > > > --- > >> > > > Twitter: https://twitter.com/ChrisChristo7 > >> > > > Tumblr: http://chrischristo7.tumblr.com > >> > > > LinkedIn: http://uk.linkedin.com/in/chrischristo > >> > > > GitHub: https://github.com/ChrisChristo > >> > > > > >> > > > On 30 May 2013, at 12:14, "Chris.Christo" <[email protected] > > > >> > > wrote: > >> > > > > >> > > > > Just a question I have related to this; > >> > > > > > >> > > > > Why do your own customer runtime exception subclasses get > wrapped > >> in > >> > an > >> > > > EjbException when the ejb beans are local? > >> > > > > Surely the caller will have the exception class in its > classpath? > >> > > > > > >> > > > > Chris Christo > >> > > > > > >> > > > > --- > >> > > > > Twitter: https://twitter.com/ChrisChristo7 > >> > > > > Tumblr: http://chrischristo7.tumblr.com > >> > > > > LinkedIn: http://uk.linkedin.com/in/chrischristo > >> > > > > GitHub: https://github.com/ChrisChristo > >> > > > > > >> > > > > On 30 May 2013, at 07:19, vhubuo <[email protected]> > wrote: > >> > > > > > >> > > > >> 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. > >> > > > > > >> > > > > >> > > > > >> > > > >> > > >> > > > > >
