4 Replies Latest reply: Jul 3, 2012 4:31 AM by 943352 RSS

    DatabaseSequenceFilter initialization stuck for 20mins

    943352

      This line is taking a long time.
      seqFilter = new DatabaseSequenceFilter(connection);
      Any standard solutions?

        • 1. Re: DatabaseSequenceFilter initialization stuck for 20mins
          rp0428
          >
          DatabaseSequenceFilter
          >
          Go back and reread the reply in the other forum where I ask you to post here.
          Database operations take a long time

          Follow the instructions I gave you in the other forum. You are wasting people's time in that other forum because they don't realize you have a Java problem and not a SQL or PL/SQL problem.
          • 2. Re: DatabaseSequenceFilter initialization stuck for 20mins
            943352
            I have 11gR2 and using JDK 1.6.32.

            Also while this filter is getting initialized for 20 mins a lot of these flash by:

            1005869 [Timer-0] DEBUG com.mchange.v2.resourcepool.BasicResourcePool - Checking for expired resources - Mon Jul 02 04:34:52 PDT 2012 [com.mchange.v2.resourcepool.BasicResourcePool@1b7b407]
            1005870 [Timer-0] DEBUG com.mchange.v2.resourcepool.BasicResourcePool - BEGIN check for expired resources. [com.mchange.v2.resourcepool.BasicResourcePool@1b7b407]
            1005870 [Timer-0] DEBUG com.mchange.v2.resourcepool.BasicResourcePool - FINISHED check for expired resources. [com.mchange.v2.resourcepool.BasicResourcePool@1b7b407]
            1012875 [Timer-1] DEBUG com.mchange.v2.resourcepool.BasicResourcePool - Checking for expired resources - Mon Jul 02 04:34:59 PDT 2012 [com.mchange.v2.resourcepool.BasicResourcePool@1082277]
            1012876 [Timer-1] DEBUG com.mchange.v2.resourcepool.BasicResourcePool - BEGIN check for expired resources. [com.mchange.v2.resourcepool.BasicResourcePool@1082277]
            1012876 [Timer-1] DEBUG com.mchange.v2.resourcepool.BasicResourcePool - FINISHED check for expired resources. [com.mchange.v2.resourcepool.BasicResourcePool@1082277]
            1015554 [Timer-2] DEBUG com.mchange.v2.resourcepool.BasicResourcePool - Checking for expired resources - Mon Jul 02 04:35:01 PDT 2012 [com.mchange.v2.resourcepool.BasicResourcePool@a34b91]
            1015555 [Timer-2] DEBUG com.mchange.v2.resourcepool.BasicResourcePool - BEGIN check for expired resources. [com.mchange.v2.resourcepool.BasicResourcePool@a34b91]
            1015555 [Timer-2] DEBUG com.mchange.v2.resourcepool.BasicResourcePool - FINISHED check for expired resources. [com.mchange.v2.resourcepool.BasicResourcePool@a34b91]
            1255833 [Timer-0] DEBUG com.mchange.v2.resourcepool.BasicResourcePool - Checking for expired resources - Mon Jul 02 04:39:02 PDT 2012 [com.mchange.v2.resourcepool.BasicResourcePool@1b7b407]
            1255833 [Timer-0] DEBUG com.mchange.v2.resourcepool.BasicResourcePool - BEGIN check for expired resources. [com.mchange.v2.resourcepool.BasicResourcePool@1b7b407]
            • 3. Re: DatabaseSequenceFilter initialization stuck for 20mins
              gimbal2
              Seems like regular pool sweeping, nothing out of the ordinary (other than that it is logged at debug level in stead of trace level). Your problem is not with the pool, it is somewhere else. Most likely outside of the code as has been said in your previous thread. You're not going to offload the responsibility for providing an answer, you are only going to solve this if you make the effort yourself. You have one advantage over all others here: you have access to the stuff and I hope you have a bunch of colleagues with which you can search for the root of the issue.
              • 4. Re: DatabaseSequenceFilter initialization stuck for 20mins
                943352
                While I agree my initial post was sloppy, I did isolate it down to one line now and that line is a constructor call that I can't get inside of to put any debug hooks.
                I also found a hit for exact same problem with the same time delay: http://stackoverflow.com/questions/7384783/slow-dbunit-databasesequencefilter-initialization , so it is not necessarily something unique to my particular setup.
                Someone mentioned: "shoddy 11R2 install" or poor listener setup (I didn't do any listener setup, all I ever did was issue a lsnctrl start command).

                Now that I know it is in that line, what's your diagnostic tool of choice? If you still think this is a non-standard, unique to my setup issue, feel free to delete the thread.