Hi, thanks for the tips! > - I have frequently seen, with DSpace, that Tomcat can not entirely > terminate it's process when getting a stop or restart command the first > time. Just figured it was worth warning anyone who hadn't noticed this. > It can cause a lot of lost time in trying to figure out why code-changes > aren't showing up, or incorrect assumptions that a trouble-shooting > attempt didn't work.
We've found this, too, though we've found that a wait of about 10 seconds tends to be all that is necessary for Tomcat to finish up. The restart alias of ours calls a script which waits 10 seconds between each service stop and start. It's pretty well behaved. We run it every night, to "shake out all the cobwebs." The stop and start aliases are for me, when I'm in a hurry, on our dev host. I stop everything, count off in my head, and start it all back up. Only saves me 20 seconds or so... but it makes me feel better. :-) > export DSPACE_HOME=/my/deploy/dir/dspace > export DSPACE_LOG=/my/deploy/dir/dspace/log/dspace.cfg I should refactor a bit, it does look a mess, doesn't it? :-) They grew up organically, one alias at a time, as I grew tired of typing something. DLXS advises a similar practice, using $DLXSROOT, but frankly, and this is going to sound really dumb, I hate having to hit the $ and then a bunch of caps... hurts my fingers. I like typing "mos[tab].mvn" or "mos[tab].au[tab]" and being right where I need to be. But, I do think the environment variables will help with keeping all those aliases easier to read, so I'm going to implement that. Thanks again. --Hardy ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
