MemorySafeUndeclaredThrowableStrategy class not found [SPR-11782]

[spring-projects-issues]

Batbayar Bazarragchaa opened SPR-11782 and commented

I'm having problem org.springframework.cglib.transform.impl.MemorySafeUndeclaredThrowableStrategy class not found exception when I enable following configuration:

<security:global-method-security pre-post-annotations="enabled" />
or
tx:annotation-driven/
I found this class in spring 4.0.1, but cannot find in later versions.
What happened to this class? How to resolve my error?

---

Affects: 4.0.2, 4.0.3, 4.0.4

Issue Links:

• aop:scoped-proxy may fail with LinkageError: loader attempted duplicate class definition for name [SPR-11398] #16025 aop:scoped-proxy may fail with LinkageError: loader attempted duplicate class definition for name

Referenced from: commits 297e4ee

[spring-projects-issues]

Batbayar Bazarragchaa commented

Forum post created by me:
http://forum.spring.io/forum/spring-projects/web/748760-memorysafeundeclaredthrowablestrategy-removed-in-spring-4-0-2-and-afterwards?_=1400051765063

[spring-projects-issues]

Juergen Hoeller commented

MemorySafeUndeclaredThrowableStrategy was a workaround for a CGLIB 3.0 issue which got fixed in 3.1, so we don't need to set that custom strategy anymore. This was only noticed in the Spring Framework 4.0.1 timeframe, so it got removed for 4.0.2... We expected no external code to depend on this.

So where exactly does that MemorySafeUndeclaredThrowableStrategy dependency come from? tx:annotation-driven is part of Spring Framework itself, so should work fine in 4.0.4 with CGLIB 3.1 there... However, the security:* namespace is part of Spring Security, so maybe you're using an older version there? Could you double-check your Spring Security version?

If the problem remains, we could temporarily reintroduce the MemorySafeUndeclaredThrowableStrategy class for Spring Framework 4.0.5. That said, it definitely won't be there in 4.1.x, so whatever external dependency you're running into will have to be fixed/removed by then.

Juergen

[spring-projects-issues]

Batbayar Bazarragchaa commented

Yes I used spring security 3.2.3 which is the latest stable release. Should I use spring security 4.0?

Also I'm using hibernate 4.3.5.Final which is also the latest stable release.

[spring-projects-issues]

Juergen Hoeller commented

Actually, according to your stacktrace, could it be that you have an old spring-aop jar on your classpath, running against a new spring-core.jar? When using both jars from the Spring Framework 4.0.4 release, no such NoClassDefFoundError should occur...

Juergen

[spring-projects-issues]

Batbayar Bazarragchaa commented

Ah I have spring-aop-3.2.8.RELEASE.jar in my classpath. Its from spring security. I try to exclude and add newer version and post results back.

[spring-projects-issues]

Juergen Hoeller commented

Even it looks like using the same versions of Spring modules will solve the problem, I've reintroduced MemorySafeUndeclaredThrowableStrategy in deprecated form for the 4.0.x line, kept around for external code depending on it. Finally removed (i.e. not reintroduced) in Spring Framework 4.1.

Juergen

[spring-projects-issues]

Batbayar Bazarragchaa commented

I excluded and its downloaded spring aop 4.0.4, then everything is working fine, thank you for the hint :)