I am developing applications running on the Liberty Profile
(WebSphere Application Server 8.5.5.7/wlp-1.0.10.cl50720150827-0437) on Java HotSpot(TM) 64-Bit Server VM, version 1.7.0_71-b14 (en_GB)
I have had to increase the Server Startup Timeout value within eclipse to 300s.
Once I have completed my developmemt and want to deploy to a "stand alone" Liberty Server, e.g. Outside of Eclipse. How do I configure this Server Startup timeout?
We do have a new configuration option for how long the server will wait for the applications to start. If your application takes a few minutes to start the server will no go up until all your applications are ready.
You can read about this here:
http://www-01.ibm.com/support/docview.wss?uid=swg1PI51375
This configuration option can be used with:
http://www-01.ibm.com/support/docview.wss?uid=swg1PI49508
That last one will close any connection that comes while the server is starting.
You could use both this configuration options to hold up the server start based on your application start up time. For shutdown there is nothing I can recommend.
Other than that, as #Alasdair has answered we do not have any start or shutdown timeout in the Liberty Server.
Another thing you can do for delaying the startup is creating a shell script or similar to sleep for x amount of time before starting the application server.
Related
We have installed WAS Liberty Core 8.5.5 to run Maximo anywhere mobile applications.
If we start the server from CMD then we are able to access worklight console and maximo anywhere apps.
Command we are using to start the server.
server start server1
But once we closed the CMD window the server stops automatically.
Any workaround to run the server as a background Service ?
Also we need info on how to add WAS Liberty server to Windows startup service so that it will start automatically on system restart.
Thanks,
Ajay
You can run Liberty as a Windows service:
https://www.ibm.com/support/knowledgecenter/en/SSEQTP_liberty/com.ibm.websphere.wlp.doc/ae/twlp_setup_new_server_winserv.html
bin\server registerWinService serverName
bin\server startWinService serverName
bin\server stopWinService serverName
Of course "net stop/net start" or services.msc can be used instead of startWinService/stopWinService
The feature to setup a proper windows service is not available in Websphere Liberty 8.5.5.x.
You can use sc.exe to create a service linked to the server executable, but it won't behave correctly i.e. it won't respond correctly to the commands from the services application. As an example, you will be able to start the service and the server will run, but then you will see an error saying the service did not respond in a timely fashion.
According to this question the proper functionality, as described in the other answer, only became available around version 17.0.0.1.
Hope that helps,
John
I'm using windows 7, eclipse neon.3, liberty server 17.0.0.1, WebSphere® Application Server Liberty Tools 2016.0.0.v20170505_1729
I have a probem when starting the liberty server from eclipse. The server is actually starting fine, but eclipse is just showing the 'Starting'- status and never get confirmation that the server is actually started. After the predefined timeout, eclipse is giving up and stops the server.
If I start the server from command line, everythings works fine and eclipse confirmed that the server is running. Have tried both ibm sdk 8 and oracle.
What is actually the WDT (or eclipse) using for determing the server is started or not ?
WDT is looking for this message from the server: CWWKF0011I: The server is ready to run a smarter planet.
Please check the following link to make sure you have not changed something in the server configuration that is causing the tools to miss the message:
https://www.ibm.com/support/knowledgecenter/en/SSAW57_liberty/com.ibm.websphere.wlp.nd.multiplatform.doc/ae/r_limitations.html
Whenever I restart my websphere application server by default it starts all the applications deployed. How can I make only particular applications will get start in the start up?
Enterprise Applications > Your Application > Target specific application status
Enable Auto Start/Disable Auto Start
In our project we have installed both the “WebSphere application server” and “WebSphere Process Server” in a single machine. But we are unable to run both the server at a same time.
WebSphere Process Server is mounted on top of WebSphere Application Server, so while we are running the process server the default WebSphere application server instance is starting with the process server. So after that if we try to start the separately installed WebSphere application server, we are getting error that one instance is already running. Please suggest how to avoid this conflict and run both the process and application server in the single machine?
Both are using the same port. We already renamed the server name of the separately installed WebSphere application server with “server2” and Process Server’s application server name is “server1”
Please share your suggestions
You need to create separate profile. You don't have to install WAS first, or install it again, if you don't want. You may use Profile Management Tool from your installation to create new separate profile for WAS (choose Application Server profile type, not Process Server).
If you want complete separation e.g different versions (like vX of WPS and vY of WAS), or different fix pack level, you will need to do full separate WAS install.
Websphere Process Server extends Websphere Application Server (WAS), so you should install WAS first. Websphere Process Server (WPS) install should be made on top. When installation is complete you will be able to create WAS and WPS profiles on this machine. WPS profile always include WAS libraries and can be managed exactly the same way as WAS.
If you want separate servers, you should create two profiles, one for WAS and one for WPS.
You will be able to manage them separately.
So, I have downloaded a Spring Tool Suite and when i want to start VMware vFabric tc Server i get this message :
Server VMware vFabric tc Server Developer Edition v2.6 was unable to start within 120 seconds. If the server requires more time, try increasing the timeout in the server editor.
Could anyone tell me where can i change this parameter which will allow me to start the server?
In the Servers view in Eclipse, double click on the Server name, that will open up an editor, there's a Timeouts section, increase the value for Start.