jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "DilipKumar S (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCR-4111) Issue with Jack Rabbit Repository
Date Fri, 10 Feb 2017 08:28:41 GMT

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

DilipKumar S updated JCR-4111:


I Could notice you have resolved the below JIRA ID with Resolution as Duplicate.

If its duplicated could you share me the Original JIRA ID which comprises of the same issue.

Please assist us.

DilipKumar S

> Issue with Jack Rabbit Repository
> ---------------------------------
>                 Key: JCR-4111
>                 URL: https://issues.apache.org/jira/browse/JCR-4111
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: core
>            Reporter: DilipKumar S
> Hi,
> Am trying to find someone who could assist me with an issue.
> We are working with an Application which utilizes actuate report server to generate Reports
, While we try to delete unwanted reports from the repository using our own utility , The
job is getting executed unfortunately we been hitting with below error in our logs :
> ==============
> 2017-02-10 10:57:33,410 | ERROR | gcl:logon/advisor(Attribute : gcl:logon/advisor) |
 |  | jobLauncherThreadPoolTaskExecutor-22 | c.o.r.s.ContentRepositoryService | removeContent:
Exception from the uderlying repository
> javax.jcr.RepositoryException: Cannot create GC. GC already running
> org.apache.jackrabbit.core.RepositoryImpl.createDataStoreGarbageCollector(RepositoryImpl.java:1454)
> ===============
> We have tried to debug the cause unfortunately we were unable to do so.
> we sought advice from our experts and they have suggested that this is hitting from JackRabbit
Jar which is not part of our environment and they could'nt help us either.
> Jar File  : jackrabbit-core.jar:2.8.0.
> Could someone help me to get the underlying cause as well as a fix to overcome the issue.
> Thanks,
> DilipKumar S

This message was sent by Atlassian JIRA

View raw message