Folks at jBoss I am having real trouble with jBoss transactions and 'spurious' ejbStore(). I have an Account entity bean that has a balance that must be updated. I noticed in by debug statements that a set of Account's, which were under the control of a single transaction, were been updated correcty until the very last step. What happens is the following: Somewhere in my code I create an instance of an Account bean which I only use for "read only" (to get the account number and balance). ejbStore() is however being called on this bean, even though no transaction REQUIRED methods are ever called on this "read only" instance of the Account bean. The correct balance in the database is then over written. I then went into ejb-jar.xml and made sure that all bean remote and home interfaces, using * wildcard, (hence all methods in all beans ) were marked as NOT SUPPRORTING transactions. I then went and selectively set a few methods ( account.updateBalance() for one ) to REQUIRED. jBoss now hangs somewhere on the transaction even though jBoss seems to still be working (I see passivation of overaged bean messages etc). My client also hangs waiting for a reply from jBoss. No exceptions thrown anywhere. When I try stop jBoss using ^C it then really hangs and I have to kill it. I am using the this pointer to figure out which instance of bean is being called when. No REQUIRED transaction methods are ever called on the 'read only' instance on the Account bean but ejbStore is. What to do? (I am using jBoss-2.0_FINAL.zip (4.19M) on Win 2000 ( Production is on Linux )) -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] List Help?: [EMAIL PROTECTED]
