Document the EJB timer issue workaround in the admin guide

[shlake]

Dataverse 4.5.1:

After yum update within OS version, part of quarterly patching, On deploy of 4.5.1 war file got the error:

remote failure: Error occurred during deployment: Exception while loading the app : EJB Timer Service is not available. Please see server.log for more details.

dataverse would not deploy/start

Fix was as follows:

• Remove all rows from EJB__TIMER__TBL
• undeploy dataverse
• stop glassfish
• remove "generated" directory
• remove "osgi-cach"
• restart glassfish
• deploy dataverse war file

[pdurbin]

@shlake thanks for opening this issue and for all the chatter in http://irclog.iq.harvard.edu/dataverse/2017-03-06 ! This issue is related to #3336 and the task should be to document these steps, especially the bit about the EJB__TIMER__TBL table, which isn't documented at all. I see that @pameyer is also working on a related script in #3670. Good stuff.

[landreev]

Since no one objected on slack - I went ahead and merged in Pete's PR with the sample cleanup script. This way I'll add a doc section that will have a link to it.

[pdurbin]

@landreev I'm glad you went ahead and merged #3670 but I wonder if we should git mv the file to somewhere in the source tree that mirrors when we'd want the new clear_timer.sh script on the file system. For example, I keep the Glassfish init script at _static/installation/files/etc/init.d/glassfish. Maybe we could put the script at _static/installation/files/usr/local/dataverse/sbin/clear_timer.sh or something. We could also tackle this when there are more files in play. There are other files that might be useful to a Dataverse admin such as scripts/search/query and my personal favorite scripts/database/homebrew/kill9glassfish. ;)

[landreev]

Pete put the script there because he meant it to be an example. Something that they can copy and paste and use as the base of their own script that will actually work on their system. I support that. It's not a ready-to-run script; unlike, say, the scripts that come with the installer. It really is an example; with absolutely no promise that it will work as is. (mostly because of how it relies on su postgres to run a psql command)

[landreev]

not sure why this was already in code review... but I've checked in the doc, so it should go into review now.

[landreev]

PR: #3674