Timer is getting for some process instance id even after time is passed out

[karan kanojiya]

Hi  All,

I am facing issue for Catching Intermediate Timer task used as a boundary event on Human Task .

Issue :

Sometime timer event is not getting triggered even after time is passed out . 

I have checked the value of the timer it is in Valid Format  : For Example PT1S or PT1m

I am facing this issue for some process instances is this a bug or i am missing any property  ?

Now i have to triggered the instances which are stop even if timer is passed out.

Plzz find the attached file for more clear idea on bpmn diagram .

Thanks in Advance !!

Regards,

Karan Kanojiya

[Abhijit Humbe]

which jbpm version you are using?  and  which timer implementation(EJB,Quartz or default)

Abhijit Humbe

--
You received this message because you are subscribed to the Google Groups "jBPM Usage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-usage+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/61d4cb4e-ec01-4db4-a4ef-c9acd0ce59c0%40googlegroups.com.

[karan kanojiya]

JBPM version is 7.18.x  

And i am not able to find Timer Implementation type in Properties Tab  as u said (EJB,Quartz or default)

Please find the attach file for timer properties.

On Monday, February 10, 2020 at 9:45:35 PM UTC+5:30, Abhijit Humbe wrote:

which jbpm version you are using?  and  which timer implementation(EJB,Quartz or default)

Abhijit Humbe

On Mon, Feb 10, 2020 at 8:25 PM karan kanojiya <kanoji...@gmail.com> wrote:

Hi  All,

I am facing issue for Catching Intermediate Timer task used as a boundary event on Human Task .

Issue :

Sometime timer event is not getting triggered even after time is passed out . 

I have checked the value of the timer it is in Valid Format  : For Example PT1S or PT1m

I am facing this issue for some process instances is this a bug or i am missing any property  ?

Now i have to triggered the instances which are stop even if timer is passed out.

Plzz find the attached file for more clear idea on bpmn diagram .

Thanks in Advance !!

Regards,

Karan Kanojiya

--
You received this message because you are subscribed to the Google Groups "jBPM Usage" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-...@googlegroups.com.

[karan kanojiya]

Hi Maciej,

Please  find the below two attached file  for  two different instances i.e Processinstance id: 1954 & 1949, where timer is getting executed in one of the instances while other one is stuck respectively.

Timer value set is for 1 minute for both 

But only 1954 get executed  but 1949 gets stuck

Is there any property i am missing ?

I am getting this error in Production ,so it is critical plzz help asap.

Thanks in Advance !

[Maciej Swiderski]

Looks like the first one is not properly configured as it does not have the next fire time and that’s why it is stuck. You can reschedule it via admin api of Kie server so it will move forward. 

Maciej

Wiadomość napisana przez karan kanojiya <kanoji...@gmail.com> w dniu 12.02.2020, o godz. 12:38:



To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-usage+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/f4a96793-0d37-4d70-ad60-1876c2180eba%40googlegroups.com.

<Timer_Stuck.JPG>

<Timer_Set.JPG>

[karan kanojiya]

Hi Maciej ,

I am facing issue for Catching Intermediate Timer task used as a boundary event on Human Task .

Issue :

Sometime timer event is not getting triggered even after time is passed out . 

I have checked the value of the timer it is in Valid Format  : For Example PT1S or PT1m

I am facing this issue for some process instances is this a bug or i am missing any property  ?

Now i have to triggered the instances which are stop even if timer is passed out.

I am setting the timer value using process variable .

So I am seeing that for  some  process instance timer is not getting trigger even if the timer value is set 

 

I have referred some of your blogs in the below link :

https://issues.redhat.com/browse/JBPM-5398

So do I need to do change any properties or do some changes in runtime strategy as u mention in the above link (from singleton to per process instance) strategy.

Please help !!!

To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/f4a96793-0d37-4d70-ad60-1876c2180eba%40googlegroups.com.

<Timer_Stuck.JPG>

<Timer_Set.JPG>

[karan kanojiya]

@maciej plzz help !
Should i change any configuration?

[Maciej Swiderski]

There is not enough details to help out .. as if the timer didn’t fire or it failed as moving process instance forward. You would have to examine the logs around the time of stuck timer to see if there are any exceptions.

Maciej

> On 14 Feb 2020, at 09:07, karan kanojiya <kanoji...@gmail.com> wrote:
>
> @maciej plzz help !
> Should i change any configuration?
>

> --
> You received this message because you are subscribed to the Google Groups "jBPM Usage" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-usage+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/aef1cb6d-eddd-42fa-9bd4-b910aa4ed78e%40googlegroups.com.

[karan kanojiya]

I have referred some of your blogs in the below link :

https://issues.redhat.com/browse/JBPM-5398

So do I need to do change any properties or do some changes in runtime strategy as u mention in the above link (from singleton to per process instance) strategy.

My current setup is with singleton strategy and As per your above blog my default timer is EJB as u said .

Since i can Timer instance value is set in process variable which is declare in Timer Property it should work as expected.

Can you  plzz help or i should try configuration that you mention i above link mention.

??

Currently facing issue in Production so can u plzz help !!

On Friday, February 14, 2020 at 2:52:54 PM UTC+5:30, Maciej Swiderski wrote:

There is not enough details to help out .. as if the timer didn’t fire or it failed as moving process instance forward. You would have to examine the logs around the time of stuck timer to see if there are any exceptions.

Maciej

> On 14 Feb 2020, at 09:07, karan kanojiya <kanoji...@gmail.com> wrote:
>
> @maciej plzz help !
> Should i change any configuration?
>
> --
> You received this message because you are subscribed to the Google Groups "jBPM Usage" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-...@googlegroups.com.

[karan kanojiya]

Hi Maciej,

Plzz find the attached File for more clear view.

Should i change my runtime strategy ( Currently : Singleton )

Or

org.kie.timer.ejb.disabled=true

so if you disable ejb timer service singleton strategy can be used safely.

??

On Friday, February 14, 2020 at 2:52:54 PM UTC+5:30, Maciej Swiderski wrote:

There is not enough details to help out .. as if the timer didn’t fire or it failed as moving process instance forward. You would have to examine the logs around the time of stuck timer to see if there are any exceptions.

Maciej

> On 14 Feb 2020, at 09:07, karan kanojiya <kanoji...@gmail.com> wrote:
>
> @maciej plzz help !
> Should i change any configuration?
>
> --
> You received this message because you are subscribed to the Google Groups "jBPM Usage" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-...@googlegroups.com.

[karan kanojiya]

@maciej ?

[Donato Marrazzo]

Let me suggest the following approach:

1) change the strategy to per process instance (just because is a good practice)

2) write and share a reproducer and a deterministic procedure to get the situation

3) if you are not able to reproduce the error, try to catch in your log an exception that seems related with problem.

Unfortunately, if we cannot reproduce the problem we cannot help.

Consider to buy a RHPAM subscription to get a supported version of jBPM.  

On Sunday, February 16, 2020 at 6:38:50 PM UTC+1, karan kanojiya wrote:

@maciej ?

[karan kanojiya]

Thanks Donato,

1) change the strategy to per process instance (just because is a good practice)

---> I will definitely  try this approach

2) if you are not able to reproduce the error, try to catch in your log an exception that seems related with problem.

--> Today i check the logs i can see the  exception mention below for the instance id shared above and also plzz find the attached log file for 

     more clearity

Exception :

1] Execution of time failed due to Could not find session data for id 7: org.drools.persistence.api.SessionNotFoundException: Could not find session data for id 7

2] 2020-02-12 15:00:41,663 ERROR [org.kie.server.remote.rest.jbpm.UserTaskResource] (default task-228) Unexpected error during processing Process instance 1950[src.main.resources.foresight] is disconnected.: java.lang.IllegalStateException: Process instance 1950[src.main.resources.foresight] is disconnected.

at org.jbpm.process.instance.impl.ProcessInstanceImpl.getProcess(ProcessInstanceImpl.java:97)

3]2020-02-12 14:39:54,513 ERROR [org.jboss.as.ejb3.timer] (EJB default - 4) WFLYEJB0020: Error invoking timeout for timer: [id=bbc64f77-f81d-49c6-b61a-097fb793d65e timedObjectId=kie-server.kie-server.EJBTimerScheduler auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@21ffdd2a initialExpiration=Tue Feb 11 11:10:48 IST 2020 intervalDuration(in milli sec)=0 nextExpiration=null timerState=IN_TIMEOUT info=EjbTimerJob [timerJobInstance=GlobalJpaTimerJobInstance [timerServiceId=Foresight_1_1.0.0-timerServiceId, getJobHandle()=EjbGlobalJobHandle [uuid=7-1894-4474]]]]: javax.ejb.EJBException: java.lang.RuntimeException: org.drools.persistence.api.SessionNotFoundException: Could not find session data for id 7

at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:246)

at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:362)

at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:144)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)

at org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81)

at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)

at org.jboss.as.ejb3.component.singleton.ContainerManagedConcurrencyInterceptor.processInvocation(ContainerManagedConcurrencyInterceptor.java:106)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438)

at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:619)

at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)

at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:99)

at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:109)

at org.jboss.as.ejb3.timerservice.TimerTask.invokeBeanMethod(TimerTask.java:189)

at org.jboss.as.ejb3.timerservice.TimerTask.callTimeout(TimerTask.java:185)

at org.jboss.as.ejb3.timerservice.TimerTask.run(TimerTask.java:159)

at org.jboss.as.ejb3.timerservice.TimerServiceImpl$Task$1.run(TimerServiceImpl.java:1299)

at org.wildfly.extension.requestcontroller.RequestController$QueuedTask$1.run(RequestController.java:494)

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

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

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

at org.jboss.threads.JBossThread.run(JBossThread.java:485)

Suppressed: java.lang.IllegalStateException: WFLYEJB0060: Wrong tx on thread: expected Local transaction (delegate=TransactionImple < ac, BasicAction: 0:ffff7f000101:60161ee3:5e27fdb7:68fc59 status: ActionStatus.ABORTED >, owner=Local transaction context for provider JBoss JTA transaction provider), actual null

at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:80)

at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:122)

at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:256)

... 36 more

Caused by: java.lang.RuntimeException: org.drools.persistence.api.SessionNotFoundException: Could not find session data for id 7

at org.jbpm.services.ejb.timer.EJBTimerScheduler.executeTimerJob(EJBTimerScheduler.java:94)

at sun.reflect.GeneratedMethodAccessor140.invoke(Unknown Source)

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

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

at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:50)

at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:61)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)

at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:90)

at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:103)

at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:61)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:50)

at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:61)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:40)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)

at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

at org.jboss.as.ejb3.component.singleton.SingletonComponentInstanceAssociationInterceptor.processInvocation(SingletonComponentInstanceAssociationInterceptor.java:53)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:237)

... 36 more

Caused by: org.drools.persistence.api.SessionNotFoundException: Could not find session data for id 7

at org.drools.persistence.PersistableRunner.initExistingKnowledgeSession(PersistableRunner.java:231)

at org.drools.persistence.PersistableRunner$TransactionInterceptor.execute(PersistableRunner.java:588)

at org.drools.persistence.PersistableRunner$TransactionInterceptor.execute(PersistableRunner.java:563)

at org.drools.core.command.impl.AbstractInterceptor.executeNext(AbstractInterceptor.java:39)

at org.drools.persistence.jpa.OptimisticLockRetryInterceptor.internalExecute(OptimisticLockRetryInterceptor.java:102)

at org.drools.persistence.jpa.OptimisticLockRetryInterceptor.execute(OptimisticLockRetryInterceptor.java:83)

at org.drools.persistence.jpa.OptimisticLockRetryInterceptor.execute(OptimisticLockRetryInterceptor.java:44)

at org.drools.core.command.impl.AbstractInterceptor.executeNext(AbstractInterceptor.java:39)

at org.drools.persistence.jta.TransactionLockInterceptor.execute(TransactionLockInterceptor.java:73)

at org.drools.persistence.jta.TransactionLockInterceptor.execute(TransactionLockInterceptor.java:45)

at org.drools.core.command.impl.AbstractInterceptor.executeNext(AbstractInterceptor.java:39)

at org.jbpm.runtime.manager.impl.error.ExecutionErrorHandlerInterceptor.internalExecute(ExecutionErrorHandlerInterceptor.java:66)

at org.jbpm.runtime.manager.impl.error.ExecutionErrorHandlerInterceptor.execute(ExecutionErrorHandlerInterceptor.java:52)

at org.jbpm.runtime.manager.impl.error.ExecutionErrorHandlerInterceptor.execute(ExecutionErrorHandlerInterceptor.java:29)

at org.drools.persistence.PersistableRunner.execute(PersistableRunner.java:398)

at org.drools.persistence.PersistableRunner.execute(PersistableRunner.java:66)

at org.drools.core.runtime.InternalLocalRunner.execute(InternalLocalRunner.java:37)

at org.drools.core.runtime.InternalLocalRunner.execute(InternalLocalRunner.java:35)

at org.jbpm.process.core.timer.impl.GlobalTimerService$DisposableCommandService.execute(GlobalTimerService.java:346)

at org.jbpm.process.core.timer.impl.GlobalTimerService$DisposableCommandService.execute(GlobalTimerService.java:323)

at org.drools.core.runtime.InternalLocalRunner.execute(InternalLocalRunner.java:37)

at org.drools.core.runtime.InternalLocalRunner.execute(InternalLocalRunner.java:41)

at org.jbpm.persistence.timer.GlobalJpaTimerJobInstance.call(GlobalJpaTimerJobInstance.java:79)

at org.jbpm.persistence.timer.GlobalJpaTimerJobInstance.call(GlobalJpaTimerJobInstance.java:48)

at org.jbpm.services.ejb.timer.EJBTimerScheduler.executeTimerJob(EJBTimerScheduler.java:91)

... 66 more

Caused by: javax.persistence.PersistenceException: org.hibernate.HibernateException: Unable to access lob stream

at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:154)

at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:200)

at org.hibernate.internal.SessionImpl.find(SessionImpl.java:3516)

at org.hibernate.internal.SessionImpl.find(SessionImpl.java:3447)

at org.drools.persistence.jpa.JpaPersistenceContext.findSession(JpaPersistenceContext.java:79)

at org.drools.persistence.PersistableRunner.initExistingKnowledgeSession(PersistableRunner.java:229)

... 90 more

Caused by: org.hibernate.HibernateException: Unable to access lob stream

at org.hibernate.type.descriptor.java.PrimitiveByteArrayTypeDescriptor.wrap(PrimitiveByteArrayTypeDescriptor.java:123)

at org.hibernate.type.descriptor.java.PrimitiveByteArrayTypeDescriptor.wrap(PrimitiveByteArrayTypeDescriptor.java:26)

at org.hibernate.type.descriptor.sql.BlobTypeDescriptor$1.doExtract(BlobTypeDescriptor.java:48)

at org.hibernate.type.descriptor.sql.BasicExtractor.extract(BasicExtractor.java:47)

at org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:261)

at org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:257)

at org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:247)

at org.hibernate.type.AbstractStandardBasicType.hydrate(AbstractStandardBasicType.java:333)

at org.hibernate.persister.entity.AbstractEntityPersister.hydrate(AbstractEntityPersister.java:3007)

at org.hibernate.loader.plan.exec.process.internal.EntityReferenceInitializerImpl.loadFromResultSet(EntityReferenceInitializerImpl.java:305)

at org.hibernate.loader.plan.exec.process.internal.EntityReferenceInitializerImpl.hydrateEntityState(EntityReferenceInitializerImpl.java:233)

at org.hibernate.loader.plan.exec.process.internal.AbstractRowReader.readRow(AbstractRowReader.java:103)

at org.hibernate.loader.plan.exec.internal.EntityLoadQueryDetails$EntityLoaderRowReader.readRow(EntityLoadQueryDetails.java:261)

at org.hibernate.loader.plan.exec.process.internal.ResultSetProcessorImpl.extractResults(ResultSetProcessorImpl.java:122)

at org.hibernate.loader.plan.exec.internal.AbstractLoadPlanBasedLoader.executeLoad(AbstractLoadPlanBasedLoader.java:122)

at org.hibernate.loader.plan.exec.internal.AbstractLoadPlanBasedLoader.executeLoad(AbstractLoadPlanBasedLoader.java:86)

at org.hibernate.loader.entity.plan.AbstractLoadPlanBasedEntityLoader.load(AbstractLoadPlanBasedEntityLoader.java:188)

at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:4269)

at org.hibernate.event.internal.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:511)

at org.hibernate.event.internal.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:481)

at org.hibernate.event.internal.DefaultLoadEventListener.load(DefaultLoadEventListener.java:222)

at org.hibernate.event.internal.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:281)

at org.hibernate.event.internal.DefaultLoadEventListener.doOnLoad(DefaultLoadEventListener.java:124)

at org.hibernate.event.internal.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:92)

at org.hibernate.internal.SessionImpl.fireLoad(SessionImpl.java:1257)

at org.hibernate.internal.SessionImpl.access$1900(SessionImpl.java:207)

at org.hibernate.internal.SessionImpl$IdentifierLoadAccessImpl.doLoad(SessionImpl.java:2874)

at org.hibernate.internal.SessionImpl$IdentifierLoadAccessImpl.load(SessionImpl.java:2848)

at org.hibernate.internal.SessionImpl.find(SessionImpl.java:3483)

... 93 more

Caused by: org.postgresql.util.PSQLException: ERROR: large object 201785 does not exist

at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)

at org.postgresql.core.v3.QueryExecutorImpl.receiveFastpathResult(QueryExecutorImpl.java:794)

at org.postgresql.core.v3.QueryExecutorImpl.fastpathCall(QueryExecutorImpl.java:586)

at org.postgresql.fastpath.Fastpath.fastpath(Fastpath.java:105)

at org.postgresql.fastpath.Fastpath.fastpath(Fastpath.java:146)

at org.postgresql.fastpath.Fastpath.getInteger(Fastpath.java:158)

at org.postgresql.largeobject.LargeObject.<init>(LargeObject.java:102)

at org.postgresql.largeobject.LargeObjectManager.open(LargeObjectManager.java:252)

at org.postgresql.largeobject.LargeObjectManager.open(LargeObjectManager.java:235)

at org.postgresql.jdbc.AbstractBlobClob.getLo(AbstractBlobClob.java:269)

at org.postgresql.jdbc.AbstractBlobClob.getBinaryStream(AbstractBlobClob.java:114)

at org.hibernate.type.descriptor.java.PrimitiveByteArrayTypeDescriptor.wrap(PrimitiveByteArrayTypeDescriptor.java:120)

... 121 more

[karan kanojiya]

@maciej any input on this ?

[karan kanojiya]

Hi Maciej,

Any inputs on facing exceptions mention above?

Also while changing runtime strategy from singleton to per process instance, old instance based on singleton strategy we cannot complete that instance until we change their runtime strategy to a per-process instance strategy.

So I found your blog

http://mswiderski.blogspot.com/2014/11/process-instance-migration-made-easy.html

So if I follow the above step I will have to change one by one old process instance to change their strategy.

Can we select all old process instances based on the singleton strategy at one time and change their strategy?

[karan kanojiya]

Any input on this ?

[karan kanojiya]

@maciej badly stuck in production due to this issue
Any resolution

[karan kanojiya]

Hi All

Any resolution on this issue ?

[karan kanojiya]

So should i considered this as a bug ?
Since i have posted all my logs,exception & scenario too. I am not getting any resolution for this.

Regards,
Karan Kanojiya

[Donato Marrazzo]

Maybe it's a bug, maybe it's a misuse.

The log is not enough clear.

[karan kanojiya]

If it is a bug then how we will get its resolution.

Misuse?

Uploaded with proper Screenshot and Complete Logfile in attachments, Now what else I should be uploading for more clear logs?

Please find log attachments for more clear logs.

[Donato Marrazzo]

Hi Karan,

you should consider that this is a forum to get some help on how to use the product without any guarantee or SLA on the problem resolution.

If you need support on a production environment with someone that spend time to analyze your unique situation you have to buy a subscription: 

https://www.redhat.com/en/technologies/jboss-middleware/process-automation-manager

So you will be entitled to open a case where experts will solve your problem.

If you think that it's a bug you have to provide a reproducer: i.e. a sample project and set of instructions on how to reproduce the problem in a deterministic fashion.

In this case you can open a Jira case: https://issues.redhat.com/secure/Dashboard.jspa

Even in this case, there is no guarantee that your case will be solved in the time frame you expect.

This is how the open source works: engineers have their own priorities and solve the problems accordingly to those.

Thank you for understanding