Worklight server hangs for local desktop development

0
votes

I am working with worklight on Eclipse on a windows machine. I can never get it to stop or restart properly. Normally I have to spend 5 minutes trying to delete the server and add back the worklight projects and then it may startup again. Has anyone experienced this and what is a fix?

When I start Worklight server (local machine), the server just hangs, the bottom right message displays "Starting Worklight Developer Server".

I am using: Launching worklight (WebSphere Application Server 8.5.5.0/wlp-1.0.3.20130524-0951) on Java HotSpot(TM) 64-Bit Server VM, version 1.6.0_30-b12 (en_US), Worklight Studio / 6.1.0.01 - 2014

Version: Kepler Service Release 2 Build id: 20140224-0627

Code Base: nothing really, just a simple HelloWorld Adapter and javascript client code.

There are no error messages, this is the last message in the console. CWWKZ0001I: Application _MobileBrowserSimulator started in 0.498 seconds.

When visiting the server in the browser, there is no response because it looks like the server is still trying to start.

I usually wait 5 minutes before killing the server in the task manager. Even after killing the server in the task manager and then closing Eclipse and trying to start the server again...the server still hangs. Normally, I end up deleting the server and creating another one.

Note: I see a potential issue with the mobile simulator application, but when I remove the mobile simulator, worklight seems to inject it back into the server.

Edit-1: Nothing has really worked. I am now using Kepler SR1 and new workspace. It is possible that the server hanging issue has died down but it still happens. Basically, the only way to kickstart the worklight server is to change the server.xml, delete all the wars/applications (all 2 of them) and then kill the server in the task manager, possibly restarting eclipse and then starting the server again. There are no errors in the message log.

2
javajavascriptibm-mobilefirstworklight-studio
instead of killing server did you try creating new workspace and restart the eclipse? – Bluewings
I did create a new workspace, same issues. Initially the server may work properly. But over time, I get the hanging issue. – Berlin Brown

2 Answers

1
votes

It's hard to say what might be wrong with just that information. Can you provide your messages.log file when the server has failed? (It should be under workspace_path/WorklightServerConfig/servers/worklight/logs)

The best way to get the real one we want, would be to use a fresh Eclipse workspace and then reproduce the problem.

Just blinded eyes, as a potential solution, I would try to set a valid IP to the Worklight Development Server, instead using "localhost" which is the default. Have you tried that? In Servers View, double click Worklight Development Server -> Host Name -> SET TO YOUR CURRENT IP. Then do a Run As -> Run on Worklight Development Server again for your application.

0
votes

Kepler SR2 isn't supported for Worklight 6.1x. I don't know if this is the cause, but there was some unpredictable behavior with SR2. I would suggest trying it on Kepler SR1 and see if you get the same behavior. Get links to supported eclipse releases and editions here: https://www.ibm.com/developerworks/mobile/worklight/download/