Problem description
MyEclipse during the running service because of exceptions to close or directly close the IDE will occasionally lead to server errors
This kind of server error is usually led by a null pointer exception prompting a large chain of exceptions, all due to the error file generated by the exception closure
Solution:
Method 1
You can delete the. Metadata file directly, and it will be automatically regenerated after restarting MyEclipse
Method 2
Delete the following file under MyEclipse and restart to solve the problem
.metadata.plugins\org.eclipse.core.runtime.settings
Similar Posts:
- MyEclipse open JSP report unhandled event loop exception no more handles error
- Solve the initialization Java tooling exception information when eclipse starts
- After modifying Tomcat’s server.xml, the Tomcat deployment project reported an error: removing observe files from server… Could not clean server
- Invalid project name: Project “XXX” already exists
- MyEclipse startup error: ‘building workspace’ has been accounted for a problem solution
- [How to Solve Eclipse Issue] Open type (Ctrl-Shift-T) Can Not Found
- Specified VM install not found Error [How to Solve]
- Eclipse debug has no response and no error report
- Several common error reporting and startup problems of Tomcat