method annotations "moved" by TC instrumentation

I've the same issue when trying to use terracotta for clustering a jboss seam session.

Seam heavily uses annotations on its components and when an annotated methods will be rewritten by terracotta instrumentation due to auto-locking, the annotation moves to the new private method which will be than probably called by the original (and public) method.

When now seam comes to search annotated methods, it finds the new private method instead of the original public method and that obvouisly triggers errors. i.e. seam tries to get the wrong annotated method by calling class.getMethod():

java.lang.NoSuchMethodException: org.jboss.seam.security.Identity.__tc_wrapped_create()
java.lang.Class.getMethod(Class.java:1581)
org.jboss.seam.Component.callComponentMethod(Component.java:2208)
org.jboss.seam.Component.callCreateMethod(Component.java:2134)

Normally it should try to get public org.jboss.seam.security.Identity.create() which was original annotated, but because terracotta moved the annotation seam tries now to get the private __tc_wrapped_create(), which is not right and also fails due to no private methods are available by class.getMethod()

above is something written about a workaround. Where can i find that? How can I fix this issue?

Btw: Are there any experiences/project known with clustering seam sessions with terracotta?

there is also written that it is fixed in trunk. maybe someone can tell in which revision, so that i can try to patch my terracotta version with the changes from this revision. thanks in advance

here is a forum thread disussing this issue as well: http://forums.terracotta.org/forums/posts/list/0/3550.page

This issue is not yet fixed anywhere. This item is labeled to be fixed in trunk but that has not yet happened.

The only workaround is to move to block synchronization (instead of synchronized access on the method). Eg.

synchronized void foo() { // }

to

void foo() {
synchronized(this) { // }
}