6 Replies Latest reply on Nov 15, 2001 8:32 PM by davidjencks

    updation problem in BMP

    vkaladhar

      Hello,
      I have a problem when i am doing updation in BMP. when i am issuing a updation call, i am not getting any errors, records are getting updated, when i stop and start the jboss server. If i don't stop, i am unable to see the updated rows, and further i unable to do any operation on that particular table. Please suggest how to solve it as early as possible.

      bye
      -kaladhar

        • 1. Re: updation problem in BMP
          danch1

          Make sure that you're bean's methods are defined as transaction Requires or RequiresNew (or Mandatory)

          • 2. Re: updation problem in BMP
            vkaladhar

            thanks for ur reply, but i didn't get what do u mean. you mean trans-attribute in ejb-jar.xml.
            <trans-attribute>Required</trans-attribute>

            • 3. Re: updation problem in BMP
              wai

              I have encounter similar problem as well.
              It appears that the bean issue an update SQL
              statement without performing a commit afterward.

              When you client keep calling the same bean,
              the Jboss would allocate addition db connections
              from the pools.

              • 4. Re: updation problem in BMP
                danch1

                Yes, that should work.

                Another possibility: make sure you're closing all of your JDBC resources (Connection, Statement, any ResultSet objects). It's usually best to do this in a finally clause at the end of a try block around your database code.

                • 5. Re: updation problem in BMP
                  luctran

                  You should change to commit option A, B, or D in jboss.xml file or standardjboss.xml file. It will work.

                  • 6. Re: updation problem in BMP
                    davidjencks

                    Commit option determines caching and whether updates made by other apps are visible, not anything about when and if commits happen. Since the connection pools were running low most likely the connections were not getting closed before tx commit.