Each call to a stateless session bean could be handled by a different bean instance.
"Stateless" means there should be no client state maintained by the bean. You
shouldn't be keeping a database connection or statement open accross bean method
calls. If you cannot think of another way of implementing your algorithm, try using a
stateful session bean.
--Victor
René Rolander Nygaard wrote:
> Since no one tries to crack the puzzle, i will give some more information.
>
> Through our speed-testing we are seeing more strange behaviors.
> It seems as JBoss looses the reference to an object if you speed-clicks.
> This can only mean that the problems occurs because the same session is
> trying to access the same object more than once.
>
> The scenario again:
> Session A loads page 1
> page 1 initializes and starts
> page 1 traverse the lists etc.
> page 1 closes all db connections etc.
>
> Now if you click to reload the page before it finishes this happens:
> Session A loads page 1
> page 1 initializes and starts
> page 1 traverse the lists etc. Session A loads page 1 again!
> page 1 initializes
> page 1 traverse the lists etc.
> *page 1 tries to close all db connections etc.
> page 1 closes all db-connections.
>
> * This fails ! Could it be that the reference from the JSP->bean->stateless
> session bean fails because the same session makes 2 reference to the same
> object ? (This must be a bug!)
> My collegue argues that in theory we can not be 100% sure that the reference
> we get to a stateless session bean is the same when we start a "transaction"
> (starts the page) - as the one we have at the end of the transaction.
> If this is the case, how can we make sure this is the case ?
> This is most likely to occur in heavy-load systems, and i guess most
> stress-test systems to not test for the correct result !?
>
> Please help us out here!!!
>
> - René Nygaard
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
