Loading from an external classpath environment variable might be the problem and not supported anymore. Have you tried putting the shiro jars into the .war (which is inside the ear file) instead?
I have little knowledge about weblogic, but I know from other application servers they will encapsulate classloaders from each other for security reasons. If you do not want to have the jars in your ear/war file, Weblogic possibly provides other means to load shared libraries. Best regards, Ben On Fri, 20 Nov 2020, 21:36 Indrajit57, <[email protected]> wrote: > Thanks Brian for your quick response. Here are the answers to your > questions: > > > What how are you deploying your application? - deploying as EAR > > Was the WAR/EAR changed between deployments if so what has changed? Have > you > diffed the contents? – No Changes are made > > Is the `shiro-web` jar on your classpath? If not how was it getting loaded > in with your previous deployment? Was it on some shared classpath? - > Yes > , shiro-web is in classpath > > > CLASSPATH= > > C:\beaUtil\util\shiro-aspectj-1.2.2.jar;C:\beaUtil\util\shiro-cas-1.2.2.jar;C:\beaUtil\util\shiro-core-1.2.2.jar;C:\beaUtil\util\shiro-ehcache-1.2.2.jar;C:\beaUtil\util\shiro-spring-1.2.2.jar;C:\beaUtil\util\shiro-web-1.2.2.jar; > C:\beaUtil\util\slf4j-api-1.6.1.jar; > > > > > -- > Sent from: http://shiro-user.582556.n2.nabble.com/ >
