[ 
https://issues.apache.org/jira/browse/CONNECTORS-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright resolved CONNECTORS-836.
------------------------------------

    Resolution: Fixed

r1550177


> ^C agents process running under zookeeper when under load causes exception
> --------------------------------------------------------------------------
>
>                 Key: CONNECTORS-836
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-836
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Framework crawler agent
>    Affects Versions: ManifoldCF 1.5
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 1.5
>
>
> The exception is as follows:
> {code}
> Exception in thread "Shutdown thread" java.lang.IllegalStateException: 
> Already have a lock in place: 
> '/org.apache.manifoldcf.locks-_Cache_JOB_1386770226340/read
> -0000000317'; can't also write lock 
> '/org.apache.manifoldcf.servicelock-AGENT_org.apache.manifoldcf.crawler.system.CrawlerAgent'
>         at 
> org.apache.manifoldcf.core.lockmanager.ZooKeeperConnection.obtainWriteLockNoWait(ZooKeeperConnection.java:265)
>         at 
> org.apache.manifoldcf.core.lockmanager.ZooKeeperLockManager.enterServiceRegistryWriteLock(ZooKeeperLockManager.java:551)
>         at 
> org.apache.manifoldcf.core.lockmanager.ZooKeeperLockManager.endServiceActivity(ZooKeeperLockManager.java:473)
>         at 
> org.apache.manifoldcf.agents.system.AgentsDaemon.stopAgents(AgentsDaemon.java:169)
>         at 
> org.apache.manifoldcf.agents.system.AgentsDaemon$AgentsShutdownHook.doCleanup(AgentsDaemon.java:385)
>         at 
> org.apache.manifoldcf.core.system.ManifoldCF.cleanUpEnvironment(ManifoldCF.java:1306)
>         at 
> org.apache.manifoldcf.core.system.ManifoldCF$ShutdownThread.run(ManifoldCF.java:1460)
> {code}
> It looks a bit like the shutdown thread is somehow inheriting the wrong 
> lockmanager instance in this case??



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Reply via email to