Hi Lodewijk,
GSearch uses ActiveMQ (or whichever message broker you have configured) to
listen for updates coming from Fedora in order to update the search index.
On startup GSearch needs to be able to connect to the broker in order to
start listening for those updates. In the default Fedora install, the
message broker is started along with the Fedora server, so if you start
GSearch before starting Fedora it cannot connect to a broker and you get an
error.
The error you are seeing is actually masking the real error, which is that
no connection could me made to the broker. When trying to log the real error
a runtime dependency error (cannot load Server.properties) is thrown and
that is what makes it to the logs. This issue was fixed for GSearch 2.2
(see http://fedora-commons.org/jira/browse/FCREPO-245) so you likely need to
update GSearch. This fix also adds in a retry feature that handles the
case where Fedora and GSearch are in the same container and GSearch happens
to be loaded first.
All this said, if you are in a production environment you should really be
running your message broker as a stand-alone application. This is fairly
easy to accomplish with ActiveMQ, and it allows you more control over how
you would like your message broker configured.
Bill
On Wed, Jul 8, 2009 at 8:10 AM, Lodewijk Bogaards <
[email protected]> wrote:
> Hi,
>
> I wonder why we are having problems starting gSearch BEFORE Fedora is
> started. It seems to have something to do with activeMQ and all that:
>
> ERROR 2009-07-08 14:02:38,056 ([/fedoragsearch]) StandardWrapper.Throwable
> java.lang.ExceptionInInitializerError
> at
> fedora.server.errors.ServerException.getMessage(ServerException.java:129)
> at
>
> fedora.client.messaging.JmsMessagingClient.start(JmsMessagingClient.java:250
> )
> at
> dk.defxws.fedoragsearch.server.UpdateListener.init(UpdateListener.java:96)
> at javax.servlet.GenericServlet.init(GenericServlet.java:212)
>
>
> Caused by: java.util.MissingResourceException: Can't find bundle for base
> name fedora.server.resources.Server, locale en_US
> at
>
> java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:8
> 36)
> at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:805)
> at java.util.ResourceBundle.getBundle(ResourceBundle.java:549)
> at fedora.server.Server.<clinit>(Server.java:85)
> ... 34 more
>
> ERROR 2009-07-08 14:02:38,062 ([/fedoragsearch]) Servlet /fedoragsearch
> threw load() exception
> java.util.MissingResourceException: Can't find bundle for base name
> fedora.server.resources.Server, locale en_US
>
> When we manually start gSearch after Fedora has been loaded the problem
> does
> not occur. Anyone know why and how to fix this?
>
> Kind regards,
>
> Lodewijk
>
>
>
> ------------------------------------------------------------------------------
> Enter the BlackBerry Developer Challenge
> This is your chance to win up to $100,000 in prizes! For a limited time,
> vendors submitting new applications to BlackBerry App World(TM) will have
> the opportunity to enter the BlackBerry Developer Challenge. See full prize
> details at: http://p.sf.net/sfu/Challenge
> _______________________________________________
> Fedora-commons-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
>
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Fedora-commons-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
