A Petshop or a EJB flaw?
1 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Noel_Byron
Posted On:   Tuesday, April 2, 2002 04:41 AM

Hi! We have a problem with Petstore running in a IBM WebSphere environment. If you add something to the cart you are redirected to the cart view. If you reload (using the reload browser button) the view everything works fine. But if you press the reload button very fast (up to 10 times a second :o) petshop breaks with the following error messages: com.sun.j2ee.blueprints.petstore.control.exceptions.GeneralFailureException: CORBA OBJECT_NOT_EXIST 0 No; nested exception is: org.omg.CORBA.OBJECT_NOT_EXIST: minor code: 0 completed: No ... That is (IMHO) because it tries to access a method of a session bean concurrently (with the same reference)? If so, does that mean that you can not a   More>>

Hi!



We have a problem with Petstore running in a IBM WebSphere environment. If you add something to the cart you are redirected to the cart view. If you reload (using the
reload browser button) the view everything works fine. But if you press the reload button very fast (up to 10 times a second :o) petshop breaks with the following error messages:

com.sun.j2ee.blueprints.petstore.control.exceptions.GeneralFailureException: CORBA OBJECT_NOT_EXIST 0 No; nested exception is:

org.omg.CORBA.OBJECT_NOT_EXIST: minor code: 0 completed: No

...



That is (IMHO) because it tries to access a method of a session bean concurrently (with the same reference)? If so, does that mean that you can not add the reference to a session bean to a web session (because webpages will access the bean concurrently)? Do you think it is ok to throw a exception instead of synchronizing the access to a session bean? Why the heck are session beans not synchronized? We are quite perplexed...


Kind regards,

Noel

   <<Less

Re: A Petshop or a EJB flaw?

Posted By:   Bozidar_Dangubic  
Posted On:   Tuesday, April 2, 2002 05:26 AM

why are you hitting the reload button 10 times a second??? even though applications should be architected to guard against idiot users, hitting the reload button 10 times a second definitely does not qualify as something that most QA people will test. and to answer your question "Why the heck are session beans not synchronized?", they are. stateful session beans do not need to be synchronized as they are dedicated to a single client. stateful session beans are pooled and need not be synchronized since they are always serving a single client at any one time during the execution of the application.
About | Sitemap | Contact