Maximo Open Forum

Hey Everybody.

Curious if anyone has thoughts on old java customization failures after upgrades/add ons?

These customizations are about a decade old and so far have made it through all the upgrades unscathed.

Recently Scheduler was installed and the graphical viewer threw an error when launching.

 java.lang.NoClassDefFoundError: sc.plust.app.workorder.SCPlusTWO_Stub (initialization failure)

I rebuilt the stub in the dev environment and everything is happy.

We moved to test(which is exactly like dev) and the same fix fails. This is a clustered environment(WebSphere) and I have verified the new stub is in both cluster members.

I removed all the cache (deleted the temp folder) and restarted, syncronized nodes.

Rebuilt stub on test server(as opposed to copying new stub from dev)

What could I be missing? or is there a good way to debug this?

Thanks!

doug

Hi Doug,

It sounds like you're already taking the steps that I would recommend for getting the new stub deployed; though, I think there are a couple things you could try:

• Try clearing the other cache files on the test servers - here is an IBM article listing the locations: https://www.ibm.com/support/pages/clearing-websphere-temporary-file-caches-maximo-asset-management then restart and resync nodes
• Rebuild the ear file with the updated stub file:
  • Copy the stub file to the appropriate folder to be included in the ear file build process
  • Build the ear file - I'd recommend printing the output to a text file for future reference since the command prompt window shows a limited number of output lines. Watch for any errors with the classpath or the stub file itself
  • After rebuilding the ear file on the test server, double-check that the stub file is included in the ear file
    • If it's missing, double-check that the folder containing the stub file is included in the classpath for the build ear process
  • After deploying the rebuilt ear file on the test server, double-check that the stub file is in the included in the deployed folder on both nodes: this would be in [AppServer_Path]/installedApps/[Cell]/MAXIMO.ear/businessobjects.jar or maximouiweb.war
• Alternatively, you could also copy the new stub file to the deployed folders on both nodes. This would only be a temporary solution since the deployed folder would get replaced any time a new ear file is deployed, but it can help verify that the stub file is working in the environment and is in the location that Maximo expects.

In terms of debugging, I believe you're already using the process that I'd recommend: watching the logs on startup and when using the graphical viewer.

Please let me know if this helps or if you encounter the same error.

Regards,

     Derek