I looked through my history, and didn't find your message dated March
28th either. Strange. Anyway, your question seems to be related to this
response I posted on March 27th:
> You could have cron invoke wget
> (http://www.gnu.org/software/wget/wget.html)
> which could then invoke a servlet that would call your backup routine.
> This way, the
> backup would run within the same JVM as the rest of the tomcat
> connections.
Of course, instead of 'backup' read 'load'. wget is a command line
utility that emulates
a browser GET. Just create a servlet that calls your load in the 'doGet'
method. Then
call wget once a day with the URL of the servlet. The servlet could
write just a line or
two of status info that the wget could append to a log file.
The key is to get the Tomcat JVM to execute the load (or backup) process.
Scott Plante
Steve Carton wrote:
> Alexei,
>
> I hope you get an answer -- This is essentially my
> problem as well. I ended up working around it by
> having the load program (which only runs once
> daily) restart the servlet engine, causing
> InstantDB to get rid of whatever cache it is
> maintaining. Cheezy.
>
> Steve
> ----- Original Message -----
> From: "Alexei Trebounskikh" <alexei@sqwest.bc.ca>
> To: <instantdb@enhydra.org>
> Sent: Friday, April 06, 2001 8:12 PM
> Subject: InstantDB: Can't see the changes being
> done on another connection
>
>
> | Hello everybody,
> |
> | I guess my question has a lot in common with
> Steve Carton's one (March 28,
> | 2001 12:47 InstantDB: Flushing a cache), but
> unfortunately that one was
> | never answered.
> |
> | I use InstantDB 3.26 and I have the following
> problem: my application does
> | the connection pooling, and I found out that
> changes done by, for example,
> | insert query, using one connection, are not seen
> using the other existing
> | connections, so the select query will not return
> the inserted row, even if
> | the connection which does this changes is
> closed. At the same time, new rows
> | are perfectly visible if I create new connection
> and execute the same select
> | query. I have to say that I really hate the idea
> to create new connections
> | all the time the change is made, but I'm running
> out of my own ideas. Could
> | you possibly give me the clue why it works this
> way and how this situation
> | can be avoided or fixed? Are there any
> connection or database properties to
> | play with?
> |
> | The quick answer will be truly appreciated.
> Thank you!
> |
> | Best regards,
> | Alexei
> |
> | ------------------------------------------------
> -----------------------------
> | To unsubscribe from this mailing list, send
> email to majordomo@enhydra.org
> | with the text "unsubscribe instantdb" in the
> body of the email.
> | If you have other questions regarding this
> mailing list, send email to
> | the list admin at owner-instantdb@enhydra.org.
>
> -----------------------------------------------------------------------------
> To unsubscribe from this mailing list, send email to majordomo@enhydra.org
> with the text "unsubscribe instantdb" in the body of the email.
> If you have other questions regarding this mailing list, send email to
> the list admin at owner-instantdb@enhydra.org.
>
>
-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
with the text "unsubscribe instantdb" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-instantdb@enhydra.org.
|