My issue with jms being active, but fedora not sending messages has been
resolved, and I thought I'd share what I
discovered.
If fedora is not configured for jms messaging when installed, there will be an
entry in the fedora.fcfg file, within the
fedora.server.management.ManagementDelegate module, that is commented out:
<!--
<param name="decorator1"
value="fedora.server.messaging.NotificationInvocationHandler" />
-->
This will prevent messaging through jms even though the ActiveMQ modules start
and connect correctly to any client. The
comment for this module *does* explain this, to a certain extent, but the
Messaging documentation for fedora does not
mention this at all.
A big thanks to Aaron Birkland for pointing this out to me.
Hth,
-Tim
> -----Original Message-----
> From: Tim Cornwell [mailto:tc...@cornell.edu]
> Sent: Wednesday, September 01, 2010 3:54 PM
> To: fedora-commons-users@lists.sourceforge.net
> Subject: [fcrepo-user] gSearch/fedora jms automated updating
> not working forme
>
> Dear All,
>
> I do not seem to be able to receive update messages from
> fedora to my gsearch instance.
>
> I am using the latest gsearch code, and fedora 3.3.
> Fedora and gsearch are running in separate tomcat (6)
> instances on the same (virtual) system. Fedora is tomcat
> 6.0.24, and gsearch is 6.0.29.
>
> I believe I have all configuration parameters correct:
> I have set enabled to true in the
> fedora.server.messaging.Messaging module.
> I have set up a datastore name (with the value of
> "apimUpdateMessages") that matches the gsearch
> updater.properties configuration parameter: client.id
>
> I have enabled debug on gsearch and can see (in the gsearch
> log file) the message:
>
> "...
> (UpdateListener) Initializing the Update Listener
> ..."
>
>
> I *do* see many log entries in the gsearch catalina.out log
> like these:
>
> "...
> DEBUG 2010-09-01 15:31:26,314 (InactivityMonitor) 10000 ms
> elapsed since last write check.
> DEBUG 2010-09-01 15:31:26,314 (InactivityMonitor) Message
> sent since last write check, resetting flag
> DEBUG 2010-09-01 15:31:26,317 (InactivityMonitor) 30001 ms
> elapsed since last read check.
> DEBUG 2010-09-01 15:31:26,317 (InactivityMonitor) Message
> received since last read check, resetting flag:
> DEBUG 2010-09-01 15:31:36,312 (InactivityMonitor) 9998 ms
> elapsed since last write check.
> DEBUG 2010-09-01 15:31:36,313 (InactivityMonitor) Message
> sent since last write check, resetting flag
> ..."
>
>
> But: When I update an object in the fedora instance, I see
> no corresponding update happen to the index, and no activity
> in the gsearch logs.
>
>
> I hope I have provided enough detail here. Any notion of
> what to try to diagnose this would be greatly appreciated.
>
> Thanks,
> -Tim
>
> Timothy Cornwell
> National Science Digital Library
> http://nsdl.org
>
>
>
>
> --------------------------------------------------------------
> ----------------
> This SF.net Dev2Dev email is sponsored by:
>
> Show off your parallel programming skills.
> Enter the Intel(R) Threading Challenge 2010.
> http://p.sf.net/sfu/intel-thread-sfd
> _______________________________________________
> Fedora-commons-users mailing list
> Fedora-commons-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
>
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Fedora-commons-users mailing list
Fedora-commons-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
