The testcase would set a class flag in the bean class if an exception occurred in the setSessionContext method. When the unit tests run and invoke a method on a bean, the bean would check this flag in its only business method and throw an exception.
The simplest intermediate fix is to delay the start of the feeder timer by 10 seconds or so. More exacting startup criteria can be dealt with as needed. There is another issue with how the feeder interacts with the pool. The getCurrentSize is really the pool free instance count. Only on startup is this also the pool count. After the pool has been filled once, (MaximumSize - getCurrentSize) is no longer how many instances need to be added to the pool. Say MaximumSize is 10 and the pool is filled by the feeder. Next 10 clients invoke methods concurrently and take the pool free count to 0 and getCurrentSize is also 0. The feeder then wakes up and puts 10 more instances into the pool. The client invocations next complete and all 10 instances are discarded as the pool is seen to be full. The AbstractInstancePool is not counting instances correctly when another thread is adding instances. ----- Original Message ----- From: "Vincent Harcq" <[EMAIL PROTECTED]> To: "'Scott M Stark'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Sunday, December 30, 2001 3:17 AM Subject: RE: [JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb/plugins AbstractInstancePool.java MessageDrivenInstanceInterceptor.java StatefulSessionInstanceInterceptor.java StatelessSessionInstanceInterceptor.java _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
