Service proxy has been destroyed error

Hi, I found similar topics but suggestions are not working for my case. My problem is that we implemented App for Jira Server and one of its method is trying to check whether issue exists or not
using our facade method

public Optional<Issue> findIssueById(long id) {
        return Optional.ofNullable(issueManager.getIssueObject(id));
    }

where issueManager is com.atlassian.jira.issue.IssueManager (https://docs.atlassian.com/software/jira/docs/api/7.6.1/com/atlassian/jira/issue/IssueManager.html)

Invocation of “proxy” of issueManager is failing with following error

org.eclipse.gemini.blueprint.service.importer.ServiceProxyDestroyedException: service proxy has been destroyed
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceDynamicInterceptor$ServiceLookUpCallback.doWithRetry(ServiceDynamicInterceptor.java:102)
at org.eclipse.gemini.blueprint.service.importer.support.internal.support.RetryTemplate.execute(RetryTemplate.java:81)
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceDynamicInterceptor.lookupService(ServiceDynamicInterceptor.java:448)
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceDynamicInterceptor.getTarget(ServiceDynamicInterceptor.java:410)
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java:70)
at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invoke(ServiceTCCLInterceptor.java:53)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:208)
at com.sun.proxy.$Proxy8982.getIssueObject(Unknown Source)
at cz.morosystems.jira.tm.pmo.services.facade.IssueFacade.findIssueById(IssueFacade.java:117)
at cz.morosystems.jira.tm.pmo.services.utilsservice.IssueUtilsService.validateIssueExistence(IssueUtilsService.java:34)
at cz.morosystems.jira.tm.pmo.services.impl.cfn.CfnAllocationServiceImpl.validateIssueExistence(CfnAllocationServiceImpl.java:380)
at cz.morosystems.jira.tm.pmo.services.impl.cfn.CfnAllocationServiceImpl.changeAllocationIssue(CfnAllocationServiceImpl.java:312)
at cz.morosystems.jira.tm.pmo.iface.service.cfn.CfnAllocationService$changeAllocationIssue$1.call(Unknown Source)
at cz.tmobile.commons.TempoPlanningFacade.moveAllocation(TempoPlanningFacade.groovy:35)
at cz.tmobile.commons.TempoPlanningFacade$moveAllocation$0.call(Unknown Source)
at cz.tmobile.post.POST_DEM_subtaskCopyAllocationsToTimesheets$_run_closure2.doCall(POST_DEM_subtaskCopyAllocationsToTimesheets.groovy:77)
at cz.tmobile.post.POST_DEM_subtaskCopyAllocationsToTimesheets.run(POST_DEM_subtaskCopyAllocationsToTimesheets.groovy:68)

I know this exception can occur when the service, for which the proxy is created, is invalidated (for example when reinstalled App, or disabled App…) but it does not make sense to me when talking about **Jira API ** service. Did you experience similar behaviour? Can it be caused by e.g. threads synchronization or something like that? The true is that this method is invoked multiple times in short time.

I have a similar issue. Our service is crashes when getting an issue from the IssueManager isntance.

    return Option.option(issueManager.getIssueObject(entityProperty.getEntityId()));