-
1. Re: entitymanager after passivation
luxspes Aug 27, 2009 1:37 PM (in response to cremersstijn)Does it fail silently? Have you tried using something like log4jdbc to see if it is (or not) sending the DELETE statement to the database?
-
2. Re: entitymanager after passivation
cremersstijn Aug 27, 2009 1:43 PM (in response to cremersstijn)it isn't sending the delete statement.
Is it possible to extended the timeout time of the passivation? or the set it off?
i'm using jboss 4.2.2-GA as application server
-
3. Re: entitymanager after passivation
swd847 Aug 27, 2009 1:54 PM (in response to cremersstijn)What happens if you do a merge of the entities after passivation?
-
4. Re: entitymanager after passivation
asookazian Aug 27, 2009 5:32 PM (in response to cremersstijn)
Stijn Cremers wrote on Aug 27, 2009 13:43:
Is it possible to extended the timeout time of the passivation? or the set it off?yes: http://www.jboss.org/community/wiki/Ejb3DisableSfsbPassivation
But remember why SFSB passivation exists in the first place (there is no SFSB pooling in the ejb container, so it's a memory consumption optimization to serialize to disk every x min's after no activity)
You should try to trouble-shoot this first before disabling passivation.
-
5. Re: entitymanager after passivation
asookazian Aug 27, 2009 5:36 PM (in response to cremersstijn)Scan the logs for proof of passivation and activation (you should be able to add @PrePassivate and @PostActivate callback methods in your SFSFB and add log statements and/or debug brkpts in them).
Sounds like the activation (de-serialization from disk to memory) may not be occurring or an exception is being thrown. This should help. If you don't want to wait 10 min's, you can tweak the timeout for that particular SFSFB as well. Read my link.