Let me give you the details you need to help me with this. This is what I run:
>From /bin I run this: BINDIR=`dirname $0` $BINDIR/dsrun_160 org.dspace.administer.ReleaseRestricted [email protected] And dsrun_160 is the dsrun from version 1.6, I have not added this to the launcher mechanism, but I have been doing this successfully forever, but now that we are using discovery, I get the error I mentioned earlier. The work around is that I can remove discovery from the dspace.cfg file and update bin, and then run my script, and I that seems to work, but I was not sure if discovery needed to know that the item was reinstated and update it's index or not. BTW, how does the discovery index get updated. I know the lucene index is updated when filter-media is run, but what about discovery. Hope this info makes my situation more clear. Thank you! Jose On Tue, Dec 11, 2012 at 10:22 AM, Jose Blanco <[email protected]> wrote: > This is the setting I have now: > > event.dispatcher.default.consumers = search, browse, discovery, > eperson, harvester > > # The noindex dispatcher will not create search or browse indexs > (usefull for batch item imports) > event.dispatcher.noindex.class = org.dspace.event.BasicDispatcher > event.dispatcher.noindex.consumers = eperson > > I'm wondering if I need to add discovery to > > event.dispatcher.noindex.consumers > > But how will the item get indexed in solr for discovery? > > -Jose > > On Mon, Dec 10, 2012 at 5:13 PM, Andrea Schweer <[email protected]> wrote: >> Hi Jose, >> >> On 11/12/12 10:59, Jose Blanco wrote: >>> It works fine as long as I don't have discovery >>> event.dispatcher.default.consumers = search, browse, eperson, harvester >>> >>> but when I add discovery >>> event.dispatcher.default.consumers = search, browse, discovery, >>> eperson, harvester >> >> This is a very stupid question, but is that the actual formatting in >> your dspace.cfg? I see a linebreak after "discovery,", which shouldn't >> be there. >> >>> I get this message. It seems like I have to do something else before >>> doing complete. : >>> >>> Exception in thread "main" java.lang.IllegalStateException: Unable to >>> aquire dispatcher named default >> >> To me this looks more like something is broken with your event consumer >> set-up. >> >> cheers, >> Andrea >> >> -- >> Dr Andrea Schweer >> IRR Technical Specialist, ITS Information Systems >> The University of Waikato, Hamilton, New Zealand >> >> >> ------------------------------------------------------------------------------ >> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial >> Remotely access PCs and mobile devices and provide instant support >> Improve your efficiency, and focus on delivering more value-add services >> Discover what IT Professionals Know. Rescue delivers >> http://p.sf.net/sfu/logmein_12329d2d >> _______________________________________________ >> DSpace-tech mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/dspace-tech >> List Etiquette: >> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
