1

I have an application deployed on Weblogic and because of a lock contention generated by a Xerces bug i would like to 'force' Weblogic to use the correct jar where the bug is already fixed.

http://svn.apache.org/viewvc?view=revision&revision=558581 (xerces bug fixed)

Is there a way to be sure that the class from a specific jar is loaded and used by my application.

By default weblogic is using the old buggy Xerves in multiple internal librares:

com.bea.core.apache_1.2.0.0.jar
com.bea.core.apache.xercesImpl_2.8.1.jar

Thanks

JoseK
  • 31,141
  • 14
  • 104
  • 131
Cris
  • 4,947
  • 6
  • 44
  • 73
  • 1
    You have to set the new JAR in startWeblogic script before other jars. see this link for more options http://stackoverflow.com/q/7187581/289396 you can also try the `prefer-webinf-classes` with the new JAR instead of native Weblogic jar – JoseK Jun 12 '13 at 07:19
  • I can't use...prefer-webinf-classes.It is an application that I do not package ... – Cris Jun 12 '13 at 08:42

1 Answers1

1

One way is to modify the CLASSPATH of Weblogic startup scripts so that it contains the desired jar before the jar containing the buggy version of the library.

You can modify e.g. domain/bin/setEnv.sh.

Use -verbose:class to verify that the correct version of the Class is loaded.

Aleš
  • 8,896
  • 8
  • 62
  • 107