Verify the LiveView Client Listener is opening the configured port

Verify the LiveView Client Listener is opening the configured port

book

Article ID: KB0074119

calendar_today

Updated On:

Products Versions
TIBCO Streaming 10

Description

I am running a LiveView server, but I cannot connect to the client port.
How can I tell what client port LiveView is using?

Issue/Introduction

Troubleshooting guidance

Resolution

The following are different commands to use to identify the LiveView service port for a running LiveView server.

The default LiveView port is 10080, but this may be configured differently.

Confirm there is a ClientAPIListener (type = "com.tibco.ep.ldm.configuration.ldmclientapilistener") present in the src/main/configurations folder of the EventFlow fragment project or the Application project, for example:

client.conf
    name = "sample-ClientAPIListener-document"
    type = "com.tibco.ep.ldm.configuration.ldmclientapilistener"
    version = "1.0.0"
    configuration = {
        ClientAPIListener = {
            portNumber = 10080
        }
    }

Make sure there is only one. You may ignore the configurations found in folder src/test/configurations.

Console log shows the port:
(fragment deploy): 2020-07-30 09:58:57.086000-0400 [6990:JettyService] INFO  com.streambase.liveview.server.core.JettyService: LiveView Web service listening on non-SSL port 10080
(fragment deploy): 2020-07-30 09:58:28.805000-0400 [6990:JettyService] INFO  com.streambase.liveview.server.dtmmarket.DTMarket: We are configured to be on lv://c8system:10080/

The 'epadmin' command shows:
$ epadmin servicename=A.X display engine
[A.X] LiveView Fragment Client URI = lv://c8system:10080
...
and:
$ epadmin servicename=A.X display services servicetype=liveview
Service Name = A.X
Service Type = liveview
Network Address = sb://gbuhtz-p50:2925 lv://gbuhtz-p50:10080

Linux netstat shows (example):
$ sudo netstat -a -n -t -p | grep 10080
    tcp6       0      0 :::10080                :::*                    LISTEN      6990/application::l 
    tcp6       0      0 127.0.0.1:10080         127.0.0.1:55230         ESTABLISHED 6990/application::l 
    tcp6       0      0 127.0.0.1:55230         127.0.0.1:10080         ESTABLISHED 6990/application::l 
    tcp6       0      0 127.0.0.1:10080         127.0.0.1:55236         ESTABLISHED 6990/application::l 
    tcp6       0      0 127.0.0.1:10080         127.0.0.1:54766         ESTABLISHED 6990/application::l 
    tcp6       0      0 127.0.0.1:55236         127.0.0.1:10080         ESTABLISHED 6990/application::l 
    tcp6       0      0 127.0.0.1:54766         127.0.0.1:10080         ESTABLISHED 6990/application::l 
    tcp6       0      0 127.0.0.1:10080         127.0.0.1:55260         ESTABLISHED 6990/application::l 
    tcp6       0      0 127.0.0.1:55260         127.0.0.1:10080         ESTABLISHED 6990/application::l
 
To show what app PID 6990 is:
  $ ps ef | grep 6990

If you cannot find the configured port in these places, then see what these tools say about the actual port in-use and see if that port is a randomly selected port or is configured for use anywhere in the project. Search for the port number in the project using the StreamBase Studio menu: Search > Search...

To find the PID of the Streaming node, use:
  $ jps
and then search the 'netstat' output for ports associated with that PID.