topic Re: TimerBoundaryEvent - Not recognizing Spring Bean in Loop in Alfresco Archive

TimerBoundaryEvent - Not recognizing Spring Bean in Loop

tidetom — Fri, 03 Jun 2011 01:44:53 GMT

Hi all,I have a tricky problem that I've been trying to solve all day, and can't seem to figure out. Hoping you can help…I have a TimerBoundaryEvent placed on a Java Receive Task in my process flow. The flow itself is somewhat of a loop. The way that my process flow works is as follows: (simplifi

Re: TimerBoundaryEvent - Not recognizing Spring Bean in Loop

frederikherema1 — Mon, 06 Jun 2011 08:20:13 GMT

Tom,

The bean you are referring to, is this a Session-scoped bean or just a regular one? Perhaps something to do with the fact the job's are executed in another thread.

Can you create a simple test-case with a process that shows the bug you are describing?

Re: TimerBoundaryEvent - Not recognizing Spring Bean in Loop

tidetom — Tue, 07 Jun 2011 01:30:52 GMT

Hi Frederik,

Thanks so much for getting back…

The bean you are referring to, is this a Session-scoped bean or just a regular one?

This is just a standard Spring bean.

Perhaps something to do with the fact the job's are executed in another thread.

Yeah, I was kind of thinking the same thing. It's almost like the reference to the Spring context is getting put up for garbage collection on the original thread, given the inconsistency across executions. If the original context was tied to the process execution prior to the job, then if that process execution goes away, the context would, potentially, do the same? But then I suppose this would likely be seen in other scenarios that didn't involve looping. Hmmm….

Can you create a simple test-case with a process that shows the bug you are describing?

No problem, I'll put something together and reply to this post with the sample. It would probably be good for me to dial down my process into the essential elements causing this anyways. I'll post back soon.

Thanks again,
Tom