Hi
first can youy check against 1.6.0 and ensure you call it through EJB business interface and not internally. secondly can you reproduce it in a unit test (it is 100% openejb code)? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-02-13 14:25 GMT+01:00 Olivier Paquet <[email protected]>: > Hello,We are using Stateful EJB and Tomee 1.5.2-Plus with the following > stateful configuration accessTimeout = 30 seconds bulkPassivate = 100 > cache = org.apache.openejb.core.stateful.SimpleCache capacity = 1000 > frequency = 30 passivator = > org.apache.openejb.core.stateful.SimplePassivater timeOut = 1After > invoking the @Removed: -the @PreDestroy is calledbut after 1 minute > the : - the @PreDestroy is called a second time - Feb 13, 2014 > 2:18:11 PM > org.apache.openejb.core.stateful.StatefulContainer$StatefulCacheListener > timedOut So apparently the instace is not removed after calling the > @Remove instance.Do you have some suggestions for the current stateful > container configuration?Ar there any known issues?Isn't it right that the > instance will be immediatly removed after calling @Remove > method?Regards,Olivier Paquet > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Stateful-EJB-not-removed-after-Remove-annontation-tp4667763.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
