Hi all, I've run into the following situation in a Solaris 8/JBoss 2.4.1/Tomcat-3.2.3/JDK 1.3.1 environment
I have a sessionbean with required transaction level which first deletes an EJBObject and subsequently creates a new EJBObject using the same PK values. (updating values directly IS an option but makes things slightly more complicated) The create throws a javax.lang.TransactionRolledbackException with java.lang.IllegalStateException nested, and the message is "INSERTING AN ALREADY EXISTING BEAN, ID = ..." To verify that the bean is actually being removed, I tried a findByPrimaryKey(<PK>) just before the create, and sure enough, it is not found. Redeploying the bean jar will solve the problem on the first subsequent transaction as long as I perform the remove as <homeobject>.remove(<handle>), which leads me to believe that container caching is playing a role here. Using <homeobject>.remove(<PK>) and <remote>.remove() will not work even with the redeploy. Has anyone encountered this type of behavior before, and/or know of any ways around it without a major change in the session bean's transaction structure? Any help would be greatly appreciated. Thanks, Jon _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
