Moving from WebSphere to Oracle WebLogic, getting a ClassNotFoundException

springframeworkweblogic

I was given an "EAR" file and told to try to deploy it on an Oracle WebLogic server. I had successfully deployed it on a IBM WebSphere server. When I attempt to start it on WebLogic, however, I get the following error:

Could not load user defined listener:
org.springframework.web.context.ContextLoaderListener
java.lang.ClassNotFoundException:
org.springframework.web.context.ContextLoaderListener
at
weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:296)
at
weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:269)
at
weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at
weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
at
weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:37)
at

I've checked that spring.war is in WEB-INF/lib in the appropriate war files.

What am I missing?

Best Answer

If you want it to load libs from your WEB-INF/lib directory then you need to add something to your weblogic.xml file (this should be in WEB-INF).

<weblogic-web-app>
   <container-descriptor>
      <prefer-web-inf-classes>true</prefer-web-inf-classes>
   </container-descriptor>
</weblogic-web-app>

Hope that helps.

Related Solutions

Oracle: Can Weblogic 11G run PL/SQL code like App Server 10G

The PL/SQL runs in the database, and so any changes on the application server won't affect the actual execution of PL/SQL code. However, it may still impact on the final result, eg. how the application presents itself to the user, depending on how the application is built.

As for PL/SQL compatibility between Oracle Datababase 11G and 10G you will likely have to do minor modifications in the code. I believe Oracle is claiming backwards compatibility, but in my experience with previous releases there are always a few things that needs tweaking.

Oracle Weblogic – Can’t Start Managed Server in Weblogic 10.3.2

The problem was that I was running wlst.sh from my home directory. wlst.sh must be run from $WL_HOME/common/nodemanager directory, because it uses the nodemanager.properties in the current directory.

The nodemanager.properties that solved my problem looks like this:

DomainsFile=/u01/app/oracle/product/11.1.1/mw/wlserver_10.3/common/nodemanager/nodemanager.domains  
LogLimit=0  
PropertiesVersion=10.3  
AuthenticationEnabled=true  
NodeManagerHome=/u01/app/oracle/product/11.1.1/mw/wlserver_10.3/common/nodemanager  
JavaHome=/u01/app/oracle/jrmc-3.1.2-1.6.0/jre  
#JavaHome=/usr/java/jdk1.6.0_18  
#LogLevel=INFO  
DomainsFileEnabled=true  
StartScriptName=startWebLogic.sh  
ListenAddress=  
NativeVersionEnabled=true  
ListenPort=5556  
LogToStderr=true  
SecureListener=true  
LogCount=1  
StopScriptEnabled=false  
QuitEnabled=false  
#LogAppend=true  
LogAppend=false  
StateCheckInterval=500  
#CrashRecoveryEnabled=false  
CrashRecoveryEnabled=true  
StartScriptEnabled=true  
LogFile=/u01/app/oracle/product/11.1.1/mw/wlserver_10.3/common/nodemanager/nodemanager.log  
LogFormatter=weblogic.nodemanager.server.LogFormatter  
ListenBacklog=50

Related Topic