Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document the EJB timer issue workaround in the admin guide #3669

Closed
shlake opened this issue Mar 6, 2017 · 9 comments
Closed

Document the EJB timer issue workaround in the admin guide #3669

shlake opened this issue Mar 6, 2017 · 9 comments

Comments

@shlake
Copy link
Contributor

shlake commented Mar 6, 2017

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
@landreev landreev changed the title EJB Timer Service is not available - Error on deploy of 4.5.1 Document the EJB timer issue workaround in the admin guide Mar 6, 2017
@pdurbin
Copy link
Member

pdurbin commented Mar 6, 2017

@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 landreev self-assigned this Mar 6, 2017
@landreev
Copy link
Contributor

landreev commented Mar 7, 2017

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
Copy link
Member

pdurbin commented Mar 7, 2017

@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
Copy link
Contributor

landreev commented Mar 7, 2017

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
Copy link
Contributor

landreev commented Mar 8, 2017

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

@landreev
Copy link
Contributor

landreev commented Mar 8, 2017

PR: #3674

@pdurbin
Copy link
Member

pdurbin commented Mar 8, 2017

@landreev pull request #3674 looks great. I made a few minor tweaks in 4a0a7e2. Thanks for the script @pameyer ! I just moved this issue to QA in https://waffle.io/IQSS/dataverse

@pdurbin pdurbin removed their assignment Mar 8, 2017
@pameyer
Copy link
Contributor

pameyer commented Mar 8, 2017

@pdurbin - if there's a better place for example utility scripts to go, please feel free to move it there.

@pdurbin
Copy link
Member

pdurbin commented Mar 8, 2017

@pameyer meh, let's wait until we create an rpm or a deb of Dataverse scripts and such. Not that we're working on that. 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants