geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris (JIRA)" <j...@apache.org>
Subject [jira] Created: (GERONIMO-5386) blocking-timeout-milliseconds is not applied to a pool if introduced from edit page.
Date Tue, 22 Jun 2010 04:32:54 GMT
blocking-timeout-milliseconds is not applied to a pool if introduced from edit page. 
-------------------------------------------------------------------------------------

                 Key: GERONIMO-5386
                 URL: https://issues.apache.org/jira/browse/GERONIMO-5386
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: databases
    Affects Versions: 2.1.5
         Environment: win32
            Reporter: Chris
            Priority: Minor


After creating a number of database pools using the web-console's pool wizard, I needed to
increase the acquire timeout on one of the pools from the default (5 seconds) to something
greater (50 seconds). 

After 
1) browsing to the database pool's page
2) selecting edit next to the pool in question (ase 12.5)
3) replacing 5000 with 50000
4) apply

No change was noticeable. Running a sample application client revealed timeout exceptions
at 5 seconds still. Restarting Geronimo and repeating 1-4, no luck. Ultimately I resorted
to altering the plan manually, adding 
{color:red} <blocking-timeout-milliseconds>50000</blocking-timeout-milliseconds>{color}

 and redeploying from the command line.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message