This content has been marked as final. Show 9 replies
Thank you for your help!
I believe that I was able to narrow down the problem. I tested these scenarios:
- created a new weblogic domain using configuration wizard; added server to the Eclipse; didn't add any web application to the server; started and stopped server from the eclipse without errors.
- added simple web application (just one index.html page) to the server; started and stopped server from the eclipse without errors. In both cases I saw the message:
Stopping WebLogic Server...
Server "AdminServer" was force shutdown successfully ...
- added my application; cannot stop server from the Eclipse or by running stopWebLogic.cmd script. Below is the error message I got when I ran script:
Stopping Weblogic Server...
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Connecting to t3://topics:7001 with userid weblogic ...
This Exception occurred at Thu Oct 04 08:58:09 EDT 2012.
javax.naming.AuthenticationException [Root exception is java.lang.SecurityException: User: weblogic, failed to be authenticated.]
Problem invoking WLST - Traceback (innermost last):
File "E:\oracle\Middleware\user_projects\domains\base_domain\shutdown.py", line 3, in ?
File "<iostream>", line 22, in connect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing connect : User: weblogic, failed to be authenticated.
Use dumpStack() to view the full stacktrace
Stopping Derby Server...
I believe that the problem might be related to the fact that our application starts several servlets and for some reason WLS cannot shutdown them.
I will continue to investigate the issue.