Re: [jBoss-User]

[Paolo Biondi]

Ok, maybe I can explain it much better with the server.log listings.   I have a routine that excute over several entity beans. When I excute it as a client and I made a set method over an entity, it makes the UPDATE sql statement you can see below:   [LotBean] RMI TCP Connection(4)-192.168.2.101 SELECT id,id FROM Lots WHERE priority > -1 ORDER BY id [LotBean] Lot Activate: 972511805358 [LotBean] RMI TCP Connection(4)-192.168.2.101 SELECT id , queuedTime , machineId , insertTime , JobId , residualTime , priority , exitTime , phase , outPlant FROM Lots WHERE id = biscotti1 [LotBean] Lot Load: 972511805388 [LotBean] RMI TCP Connection(4)-192.168.2.101 UPDATE Lots SET id = biscotti1 , queuedTime = 0 , machineId = m02 , insertTime = -100 , JobId = biscotti , residualTime = 7 , priority = 0.0 , exitTime = 0 , phase = 1 , outPlant = 0 WHERE id = biscotti1 [LotBean] RMI TCP Connection(4)-192.168.2.101 SELECT COUNT ( * ) FROM Lots WHERE id = biscotti1 [LotBean] Lot Activate: 972511808803 [LotBean] RMI TCP Connection(4)-192.168.2.101 SELECT id , queuedTime , machineId , insertTime , JobId , residualTime , priority , exitTime , phase , outPlant FROM Lots WHERE id = biscotti5 [LotBean] Lot Load: 972511808823 [LotBean] RMI TCP Connection(4)-192.168.2.101 UPDATE Lots SET id = biscotti5 , queuedTime = 0 , machineId = m01 , insertTime = 0 , JobId = biscotti , residualTime = -1 , priority = 0.0 , exitTime = 0 , phase = 0 , outPlant = 1 WHERE id = biscotti5 when I excute the same routine as a method of a Stateful Session Bean called by another small client it doesn't execute the UPDATE sql statement you can see:   [LotBean] RMI TCP Connection(4)-192.168.2.101 SELECT id,id FROM Lots WHERE priority > -1 ORDER BY id [LotBean] Lot Activate: 972510819320 [LotBean] RMI TCP Connection(4)-192.168.2.101 SELECT id , queuedTime , machineId , insertTime , JobId , residualTime , priority , exitTime , phase , outPlant FROM Lots WHERE id = biscotti1 [LotBean] Lot Load: 972510819350 [LotBean] RMI TCP Connection(4)-192.168.2.101 SELECT COUNT ( * ) FROM Lots WHERE id = biscotti1 [LotBean] Lot Activate: 972510819431 [LotBean] RMI TCP Connection(4)-192.168.2.101 SELECT id , queuedTime , machineId , insertTime , JobId , residualTime , priority , exitTime , phase , outPlant FROM Lots WHERE id = biscotti5 [LotBean] Lot Load: 972510819451 and only when the routine ends, the final state of the entity beans involved is stored by the UPDATES sql statements:   [InsaSessionBean] RMI TCP Connection(4)-192.168.2.101 UPDATE Lots SET id = biscotti1 , queuedTime = 0 , machineId = m02 , insertTime = -100 , JobId = biscotti , residualTime = 7 , priority = 0.0 , exitTime = 0 , phase = 1 , outPlant = 0 WHERE id = biscotti1 [InsaSessionBean] RMI TCP Connection(4)-192.168.2.101 UPDATE Lots SET id = biscotti5 , queuedTime = 0 , machineId = m01 , insertTime = 0 , JobId = biscotti , residualTime = -1 , priority = 0.0 , exitTime = 0 , phase = 0 , outPlant = 1 WHERE id = biscotti5 [InsaSessionBean] RMI TCP Connection(4)-192.168.2.101 UPDATE Lots SET id = biscotti6 , queuedTime = 0 , machineId = m01 , insertTime = 0 , JobId = biscotti , residualTime = -1 , priority = 0.0 , exitTime = 0 , phase = 0 , outPlant = 1 WHERE id = biscotti6 This have not any utility because if i made a change in my beans from another bean I want this changes is immediatly made into the databese too. this is important to me because i want the Stateful Session bean method works absolutely like the client I show you first. But actually it doesn't!!! I don't know if i must set some parameter to avoid this problem..... If you understand the problem can you explain me how i can force the UPDATEs ?   thank you in advance,   paolo.   ----- Original Message ----- From: marc fleury To: jBoss Sent: Wednesday, October 25, 2000 6:26 PM Subject: RE: [jBoss-User] paolo this is not clear at all, please re-explain the problem   maybe it is just me ??? marc   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Paolo Biondi Sent: Wednesday, October 25, 2000 3:33 PM To: [EMAIL PROTECTED] Subject: [jBoss-User] Hi everyone, I want to explain you something that happened to me, with Jboss PROD3: when I excute a routing as a client application over several entity bean all work properly, but insted if I excute the same routine as another entity bean in the same container where the worked entity bean are instanced the UPDATE sql statements are not performed .... and they are performed only at the end of the session.   Maybe I must set some parameters ... to avoid the problem? If anyone have some suggestion for me, I want to thank him in advance.   Paolo Biondi.