hi there. it might be worth looking in the jboss forums and mailing lists for answers...
FORUMS ====== Stateless: http://www.jboss.org/forums/thread.jsp?forum=47&thread=1968 Stateful: http://www.jboss.org/forums/thread.jsp?forum=47&thread=2285 JBOSS-USER mailing list ========== http://www.mail-archive.com/[email protected]/msg11507.ht ml http://www.mail-archive.com/[email protected]/msg11755.ht ml [definitive answer] In the meantime, this error has been fixed in jboss-2.4.3 and can be found at http://sourceforge.net/project/showfiles.php?group_id=22866 cheers oliver www.pogo-tech.com > -----Original Message----- > From: Noels Jeroen [mailto:[EMAIL PROTECTED]] > Sent: 09 October 2001 13:56 > To: '[EMAIL PROTECTED]' > Subject: [JBoss-user] stateless session bean pooling seems to have > disappeared in jboss2.4????? > > > hi, > > We have been using jboss 2.2.1 for about half a year, and I > think this a > great product. Recently we upgraded to jboss 2.4.1, without > any problems > whatsoever. However, it appears to me that jboss 2.2.1 and jboss 2.4.1 > behave very differently in dealing with the pooling of > stateless session > beans: I deployed exactly the same beans in both jboss > versions, with the > same (in fact: the default) container configurations and investigated > jboss-logging and some customized logging in our beans about their > life-cycle events. > In 2.2.1, this kind of logging convinces me that stateless > session beans are > indeed pooled and reused. However it seems that in 2.4.1 this > is no longer > the case: no-arg-constructors, setSessionContext() and > ejbCreate() methods > are called over and over again, even when I reduce the > pool-size to say 2 > instances! please help!!! > > Jeroen Noels > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
