If you have an error "Failed to deserialize statedump from server ""java.lang.ClassNotFoundException"
you should read Oracle Document:
"How To Avoid De-Serialize Statedump Errors While Starting Manage Servers in Cluster Environment (java.lang.ClassNotFoundException) (Doc ID 796357.1)"
The solution is to start first the Admin, and only when this is running you should start the managed servers one by one, and not in parallel (the Oracle doc says the opposite). Don't ask me questions, I have no clue.
The other possible root cause could be an invalid EAR, try rebuilding it and redeploying it.
http://oraclefmwadmins.blogspot.ch/2014/07/bea-000140-failed-to-deserialize.html
you should read Oracle Document:
"How To Avoid De-Serialize Statedump Errors While Starting Manage Servers in Cluster Environment (java.lang.ClassNotFoundException) (Doc ID 796357.1)"
The solution is to start first the Admin, and only when this is running you should start the managed servers one by one, and not in parallel (the Oracle doc says the opposite). Don't ask me questions, I have no clue.
The other possible root cause could be an invalid EAR, try rebuilding it and redeploying it.
http://oraclefmwadmins.blogspot.ch/2014/07/bea-000140-failed-to-deserialize.html
Reason:
Corrupted EJB files due to temporary communication failure between WebLogic admin and managed server instances
Solution:
1. Stop Weblogic Managed/Admin Server
2.Delete the directory under $DOMAIN_HOME/servers//tmp/_WL_user/
3.Restart Admin/Managed servers. The file will create automatically.