Banner Workflow Production Issue

Outage category: 
Applications
Location: 
All locations
Status: 
Open
Resolved alert: 
03/30/2020 12:16 pm

When attempting to log into Banner Workflow, users got a message that the workflow engine was not running.It looked like it was running on the server.

Initial symptoms: 

No one could log into the Workflow application

Duration: 
03/30/2020 11:09 am - 03/30/2020 12:16 pm
Impact to Mason: 

Banner Workflow users and users attempting to approve travel authorizations.

Affected Services: 
Workflow
Other Affected Services: 
Travel authorizations
ROOT CAUSE ANALYSIS
Cause: 

Part of Banner Workflow application named “workflow engine” stayed as “offline” on workflow website even though the engine was started up on the Linux server. That affected workflow services and Mason’s travel system. Banner Workflow is running on Oracle WebLogic 12.2.1.3 with Java 1.8.0_231 Oracle security patches p28186730_139400_Generic and p29909359_139400_Generic were applied on March 29. Oracle changed security policy on newer Java version, which blocked RMI connection that Workflow needs.

Resolution: 

The issue has been fixed after the following Oracle WebLogic configuration parameters were changed:

-Dweblogic.oif.serialFilterMode=combine

-Dweblogic.oif.serialFilter=java.rmi.server.RemoteObject

Prevention: 

Working with vendor to determine how to prevent future issues.

STATISTICS
Service Team: 
DBA Team