Hello Scott, Of course. But this is for development hsqldb makes it simpler to develop since I don't have to be connected to the network or install the pig that is Oracle on my own development box. Plus it makes it simple to clean things up after testing. We have Oracle set up for production. I just wish I didn't have to completely shut down Tomcat all the time to avoid the locking of hsqldb files during development.
Jake Wednesday, March 12, 2003, 11:10:40 AM, you wrote: WS> We had this issue with production apps locking up on hsql, even without restarting. Hsql seems buggy in single-user mode so I would highly recommend, NOT using hsql for this reason. WS> -scott >> -----Original Message----- >> From: Jacob Kjome [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, March 12, 2003 11:51 AM >> To: Jetspeed Users List >> Subject: Re[2]: Sessions and Restarting Jetspeed >> >> Hello Ryan, >> >> Seems to me that when I ran into problems after restarting the app via >> the Tomcat manager app, the problem was that Jetspeed was not able to >> write stuff to the hsqldb database files because another process had a >> handle on those files. Restarting Tomcat fully resolves this issue. >> So, it seems as if hsqldb isn't releasing the files when it is shut >> down. Somehow the JVM keeps a handle on the files. Is this what >> people are seeing and confusing it with session problems or am I just >> seeing a completely different issue here? >> >> Jake >> >> Wednesday, March 12, 2003, 10:26:21 AM, you wrote: >> >> RC> I get the same problem, and sometimes I get a horrible exception, >> RC> sometimes and out of memory error. This usually happens after I use >> the >> RC> manger app to reload the application about 8-10 times. If I stop >> tomcat, >> RC> then start it back up problems go away. >> >> RC> Mark Orciuch wrote: >> >> >>I believe this has to do with Tomcat attempting to restore the sessions >> upon >> >>restart. Here are some related posts: >> >> >> >>http://www.mail-archive.com/jetspeed- >> [EMAIL PROTECTED]/msg07902.html >> >>http://www.mail-archive.com/turbine- >> user%40jakarta.apache.org/msg11325.html >> >> >> >>Best regards, >> >> >> >>Mark Orciuch - [EMAIL PROTECTED] >> >>Jakarta Jetspeed - Enterprise Portal in Java >> >>http://jakarta.apache.org/jetspeed/ >> >> >> >> >> >> >> >>>-----Original Message----- >> >>>From: Jarrell, Maury [mailto:[EMAIL PROTECTED] >> >>>Sent: Wednesday, March 12, 2003 8:45 AM >> >>>To: 'Jetspeed Users List' >> >>>Subject: Sessions and Restarting Jetspeed >> >>> >> >>> >> >>>Hello all, >> >>> >> >>>I've been lurking on this list for quite some time and appreciate all >> the >> >>>help people provide here. >> >>> >> >>>I've been tinkering with Jetspeed ( 1.4b3 on Tomcat 4.12 ): setting up >> >>>simple HTML portlets in the registry and such. To do this I >> >>>first tried the >> >>>manager app in Tomcat to shutdown Jetspeed, make my changes and >> >>>then restart >> >>>Jetspeed. Later I tried shutting down Tomcat altogether, making >> changes, >> >>>and then restarting. When I try to log back in to Jetspeed, I >> >>>get "Horrible >> >>>Exception Errors" that I surmise are the result of my browser >> >>>hanging on to >> >>>a session id or some such that the new instance of Jetspeed knows >> nothing >> >>>about. It takes several minutes before I'm able to connect again >> >>>and it is >> >>>slowing my progress significantly. I'm sure there is a silly thing I'm >> >>>overlooking, but need a nudge in the right direction. So my >> >>>questions are: >> >>>1. Is my guess correct, or is something else going on? and 2. How >> can I >> >>>overcome this nuisance? >> >>> >> >>>Thanks, >> >>>Maury Jarrell >> >>> >> >>> >> >>> >> >>> >> >>>--------------------------------------------------------------------- >> >>>To unsubscribe, e-mail: [EMAIL PROTECTED] >> >>>For additional commands, e-mail: [EMAIL PROTECTED] >> >>> >> >>> >> >> >> >> >> >>--------------------------------------------------------------------- >> >>To unsubscribe, e-mail: [EMAIL PROTECTED] >> >>For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> >> >> >> >> >> RC> --------------------------------------------------------------------- >> RC> To unsubscribe, e-mail: [EMAIL PROTECTED] >> RC> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> -- >> Best regards, >> Jacob mailto:[EMAIL PROTECTED] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] -- Best regards, Jacob mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
