1 2 Previous Next 19 Replies Latest reply on Sep 19, 2010 2:15 AM by abdulrahman Go to original post
      • 15. Re: jbpm 4.3 - org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
        jedizippy

        Hi Ronald,

         

        I take on board your comments. However the point I was trying to make is that as there are no docs on JTA/transactions for jBPM then the user community is left to try and figure it out for themselves (most likely the hard way). Most likely the only people who would know ths information are the people who implemented it. And as they have not documented it in any form (for whatever reason) then of course that effectively means that no-one will likely be able to use it unless they have the luxury of the time to sit and go through all the code to try and figure out what it is doing.

         

        It seems rather strange to me that the JobExecutor seems to be looked on as some kind of usual use case. The whole point of BPM is to handle exactly these kind of asynchronous long running tasks. Regardless of which server you are running on it should not be relevant as this should be taken care of by in the hibernate config (or at least that is my understanding of how this application should work). If not then it simply cant be ported to other non-JBoss servers without custom code mods which would make no sense (maybe this is the way to get people onto JBoss )

         

        So a simple question. Should I use jbpm.tx.jta.cfg.xml or jbpm.tx.hibernate.cfg.xml should surely be a simple question to answer for anyone involved with the product. As this question is irrelavent of the app server. Or are people just running very simple standalone apps with basic hibernate transactions - so this is not enterprise then ?.

         

        Just seems odd to me that the core guys are spending time implementing loads of new functionality when the basics are not deocumented well enough for people to use them. I did try to mail the project lead directly regarding this simple question on JTA but he didnt see fit to answer. So I guess you can draw your own conclusion from that. We are facing lots of issues around Id generation, constraint violations to name just a few. I am sure they are all related to this JTA question. But it looks like JBPM will go in the bin as if we can solve it in the next few days then we wont have any other choice to dump it and implement another solution.

         

        I appreciate your time as always.

         

        Regards

        martin

        • 16. Re: jbpm 4.3 - org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
          kukeltje

          Well, from what I could determine from the different configs is: (and this does not yield any more new info for me)

          - use JTA if you want jBPM to participate fully in JTA

          - use 'normal' if you want to just have jdbc transactions.

           

          In the first case do not forget to configure

           

                  <property name="hibernate.transaction.factory_class">org.hibernate.transaction.JTATransactionFactory</property>
                  <property name="hibernate.transaction.manager_lookup_class">org.hibernate.transaction.JBossTransactionManagerLookup</property>
                  <property name="jta.UserTransaction">UserTransaction</property>
          
          

           

          correctly in your hibernate config specific for your server. That is all I can find out without digging to much in. Does this shed new light on it for you or doesn't it? (I think the latter)

          • 17. Re: jbpm 4.3 - org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
            jedizippy

            Hi,

             

            We already had those specified (but the Weblogic versions of course). JTA seems to be behaving correctly. My issue is with this new config that is documented in the docs but which of course is JBoss specific. Seems we are on a road to nowhere regarding that however.

             

            Implementing our own ID Generator seems to have solved the constraint violations in the short term but now we are onto the next issue with duplicated values in process variables. Again trying to reproduce it is hard in an async environment. It would seem that once the JobExecutor is introduced into the equation then all the bugs come out to play !. But then it would seem that there is no test cycle including the JobExecutor so I guess that is to be expected !.

             

            We are starting end to end testing this week so we will see what else comes out..

             

            Regards

            Martin

            • 18. Re: jbpm 4.3 - org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
              mukh.prac

              Hi All,

               

              Thanks for sharing the information. I am facing exactly similar issues while dealing with jBPM 4.3 JobExecutor and asynchronous calls.

              I am using HSQL DB and would be switching to DB2 in a day or two.

               

              Could you please share any workarounds / solutions you used (e.g updating execution.hbm file etc.) to overcome the problem.

              I am facing various kinds of Hibernate issues, some of them being:

              ConstraintViolationException

              StaleObjectStateException

              Could not execute JDBC Batch update, etc.

               

              Some steps I have already tried out:

              Update the jbpm.cfg.xml file by adding jta and hiberate related mapping files.

              Using continue  = sync, async / exclusivre, but all options throw the same error.

               

              Please help me on the same. Its needed on urgent basis.

               

              Many thanks in advance,

              Prachi

              • 19. Re: jbpm 4.3 - org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
                abdulrahman

                Hi Prachi,

                 

                I am facing the same issue but in JBPM 4.2 and using oracle as the database. Did you find any solution for this?

                 

                Regards

                Abdul

                1 2 Previous Next