I found another reference to the dao layer which references the spring jpatemplate and fixed the first problem and everything now starts up correctly.
I now have a problem when a method in a clustered object gets invoked.
The class is definitely included in the instrumentation and i have an
autolock on a method higher up in the execution process.
Does terrocatta recognise synchronized(this) as a boundary?
Do locks have to be configured for every method or just for the top level invocation?
The cause may be one or more of the following:
* Terracotta locking was not configured for the shared code.
* The code itself does not have synchronization that Terracotta
can use as a boundary.
* The class doing the locking must be included for instrumentation.
* The object was first locked, then shared.
Hi..i provides hello world spring applications here,
1)class name: A class name is the implementation of the bean class that is described in the bean definition.
2)bean behavioral configuration elements: Here we define the bean behavior that is bean initialization, dependency checking mode, destruction methods etc.
3)constructor arguments and property values efines the no of arguments and the property values that are to be set in the newly created bean.