
Anonymous
Not applicable
2016-03-25
11:47 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Services endpoint list page not reachable in ESB Runtime
Hello,
I started using ESB Runtime Server recently. Everything worked well since couple of days when http://localhost:8040/services/ stopped working. Port seems to be used from the server, but url is no more reachable:
localhost didn’t send any data.
ERR_EMPTY_RESPONSE
I don't think I've done anything specific that could cause this issue. I tried restart, running the server with/without sudo, giving permissions to server folders, etc. Any idea what could have caused it? Or if there's another way to get all wsdl and wadl urls?
Thanks,
Kostadin
I started using ESB Runtime Server recently. Everything worked well since couple of days when http://localhost:8040/services/ stopped working. Port seems to be used from the server, but url is no more reachable:
localhost didn’t send any data.
ERR_EMPTY_RESPONSE
I don't think I've done anything specific that could cause this issue. I tried restart, running the server with/without sudo, giving permissions to server folders, etc. Any idea what could have caused it? Or if there's another way to get all wsdl and wadl urls?
Thanks,
Kostadin
118 Views
1 Reply

Anonymous
Not applicable
2016-03-26
04:47 PM
Author
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
running the server with/without sudo is a dangerous attempt!
I suggest to define a user under which the server has to run (it should in general be never the root user!).
You have to clean the file system after such error prone attempts. Stop the server, chown all files to the user you actually want to use for this server and restart it again - but take care you have set the variable RUN_AS_USER correctly in the scripts!
Now check if you can reach the console of the server. There is a command line client (I guess it is calls trun) and here you can see all bundles running.
Please check also if there are no zombie processes claiming this port already. Sometimes the stop command does not work and if you start the server again, the port is already bound and the original process is not working correctly. So take care there is no runtime process anymore before you start it again.
I suggest to define a user under which the server has to run (it should in general be never the root user!).
You have to clean the file system after such error prone attempts. Stop the server, chown all files to the user you actually want to use for this server and restart it again - but take care you have set the variable RUN_AS_USER correctly in the scripts!
Now check if you can reach the console of the server. There is a command line client (I guess it is calls trun) and here you can see all bundles running.
Please check also if there are no zombie processes claiming this port already. Sometimes the stop command does not work and if you start the server again, the port is already bound and the original process is not working correctly. So take care there is no runtime process anymore before you start it again.
118 Views
