Skip to main content
Kofax

Unable to open Payables Suppliers page after applying patch Oracle log4j patch 33672402 R12 TXK C

Article # 3037517 - Page views: 116

Issue

  • Due to the vulnerability with log4j, Oracle has released critical patch  33672402:R12.TXK.C
  • After applying the patch the iSupplier page will show the following error when you attempt to open it:

Error stack has the below error.

Error Stack:

## Detail 0 ## java.lang.NoClassDefFoundError: Could not initialize class com.markview.oracle.apps.util.MVFrameworkUtilsat com.markview.oracle.apps.util.webui.MVAutoAttachCO.processRequest(MVAutoAttachCO.java:76)at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:673)at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:283)at oracle.apps.fnd.framework.webui.beans.layout.OAStackLayoutBean.processRequest(OAStackLayoutBean.java:362)at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:1116)at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:1083)at
 

 

Cause

The patch is causing an issue with the personalization by removing contents from java_top. 

Solution

Download the following fix here.

This includes the classes that are generally the same as copied to $JAVA_TOP during MarkView Oracle Objects installation, except of the updated class com\markview\oracle\apps\util\MVFrameworkUtils.class and new class com\markview\oracle\apps\util\Logger.class. 

 

 

1. Log in as the EBS owner user

 

2. Backup $JAVA_TOP directory

 

3. Copy mv_java_top.zip to $JAVA_TOP

 

cp mv_java_top.zip $JAVA_TOP

 

4. Go to $JAVA_TOP directory

 

cd $JAVA_TOP

 

5. Remove the previous customall.jar file

 

rm customall.jar

 

6. Remove the previous com/markview folder

 

rm -R com/markview

 

7. Optionally remove org/apache/log4j directory if it exists

 

rm -R org/apache/log4j

 

8. Unzip mv_java_top.zip file

 

unzip mv_java_top.zip

 

9. Recreate customall.jar file with the following command (it requests apps credentials, all other required custom classes should be in $JAVA_TOP)

 

adcgnjar

 

10. Bounce the EBS

 

NOTE: For Multi-node environments, it depends on how the multi-node has been setup in the environment. If each node uses its own COMMON_TOP (JAVA_TOP) then the fix should be applied on each node. If all nodes share the same COMMON_TOP (JAVA_TOP) then the fix should be applied only once.

Level of Complexity 

High

 

Applies to  

Product Version Build Environment Hardware
MarkView 8.2+    33672402:R12.TXK.C  

 

  • Was this article helpful?