NPE UnitOfWork Thrown in FlowManager

[timkruzel]

I am opening this ticket in behalf of Venkatesh as he is on holiday in
Bangalore. Here is a snippet from your exchange with him yesterday.
Thanks,
Tim (timothy.kruzel@ge.com)

Please create a ticket for this issue.
Thanks,
Martin
Am 30.08.2011 11:36 schrieb "Venkatesh Laguduva"
lbvenkatesh@gmail.com:

I am still struck at this issue; Has any body used replay feature with
Camel
2.5?

Thanks & Regards
Venkatesh Laguduva

On Tue, Aug 30, 2011 at 9:45 AM, Venkatesh lbvenkatesh@gmail.com
wrote:

Please note that I am using Camel 2.5!

On Aug 29, 11:54 pm, Venkatesh Laguduva lbvenkat...@gmail.com
wrote:

Hi,
I am trying to replay a message and I am getting a
NullPointerException
at

org.apache.camel.spring.spi.TransactionErrorHandler.process(TransactionErrorHandler.java:84).

It looks to be happening because the Exchange reconstructed from
the
PlatformPacket has got a null UnitOfWork. I do not see a place
where
UnitOfWork is being set. Am I missing something? or is this a
bug?

Thanks & Regards
Venkatesh Laguduva

[timkruzel]

The issues described above are occurring with IPF 2.2.4

[krasserm]

Does the NPE also occur with the latest development snapshot? If yes, please clone the project, and create a failing unit test (in platform-camel-flow) for reproducing the problem.

Thanks,
Martin

[timkruzel]

The files are attached. I suspect that you may spend some time getting the
library dependencies sorted out.

Also, I think that you will have to comment out the following from the context.xml file:

I am still sorting out libraries in my development environment so I have not
been able to load the JUnit.

Venkatesh, relative to our development environment, what project did you
put those files in? I created a new separate project, but based upon all
of the library build path dependencies that I ran into, I am guessing that
you did not do that. Did you put it under DataLinkCore? I will try that.

Venkatesh and Martin,
Thanks for all of your help

Tim

[timkruzel]

Martin,
This JUnit does indeed duplicate the error. I moved the test files into a different project in our
development environment (DataLinkCore) and it does work properly (throws the Flow related
Exceptions).

And as I suggested in the prior e-mail you should comment out the DataLinkQueueProducer
bean definition from the context.xml file.

And as you would expect all of the database connection definitions will have to be changed
if you try to run this in your development environment (though I suspect that you will have your
own setup).

Please let us know if you have any questions.

Venkatesh, thanks for working on this during your holiday. Great work.
Ganesh will be appreciative (as am I).

Thanks all,
Tim