Solr index is no longer updated after fedora has been up for several days

[Lloyd Harischandra]

I use Fedora 3.5, FedoraGSearch 2.6 and Solr 4.2.1

I've been experiencing this problem since quite some time. When I restart the tomcat server and then ingest some objects, they are indexed property. Everything works as expected. But when I keep fedora running for several days, it seems that new objects or the objects that are being purged are not undated in the solr index.

When I shut down the tomcat server, I see the following error message in catalina.out log.

ERROR 2014-03-30 23:58:23,913 (MessagingClient) Messaging Exception encountered attempting to stop Messaging Client: fedoragsearch0. Exception message: The JMS connection has failed: Channel was inactive for too (>30000) long: localhost/127.0.0.1:61616

com.yourmediashelf.fedora.client.messaging.MessagingException: The JMS connection has failed: Channel was inactive for too (>30000) long: localhost/127.0.0.1:61616

at com.yourmediashelf.fedora.client.messaging.JMSManager.close(JMSManager.java:680)

at com.yourmediashelf.fedora.client.messaging.MessagingClient.stop(MessagingClient.java:320)

at dk.defxws.fedoragsearch.server.UpdateListener.destroy(UpdateListener.java:127)

at org.apache.catalina.core.StandardWrapper.unload(StandardWrapper.java:1394)

at org.apache.catalina.core.StandardWrapper.stop(StandardWrapper.java:1739)

at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4764)

at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:924)

at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:1319)

at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:1290)

at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:323)

at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)

at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1086)

at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1098)

at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:450)

at org.apache.catalina.core.StandardService.stop(StandardService.java:587)

at org.apache.catalina.core.StandardServer.stop(StandardServer.java:744)

at org.apache.catalina.startup.Catalina.stop(Catalina.java:648)

at org.apache.catalina.startup.Catalina.start(Catalina.java:615)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)

at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)

Caused by: org.apache.activemq.ConnectionFailedException: The JMS connection has failed: Channel was inactive for too (>30000) long: localhost/127.0.0.1:61616

at org.apache.activemq.ActiveMQConnection.checkClosedOrFailed(ActiveMQConnection.java:1362)

at org.apache.activemq.ActiveMQConnection.stop(ActiveMQConnection.java:545)

at com.yourmediashelf.fedora.client.messaging.JMSManager.close(JMSManager.java:674)

... 23 more

Caused by: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>30000) long: localhost/127.0.0.1:61616

at org.apache.activemq.transport.InactivityMonitor$4.run(InactivityMonitor.java:185)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

at java.lang.Thread.run(Thread.java:744)

I don't know whether this error comes because of broker has been inactive for long time before I shut down the tomcat server or because I shut the tomcat server down hence broker is now inactive.

Furthermore when this happens, no new log messages are printed on fedoragsearch.daily.log

Any help would be much appreciated.

[Luis Zorita]

Hi  Lloyd:
I think this url will help you to solve the problem.
https://activemq.apache.org/activemq-inactivitymonitor.html
Saludos
Luis Zorita
UNED

--
You received this message because you are subscribed to the Google Groups "Fedora Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fedora-communi...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.