0

I was recently trying to solve class cast exception in our web application. After few tests have found out that the classloader information for our web application right after application server restart are different from classloader information after webapp restart/update (without app server restart).

Classloader information were retrieved using the Manage modules - View Module class loader - Export in the Websphere administration console.

The items (paths to webapp .jar files) in exported XML are the same. But some of the items (as I understand it - these are the classes in webapps' classloader) are different.

Could anybody explain why?

Thanks.

Update: Here is the difference which is maybe the main problem (I keep getting ClassCastException on XMLSignatureFactory in my log file). This class is contained in xmlsec library and this library is deployed with our webapp war file. The classloader order is set to PARENT LAST, but it seems like sometimes the XMLSignatureFactory from IBM JDK is loaded instead of the xmlsec implementation (after redeploy).

Difference of loaded classes

I have described the exception further in this post. After I have changed the settings in MANIFEST.MF file and set up the servlet listener, I could get the application working after every restart, but the redeploy problem still occurs (which is quite annoying).

Community
  • 1
  • 1
shimon001
  • 733
  • 9
  • 24
  • Unless you can give more specific details, I think it's unlikely anyone will be able to help. Are the different items names of JAR files or modules or shared libraries? In what way are they different? Can you show a before and after? – Brett Kail Dec 28 '14 at 01:30
  • @bkail - I have updated the post. Hope this will describe my problem better. – shimon001 Jan 08 '15 at 15:14

1 Answers1

0

I got the same problem here. To fix that issue, push xmlsec jar to AppServer\classes then we can override IBM JDK by our lib

Trung Pham
  • 125
  • 7