I don't know if this is the solution you need, but I would like to know if you are willing to try it, or at least have a look to see if this is the case. There were known problems with caching (though I don't know the exact nature of the problem personally) using the DiGIR provider, so we turned it off in any existing installations. Can you check to see if you have caching turned on? It is set by the line in localConfig.php that may be commented out. I set it like this to turn caching off:

define('DIGIR_USE_CACHE', FALSE);

We are hoping to have a new DIGIR provider release within a week - one that has log querying capabilities. Some of the capabilities are there in CVS, but there will be a number of changes committed as soon as I have a chance to test them to a reasonable extent. Once committed, I will create a new downloadable release on http://sourceforge.net/projects/digir - the first one since 2003!

On 9/26/06, John Wall < j.wall@rbgkew.org.uk> wrote:

Hi,

A few months ago, we installed the DiGIR provider to provide data to the GBIF portal.  It ran with some teething troubles relating to cache size until last week we had our first big hit on the provider, which caused a massive increase in connections to the mysql database we are using to hold the content.  We then discovered that the DiGIR provider was not releasing connections (which in turn was causing other systems to fail). As a short term measure, we then restricted the maximum number of connections mysql would permit the user to have. This prevents DiGIR from overwelming mysql but now DiGIR has used up the connections and will not query the database, presumably because the connections are being held and are not available.

Looking at the documentation I can't see where the maximum number of connections is set (of course, I might be looking in the wrong place!).  I'm not a php person so looking at the code isn't helping.  I've also tried to download the latest cvs snapshot from www.digir.net but every time we try it we get a corrupted file warning (tried this on 2 difference machines at work).

Heres the diagnostics we get from DiGIR.php:

<diagnostics>

<diagnostic code="STATUS_INTERVAL" severity="info">600</diagnostic>

<diagnostic code="STATUS_DATA" severity="info">2,0,0</diagnostic>

<diagnostic code="Unknown PHP Error [2]" severity="DIAG_WARNING">mysql_pconnect(): User 'digir' has exceeded the 'max_connections' resource (current value: 10) (/home/www/docs/digir/lib/adodb/drivers/adodb- mysql.inc.php:251)</diagnostic>

<diagnostic code="INTERNAL_DATABASE_ERROR" severity="error">ADOdb reported error connecting to database:User 'digir' has exceeded the 'max_connections' resource (current value: 10)</diagnostic>

<diagnostic code="Unknown PHP Error [2]" severity="DIAG_WARNING">mysql_close(): supplied argument is not a valid MySQL-Link resource (/home/www/docs/digir/lib/adodb/drivers/adodb- mysql.inc.php:370)</diagnostic>

</diagnostics>


I hope you can help!

John Wall


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

_______________________________________________
DiGIR-developers mailing list
DiGIR-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/digir-developers