Linux under WebLogic reflectionutils.makeaccessible (ljava/lang/reflect/constructor;) v Exception __oracle

Project installed on the local Windows machine WebLogic deployment Normal, migrated to Linux (64-bit) installed 32-bit weblogic10.3 abnormal

<jan 2013 5:13:23 PM cst> <Error> <Deployer> <BEA-149231> <unable to set the activation STA
Te to True for the application ' Eteller '. Weblogic.application.ModuleException:at weblogic.servlet.internal.WebAppModule.startContexts (Webappmodule.java: 1510) at Weblogic.servlet.internal.WebAppModule.start (webappmodule.java:482) at Weblogic.application.inter Nal.flow.modulestatedriver$3.next (modulestatedriver.java:425) at Weblogic.application.utils.StateMachineDriver.nextState (statemachinedriver.java:52) at Weblogic.application.internal.flow.ModuleStateDriver.start (modulestatedriver.java:119) truncated. The log file for complete stacktrace caused By:java.lang.NoSuchMethodError: Org.springframework.util.ReflectionUtils.makeAccessible (Ljava/lang/reflect/constructor) V at Org.springframework . Beans. Beanutils.instantiateclass (beanutils.java:125) at Org.springframework.beans.BeanUtils.instantiateClass (Beanutils.java:104) at Org.springframework.web.context.ContextLoader.createWebApplicationContext (Contextloader.java : 236) at Org.springframework.web.context.ContextLoader.initWebApplicationContext (contextloader.java:184) A
        T org.springframework.web.context.ContextLoaderListener.contextInitialized (contextloaderlistener.java:49) truncated. The log file for complete StackTrace

Online search solutions are said to be Careful checking is due to two packages Asm2.0.3.jar and Asm.jar as well as there are Spring-core.jar and Spring-2.0.5core.jar, packet conflicts, delete Asm2.0.3.jar and Spring-2.0.5core.jar after reboot normal , but looked up the jar and WebLogic under Lib and the public module and service did not have these two packages, our system is not used,

Then go to the official website to download the latest 32-bit 12 version and 64-bit version of 10.3weblogic, error still, eliminate WebLogic problems,

And then the log out of the boot when the error found to find the package path is

[Loaded org.springframework.util.ReflectionUtils from File:/bea/app/products/web-inf/lib/spring-1.2.x.jar]

Should be the conflict between Spring-1.2.x.jar and Spring-core-3.0.3.release.jar, should be the makeaccessible side of the call to the Reflectionutils class in Spring-core-3.0.3.release.jar Law, but went to the Spring-1.2.x.jar to find

The final solution is to replace the packages used in the system

Web-inf/lib/spring-context-support-2.5.6.jar
Web-inf/lib/spring-1.2.x.jar
web-inf/lib/ Spring-jms-3.0.3.release.jar
Web-inf/lib/spring-tx-3.0.3.release.jar
web-inf/lib/ Spring-core-3.0.3.release.jar
Web-inf/lib/spring-context-3.0.3.release.jar

Replace All to

Web-inf/lib/org.springframework.beans-3.0.3.release.jar Web-inf/lib/org.springframework.jms-3.0.3.release.jar Web-inf/lib/org.springframework.jdbc-3.0.3.release.jar web-inf/lib/ Org.springframework.aspects-3.0.3.release.jar Web-inf/lib/org.springframework.test-3.0.3.release.jar WEB-INF/lib /javassist-3.12.0.ga.jar Web-inf/lib/org.springframework.instrument.tomcat-3.0.3.release.jar WEB-INF/lib/ Org.springframework.web.servlet-3.0.3.release.jar Web-inf/lib/org.springframework.oxm-3.0.3.release.jar WEB-INF/
Lib/org.springframework.web.portlet-3.0.3.release.jar Web-inf/lib/org.springframework.web-3.0.3.release.jar
Web-inf/lib/org.springframework.asm-3.0.3.release.jar Web-inf/lib/org.springframework.context-3.0.3.release.jar Web-inf/lib/org.springframework.transaction-3.0.3.release.jar web-inf/lib/ Org.springframework.core-3.0.3.release.jar Web-inf/lib/org.springframework.expression-3.0.3.release.jar WEB-INF/ Lib/org.springframework.web.struts-3.0.3.release.jar Web-inf/lib/org.springframework.orm-3.0.3.release.jar Web-inf/lib/org.springframework.context.support-3.0.3.release.jar WEB-INF/lib/hibernate3.jar Web-inf/lib/org.springframework.instrument-3.0.3.release.jar web-inf/lib/ Org.springframework.aop-3.0.3.release.jar

Finally, the problem was solved, but it left a doubt that it was a 64-bit Linux system and WebLogic, but there was no problem at the time, but the deployed colleagues had already gone, so I started

Think it should be weblogic the public part of the jar conflict, unfortunately looked at the WebLogic also did not find a conflict with the part of the end can only go the wrong way, replace the jar, replace a heap of jar start is no problem, but may have some impact on the application