[JBoss-user] [Persistence & CMP/JBoss] - Re: jboss 3.2 to jboss 4.0 migration problem: requests execu

2005-05-18 Thread ffaure
Hi all, We finally found a solution for our problem: - we changed our timestamp columns from date type to timestamp type - we changed the trigger to be effective only when a new timestamp value is not brought by the insert or update request itself: CREATE OR REPLACE TRIGGER UPD_INS | | BEF

[JBoss-user] [Persistence & CMP/JBoss] - Re: New

2005-05-03 Thread ffaure
Hi Roger, Thanks for your response. But I'm afraid my problem is not related to servlet specifications. In fact, the discussion is going on this post: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=63326 An the problem is related to date mapping problem and triggers... thanks again, fr

[JBoss-user] [Persistence & CMP/JBoss] - Re: jboss 3.2 to jboss 4.0 migration problem: requests execu

2005-05-02 Thread ffaure
Hi, Alex, thanks a lot for your help. I've been following your advises and it seems to be clearer for me. The problem is that our tstamp column is a DATE column. When I manually try an insert then an update with java.sql.Timestamp, it does not work. If I execute it with a java.sql.Date, it work

[JBoss-user] [Persistence & CMP/JBoss] - Re: jboss 3.2 to jboss 4.0 migration problem: requests execu

2005-04-29 Thread ffaure
More information: I've printed my tstamp info at ejbPostCreate time (juste after the insert request) Then, I've printed it too at ejbStore time. It is called just before the update that generates the exception. What is surprising me is that the values are equals! I have to ideas (with really no

[JBoss-user] [Persistence & CMP/JBoss] - Re: jboss 3.2 to jboss 4.0 migration problem: requests execu

2005-04-29 Thread ffaure
Hi Alex, Thanks a lot for your response, even if it means bad news for me... We have to change our optimistic locking management for all our applications (the problem is more for other applications that don't run under jboss...) However, I'm worrying because I just tried to remove the triggers o

[JBoss-user] [Persistence & CMP/JBoss] - Re: 3.2 to 4.0 problem: Optimistic locking whith tstamp

2005-04-29 Thread ffaure
I've realized my problem is perharps not linked to the commit time execution of request but with the optimistic locking management: In xdoclet, I've declared this stuff for the entity bean concerned: * @jboss.optimistic-locking * timestamp-column="TSTAMP" * field-name="tstamp" * column

[JBoss-user] [Persistence & CMP/JBoss] - jboss 3.2 to jboss 4.0 migration problem: requests executed

2005-04-28 Thread ffaure
Sorry but there was a problem with the title of my previous post that doesn't make it expicit. I add this one to give it a title. But you can respond here: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=63325 Sorry for the inconvenience, Fred View the original post : http://www.jbos

[JBoss-user] [Persistence & CMP/JBoss] - New

2005-04-28 Thread ffaure
Hello everybody, This is my first post and I'm afraid my problem is not trivial. I've got an application with session and cmp entity beans. It's running fine on JBoss 3.2.2 But I've got an exception in rare but reproductible cases on JBoss 4.0.1sp1: 12:48:16,056 DEBUG [EjbEcSituations] Executi