This content has been marked as final. Show 2 replies
Here is what I would do in such a scenario:
1. Change the log level to "debug" using weblogic server console and see if I can catch any errors.
2. If 1 does not work then I would go back to my project workspace and create a blank web project, ear project with the name I wanted and then copy the resources (java, jsps etc.) to this newly created web project and ear project, bundle it again and see if it works.
3. Try to hit a portal, portlet or even jsp if it works. In my experience 500 error is sporadic in weblogic portal applications.