There are lots of new weblogic application status introduced Weblogic 9.x onwards.
Weblogic application states are purely dependent on the different circumstances like -
State of server, If your server is running or not on which you are deploying application ?
What is the size of your application you are going to deploy ?
May be there some technical configuration issues with your application you are going to deploy
Purpose of your deployment like you want to up it only for administration for some testing
Very first thing is, if your domain is in Development mode or Production mode. If it's on development mode then you not need to worry about lots of status since during deployment in development mode your application directly come in Active mode ( if there is no configuration issues with the file you are going to deploy ) however in production not.
Weblogic change center enabled only in production mode.
You can ask an application -
To start servicing all requests
To start servicing only administrator request
OR you can say
After that you can choose the option to make it "active" ( select application > Start > Servicing all requests)
If the server on which you are going to deploy the application or checking status of deployed application is running then -
Once you will deploy an application, it will come to "deploy initializing" state
Once you will activate the changes, it will come to "Prepared" state
Once you will start it with option "start servicing request", it will come to "Active" state
Weblogic server application status "stop running" & "start Running"
Apart from above sometimes you will see start Running and stop Running status during starting or stopping an application, it's generally appear in case you have a big application which took time to initialize the requested operation.
start Running generally you will see once you will start a big application ( aroung 1 gb or more in size ), later it will come in active state ( if there is no issues with the application )
stop Running generally you will see once you will try to stop/shutdown the application ( either gracefully or forcefully ) depend on the size of your application, current connections etc it takes time to stop and later will come to prepared state.
Weblogic application states are purely dependent on the different circumstances like -
State of server, If your server is running or not on which you are deploying application ?
What is the size of your application you are going to deploy ?
May be there some technical configuration issues with your application you are going to deploy
Purpose of your deployment like you want to up it only for administration for some testing
Very first thing is, if your domain is in Development mode or Production mode. If it's on development mode then you not need to worry about lots of status since during deployment in development mode your application directly come in Active mode ( if there is no configuration issues with the file you are going to deploy ) however in production not.
Weblogic change center enabled only in production mode.
You have some options to control the application with respective to Start or Stop.
Stop weblogic application options
You can -
Request an application to stop when work completes
Force stop application
Request to stop client connections however to take requests of administrator
OR you define
- When work completes: Specifies that WebLogic Server wait for the application to finish its work and for all currently connected users to disconnect.
- Force stop now: Specifies that WebLogic Server stop the application immediately, regardless of the work that is being performed and the users that are connected.
- Stop, but continue servicing administrative requests: Specifies that WebLogic Server stop the application once all its work has finished, but to then put the application in Administration Mode so it can be accessed for administrative purposes.
Start weblogic application options
You can ask an application -
To start servicing all requests
To start servicing only administrator request
OR you can say
- Servicing all requests: Specifies that WebLogic Server make the application immediately available to all clients.
- Servicing only administrative requests: Specifies that WebLogic Server make the application available in Administration Mode only.
In production mode -
If the server on which you are going to deploy the application or checking status of deployed application is not running then -
1. You will see the status as "New" for the application already deployed there.
2. If you will deploy a new application then -
It will come to "distribute Initializing" status
Once you will click on Activate Changes, it will changed to "New" status
Once server started, it will come to "Prepared" stateAfter that you can choose the option to make it "active" ( select application > Start > Servicing all requests)
If the server on which you are going to deploy the application or checking status of deployed application is running then -
Once you will deploy an application, it will come to "deploy initializing" state
Once you will activate the changes, it will come to "Prepared" state
Once you will start it with option "start servicing request", it will come to "Active" state
Weblogic server application status "stop running" & "start Running"
Apart from above sometimes you will see start Running and stop Running status during starting or stopping an application, it's generally appear in case you have a big application which took time to initialize the requested operation.
start Running generally you will see once you will start a big application ( aroung 1 gb or more in size ), later it will come in active state ( if there is no issues with the application )
stop Running generally you will see once you will try to stop/shutdown the application ( either gracefully or forcefully ) depend on the size of your application, current connections etc it takes time to stop and later will come to prepared state.
What does Application running in Adminstrator mode means
ReplyDeleteHI Mukesh ,
ReplyDeletethere is a situation where am seeing application are showing in monitoring tab but not in control , what could be the cause ?