Parco, It seems like you have several choices. Read this thread: http://forums.asp.net/t/623320.aspx. The second post mentions non- overlapping recycling which seems to mean that requests in the old worker process get dropped. Probably not what you want. The first post goes over the scheduling and resource settings for controlling recycles in the Application Pool.
I would suggest you try and set your recycles for a time of day that is best for you. Keep overlapping recycles, but if the new worker process finds itself in client-server mode try to move to embedded mode (you'll have to at some point because the old worker won't be there anymore). Keep track of how long your worker is trying to get into embedded mode. If it is seconds or minutes each day, let it be. If it is several minutes a day, use the Application Pool settings to see if you can limit the time that a recycled worker has to fulfill requests before it gets killed. Good luck, McKinley On Mar 11, 5:53 pm, Parco <[email protected]> wrote: > Then, now the problem is, the H2 engine in the old process would still > lock the database files and the H2 inside the new process would fail > to open the database files and return error exceptions. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/h2-database?hl=en -~----------~----~----~----~------~----~------~--~---
