[chrisplough]

Hello!

Issue:

With several clients, we've noticed strange UI issues with OTM v5.5 CU2. This manifested itself in various ways, and even more frustrating was the fact that it was different for each client. Some of the symptoms were:

• Inability to use the "v" buttons to verify input in fields
• Random inability to open screens and finders
• Top tab bar losing it's formatting
• Error messages when trying to open various tabs like:

Error Found Handling The Request.
shipment shipment/feasibility_code not found

• Errors like the following in the glog.web.log file:

org.apache.jasper.JasperException: Unable to load class for JSP

• etc...

Resolution:

We found that the root of these errors were leftover jspx from older code releases (CU01, GA) that needed to be removed. Here are the steps to resolve:

1. Shutdown your OTM web server
2. Change directories to <otm_install_dir>/tomcat
3. Rename the work subdirectory to work.old
4. Create a new (empty) work subdirectory
5. Restart the OTM web server

That's it! OTM will create new jspx files as it runs and your UI issues will be resolved.

I hope this helps!

--Chris