4 Replies Latest reply on Jul 26, 2002 11:39 AM by jlmartinez

    Massive querys problem

    jlmartinez

      I sent more or less 1000 querys(inserts, updates) in a transaction, the aplication don't reported any exception. but the database was not updated.
      sometimes in the server console appear the next warning:

      WARN [LocalTxConnectionManager$LocalConnectionEventListener] prepare called
      on a local tx. You are not getting the semantics you expect!

      I'm using JBoss 3.0.0 with PostgresDB.

      what can be happening?

        • 1. Re: Massive querys problem
          dsundstrom

          Try 3.0.1.

          • 2. Re: Massive querys problem
            jlmartinez

            We've tested with the last version, but We obtain the same result.

            I think that the problem is the pool.

            Thank you

            • 3. Re: Massive querys problem
              dsundstrom

              I still think this is a bug we fixed already. Can you try cvs Branch_3_0 or HEAD? If that doesn't fix it, post a bug report.

              • 4. Re: Massive querys problem
                jlmartinez

                I'm trying whit jboss-3.0.1RC1, but I' have problems with JAVA_OPTS, When I put -D Properties in run.bat, the server don't start.

                the line in run.bat is:
                set JAVA_OPTS=%JAVA_OPTS% -Dproject.name=atenea .....

                The exception is:
                10:51:18,129 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.x
                ml
                10:51:18,129 INFO [AbstractDeploymentScanner$ScannerThread] Running
                10:51:18,259 ERROR [MainDeployer] could not start deployment: file:/C:/Java/jboss-3.0.1RC1
                /server/atenea/conf/jboss-service.xml
                java.lang.NoSuchMethodError: org.apache.log4j.Category.getDefaultHierarchy()Lorg/apache/lo
                g4j/Hierarchy;
                at org.apache.log4j.xml.DOMConfigurator.configure(DOMConfigurator.java:608)

                And the same error occur if I fix debugger properties.

                I don't understand the relation whit Log4J?

                Thank you.