When you install a new Boomi Atom, and the “Shared Web Server” is enabled on port 9090 (default), you sort of expect that the java atom process is immediately listening at that port.<\/p>\n
I was searching for a method to locally query the atom for its generic status, and this page<\/a>, says that a special Endpoint is always available<\/p>\n http:\/\/<host>:<port>\/_admin\/status<\/span><\/p>\n This Endpoint is not authenticated. However much I tried, I was not able to query that Endpoint.<\/p>\n It turned out, that no process (the atom) was listening on (default) port 9090.<\/p>\n shows that no process is listening on port 9090<\/p>\n Changing configuration and restarting the atom made not change.<\/p>\n Googling the issue did not reveal any relevant information.<\/p>\n Speculating, that it might be because no “Listening” processes were deployed, I made a quick “Web Service Listen” process, and deployed it to the atom, and immediately:<\/p>\n Even though Linux shows it as a “tcp6” port, it actually also listens<\/a> on the tcp4 interface<\/p>\n So, it could look like that the Boomi atom actually does not start the “Listening” process, before at least one Listening process has been deployed to that atom (here disregaring the built-in one)<\/p>\n","protected":false},"excerpt":{"rendered":" When you install a new Boomi Atom, and the “Shared Web Server” is enabled on port 9090 (default), you sort of expect that the java atom process is immediately listening at that port. I was searching for a method to locally query the atom for its generic status, and this page, says that a special … Continue reading “Boomi – Web Server Listening port not showing in netstat”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[39,8],"class_list":["post-824","post","type-post","status-publish","format-standard","hentry","category-guides","tag-boomi","tag-linux"],"_links":{"self":[{"href":"https:\/\/wp.bizoir.dk\/index.php?rest_route=\/wp\/v2\/posts\/824","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wp.bizoir.dk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wp.bizoir.dk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wp.bizoir.dk\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wp.bizoir.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=824"}],"version-history":[{"count":8,"href":"https:\/\/wp.bizoir.dk\/index.php?rest_route=\/wp\/v2\/posts\/824\/revisions"}],"predecessor-version":[{"id":843,"href":"https:\/\/wp.bizoir.dk\/index.php?rest_route=\/wp\/v2\/posts\/824\/revisions\/843"}],"wp:attachment":[{"href":"https:\/\/wp.bizoir.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=824"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wp.bizoir.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=824"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wp.bizoir.dk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=824"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n<\/p>\nThis status endpoint enables you to verify that an Atom's web server is active and ready to accept incoming web service requests. The endpoint returns an HTTP status code of 200 OK if the Atom is running and all known listeners have started. Failure to connect with the endpoint or a status code other than 200 means that the Atom is not ready to accept new requests. Knowing the status of an Atom's web server can also help you balance the workload between nodes in a Molecule or Atom Cloud more effectively.<\/pre>\n
sudo netstat -tapn<\/pre>\n
sudo netstat -tapn<\/pre>\n
tcp6 0 0 :::9090 :::* LISTEN 28438\/java<\/pre>\n