How to start WebLogic Server using default scripts?
Posted
by Luz Mestre-Oracle
on Oracle Blogs
See other posts from Oracle Blogs
or by Luz Mestre-Oracle
Published on Tue, 19 Aug 2014 22:49:07 +0000
Indexed on
2014/08/20
4:25 UTC
Read the original article
Hit count: 242
Filed under:
/Oracle
There are a few common issues reported when starting weblogic server using scripts.
1. User is not able to access weblogic console.
2. After a few days/hours weblogic server stops abruptly.
3. When user closes putty, they are not able to connect to weblogic server anymore.
4. When user closes windows command prompt, they are not able to connect to weblogic server anymore.
5. Weblogic is started using startManagedWebLogic.cmd/startManagedWebLogic.sh.
By default, WebLogic Server does not run in background mode, so after you close the window the process finishes as well.
In Linux/Unix based platforms, you need to use:
nohup ./startManagedWebLogic.sh <Server> <URL> &
In Windows platforms, you need to start Managed Servers using Windows Services:
How to Install MS Windows Services For FMW 11g WebLogic Domain Admin and Managed Servers (Doc ID 1060058.1)
http://docs.oracle.com/cd/E23943_01/web.1111/e13708/winservice.htm
There a few more reasons that could cause similar symptoms, like JVM crash, signals sent by the Operating System, and many other reasons.
But the above steps is the first one to start.
Enjoy!
© Oracle Blogs or respective owner
