Technical Blog Post
Error BMXAA3765E after rebuliding and redeploying in a customized environment
With application development, it is normal to rebuild and redeploy the Maximo ear file as part of the admin activities.
Have you encountered this error after a simple rebuild and redeploy of your Maximo ear and all of a sudden no one can access one or some applications?
Help! No users can access this application to complete their daily duties!
1. You checked that you can login, start center appears ok and other apps are working.
2. You also checked to ensure the rebuild and redeploy process did not encounter any issues.
3. You have tried to clear the WebSphere cache and redeploy the maximo ear.
So, what happened?
This typical behaviour is usually seen where there have been some sort of customization to the application in the form of code java class modifications.
Let's take a closer look at what is happening behind the scenes with the logs to see if we can discover something more to this error.
From the sytsemerr.log at the time the message was seen, we can see the below:
[7/2/15 18:10:08:195 SGT]
java.lang.ClassFormatError: JVMCFRE076 bad magic number; class=psdi/app/po/PORemote, offset=0
Caused by: java.lang.ClassFormatError: JVMCFRE076 bad magic number; class=psdi/app/po/PORemote, offset=0
A ClassFormatError is usually thrown by the JVM when it attempts to read a class file and determines that the file is malformed ortherwise cannot be interpreted as a class file.
From the above error, the related class with the issue is coming from psdi/app/po/PORemote
a) Compare with a working environment the differences related to this class.
b) Clear WebSphere class cache
We want to ensure that the cache is not holding on to previous versions of the classes, and to remove any cache that may have been corrupted.
As a good practice, ensure you always document any changes or customizatoin specific to the environment.