Ticket #267 (closed defect: fixed)

Opened 11 years ago

Last modified 11 years ago

GS3: Need to restart tomcat in order for browser to note new and deleted collections

Reported by: ak19 Owned by: kjdon
Priority: very high Milestone: 3.04 Release
Component: Greenstone3 Runtime Severity: blocker
Keywords: tomcat, restart, stop, start, collection, new, delete Cc:

Description

Using: Greenstone 3 compiled from source code checked out on 03 March 2008.

Problem: when I have the Greenstone 3 browser running and create a new collection in GLI (or delete an existing collection), merely refreshing the browser is not enough. An ant restart is required to propagate these changes to the server. As a natural consequence, changes made to a collection when it is rebuilt--such as after unticking the Casefold option in GLI's Design tab > Search Indexes--are not visible in the browser pages either until an explicit restart of the web server.

My GS 2.80 installations, binary as well as from recent source code, do not exhibit this problem.

Change History

Changed 11 years ago by ak19

  • priority changed from moderate to very high
  • severity set to blocker

Changed 11 years ago by dmn

  • owner changed from nobody to kjdon

Changed 11 years ago by davidb

We think GLI has a mechanism to cope with this. Check it's working correctly?

Changed 11 years ago by kjdon

Works for me (18 Aug). Did you have your library_url set correctly? I created a new collection and didn't even need to click preview. It's already sent a configuration request so that my new collection shows up.

Oh, just thought to test deleting a collection - its not done there. :-(

Changed 11 years ago by ak19

  • status changed from new to closed
  • resolution set to fixed

Updated delete collection code in GLI by calling Gatherer.configGS3Server() from CollectionManager?.deleteCollection(). This fixes the part that was still outstanding. Closing ticket.

Note: See TracTickets for help on using tickets.