I have resolved my problem. My stateful session was declared as Bean user Transaction in the DD. Changed to Container transaction and now works fine.
I really not need a Bean User Transaction; my stateful session is used only to "emulate" a http session accordint to the suggestion of some "best pratics". the only problem that persist is: 10:16:52,486 WARN [AbstractInstanceCache] Unable to passivate due to ctx lock, id=e0220bjp-4 But i dont' understand who set a lock (or not release a lock), maybe a bug just fixed because this append only on jboss 3.2.3; using 3.2.5 and 3.2.6RC2 no problem occurs. A question: what appends to a stateful session not removed when the jboss server shutdown ? What appends to the next startup ? Thank You! Roberto View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3850739#3850739 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3850739 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
