Clarity

Expand all | Collapse all

CA PPM port revisited

  • 1.  CA PPM port revisited

    Posted Oct 11, 2016 04:56 AM

    Going back to CA Clarity Login

    https://communities.ca.com/message/101075369?commentID=101075369#comment-101075369 

    15.1 documentation still says

    Having done two separate fresh installs of 15.1 I still get

    when using port 80.

    When I set the port in CSA to 8080 no problem getting the login page.

     

    I take

    ...And this is exactly source of a problem because TOMCAT 7 has got 8080 (not 80!) as a default port for Clarity application server!

    as stated in the referred thread still holds and is true for Tomcat 8, too.

    So why am I hitting this first in 15.1 and not in 14.x?

    Is there a setting somewhere that controls this?

    Is the documentation in error?

    How would a user know which port works without trial and error?



  • 2.  Re: CA PPM port revisited

    Broadcom Employee
    Posted Oct 11, 2016 05:30 AM

    Can you share the csa screen shot, I have the below configuration on port 80 and it works fine 

     



  • 3.  Re: CA PPM port revisited

    Posted Oct 11, 2016 06:21 AM

    This is what I have now and can access the login page

    If I set the port 80 I get the error.



  • 4.  Re: CA PPM port revisited

    Posted Oct 11, 2016 09:24 PM

    So this will happen if you have IIS running or IIS express.

     

    To test if IIS owns the port, try http://localhost

     

    V/r,

    Gene



  • 5.  Re: CA PPM port revisited

    Posted Oct 12, 2016 03:07 AM

    Thank you both for your answers. You make it sound that what I experience is not the way it is supposed to be.

    Based on Gene's test IIS is not running

    On the other hand would not IIS show up as World Wide Web service in the services?



  • 6.  Re: CA PPM port revisited

    Posted Oct 12, 2016 11:51 AM

    You might also want to check if iisexpress is running.

     



  • 7.  Re: CA PPM port revisited

    Posted Oct 12, 2016 05:27 AM

    Had this problem a while ago, something else was using port 80.

    run "netstat  -an" in command prompt and look if port 80 is listening.

    You could also check that the property file has actually stored the new port setting and restart the services

     

    Also since you are on the actual server it shouldn't matter, but check the firewall rules and ensure port 80 is open.

     

    Finally just to confirm, I was able to get 15.1 working on port 80



  • 8.  Re: CA PPM port revisited

    Posted Oct 12, 2016 07:12 AM

    Thanks  am1   So in my case there is something that caused this.

    This is the netstat -an

    Active Connections

     

      Proto  Local Address          Foreign Address        State
      TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
      TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
      TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
      TCP    0.0.0.0:1433           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:5985           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:8009           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:8080           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:8090           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:8109           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:9091           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:47001          0.0.0.0:0              LISTENING
      TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING
      TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING
      TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING
      TCP    0.0.0.0:49155          0.0.0.0:0              LISTENING
      TCP    0.0.0.0:49156          0.0.0.0:0              LISTENING
      TCP    0.0.0.0:49157          0.0.0.0:0              LISTENING
      TCP    0.0.0.0:49158          0.0.0.0:0              LISTENING
      TCP    127.0.0.1:1433         127.0.0.1:49723        ESTABLISHED
      TCP    127.0.0.1:1434         0.0.0.0:0              LISTENING
      TCP    127.0.0.1:23791        0.0.0.0:0              LISTENING
      TCP    127.0.0.1:23792        0.0.0.0:0              LISTENING
      TCP    127.0.0.1:31000        127.0.0.1:32000        ESTABLISHED
      TCP    127.0.0.1:31002        127.0.0.1:32002        ESTABLISHED
      TCP    127.0.0.1:31004        127.0.0.1:32001        ESTABLISHED
      TCP    127.0.0.1:32000        0.0.0.0:0              LISTENING
      TCP    127.0.0.1:32000        127.0.0.1:31000        ESTABLISHED
      TCP    127.0.0.1:32001        0.0.0.0:0              LISTENING
      TCP    127.0.0.1:32001        127.0.0.1:31004        ESTABLISHED
      TCP    127.0.0.1:32002        0.0.0.0:0              LISTENING
      TCP    127.0.0.1:32002        127.0.0.1:31002        ESTABLISHED
      TCP    127.0.0.1:49229        127.0.0.1:49230        ESTABLISHED
      TCP    127.0.0.1:49230        127.0.0.1:49229        ESTABLISHED
      TCP    127.0.0.1:49231        127.0.0.1:49232        ESTABLISHED
      TCP    127.0.0.1:49232        127.0.0.1:49231        ESTABLISHED
      TCP    127.0.0.1:49239        127.0.0.1:49240        ESTABLISHED
      TCP    127.0.0.1:49240        127.0.0.1:49239        ESTABLISHED
      TCP    127.0.0.1:49241        127.0.0.1:49242        ESTABLISHED
      TCP    127.0.0.1:49242        127.0.0.1:49241        ESTABLISHED
      TCP    127.0.0.1:49243        127.0.0.1:49244        ESTABLISHED
      TCP    127.0.0.1:49244        127.0.0.1:49243        ESTABLISHED
      TCP    127.0.0.1:49245        127.0.0.1:49246        ESTABLISHED
      TCP    127.0.0.1:49246        127.0.0.1:49245        ESTABLISHED
      TCP    127.0.0.1:49352        127.0.0.1:49353        ESTABLISHED
      TCP    127.0.0.1:49353        127.0.0.1:49352        ESTABLISHED
      TCP    127.0.0.1:49354        127.0.0.1:49355        ESTABLISHED
      TCP    127.0.0.1:49355        127.0.0.1:49354        ESTABLISHED
      TCP    127.0.0.1:49371        127.0.0.1:49372        ESTABLISHED
      TCP    127.0.0.1:49372        127.0.0.1:49371        ESTABLISHED
      TCP    127.0.0.1:49373        127.0.0.1:49374        ESTABLISHED
      TCP    127.0.0.1:49374        127.0.0.1:49373        ESTABLISHED
      TCP    127.0.0.1:49375        127.0.0.1:49376        ESTABLISHED
      TCP    127.0.0.1:49376        127.0.0.1:49375        ESTABLISHED
      TCP    127.0.0.1:49377        127.0.0.1:49378        ESTABLISHED
      TCP    127.0.0.1:49378        127.0.0.1:49377        ESTABLISHED
      TCP    127.0.0.1:49723        127.0.0.1:1433         ESTABLISHED
      TCP    127.0.0.1:49756        127.0.0.1:1433         TIME_WAIT
      TCP    127.0.0.1:49757        127.0.0.1:1433         TIME_WAIT
      TCP    169.254.32.159:139     0.0.0.0:0              LISTENING
      TCP    169.254.32.159:49158   169.254.32.159:49752   ESTABLISHED
      TCP    169.254.32.159:49158   169.254.32.159:49753   ESTABLISHED
      TCP    169.254.32.159:49233   0.0.0.0:0              LISTENING
      TCP    169.254.32.159:49233   169.254.32.159:49368   ESTABLISHED
      TCP    169.254.32.159:49341   0.0.0.0:0              LISTENING
      TCP    169.254.32.159:49341   169.254.32.159:49351   ESTABLISHED
      TCP    169.254.32.159:49351   169.254.32.159:49341   ESTABLISHED
      TCP    169.254.32.159:49363   0.0.0.0:0              LISTENING
      TCP    169.254.32.159:49366   0.0.0.0:0              LISTENING
      TCP    169.254.32.159:49366   169.254.32.159:49367   ESTABLISHED
      TCP    169.254.32.159:49367   169.254.32.159:49366   ESTABLISHED
      TCP    169.254.32.159:49368   169.254.32.159:49233   ESTABLISHED
      TCP    169.254.32.159:49752   169.254.32.159:49158   ESTABLISHED
      TCP    169.254.32.159:49753   169.254.32.159:49158   ESTABLISHED
      TCP    [::]:80                [::]:0                 LISTENING
      TCP    [::]:135               [::]:0                 LISTENING
      TCP    [::]:445               [::]:0                 LISTENING
      TCP    [::]:1433              [::]:0                 LISTENING
      TCP    [::]:5985              [::]:0                 LISTENING
      TCP    [::]:47001             [::]:0                 LISTENING
      TCP    [::]:49152             [::]:0                 LISTENING
      TCP    [::]:49153             [::]:0                 LISTENING
      TCP    [::]:49154             [::]:0                 LISTENING
      TCP    [::]:49155             [::]:0                 LISTENING
      TCP    [::]:49156             [::]:0                 LISTENING
      TCP    [::]:49157             [::]:0                 LISTENING
      TCP    [::1]:1434             [::]:0                 LISTENING
      UDP    0.0.0.0:123            *:*                    
      UDP    0.0.0.0:1434           *:*                    
      UDP    0.0.0.0:5355           *:*                    
      UDP    0.0.0.0:7500           *:*                    
      UDP    0.0.0.0:7500           *:*                    
      UDP    0.0.0.0:7500           *:*                    
      UDP    0.0.0.0:7500           *:*                    
      UDP    0.0.0.0:9090           *:*                    
      UDP    0.0.0.0:9090           *:*                    
      UDP    0.0.0.0:9090           *:*                    
      UDP    0.0.0.0:9090           *:*                    
      UDP    0.0.0.0:64581          *:*                    
      UDP    0.0.0.0:64582          *:*                    
      UDP    169.254.32.159:137     *:*                    
      UDP    169.254.32.159:138     *:*                    
      UDP    169.254.32.159:64200   *:*                    
      UDP    169.254.32.159:64579   *:*                    
      UDP    169.254.32.159:64583   *:*                    
      UDP    169.254.32.159:64584   *:*                    
      UDP    [::]:123               *:*                    
      UDP    [::]:1434              *:*                    
      UDP    [::]:5355              *:*                    

     

    but I do not know what to make out of it. Both 80 and 8080 are listet for 0.0.0.0 but not for the IP  or 127.0.0.0

     

    This is what the properties file has

    <webServerInstance id="app" entryUrl="http://localhost" sslEntryUrl="https://localhost:8043" port="8080" enablePort="true" sslPort="8043" enableSSLPort="false"

    So even the sslport is not 443 but 8043 and i have not touched that.



  • 9.  Re: CA PPM port revisited

    Posted Oct 12, 2016 09:14 AM

    Try netstat -ano to get the process id.

     

    Then look whats is running on in that id

     

    tasklist /svc

     

    V/r,

    Gene



  • 10.  Re: CA PPM port revisited

    Posted Oct 12, 2016 10:26 AM

    Thanks gcubed (and adequately detailed instructions.

    The only PID for port 80 is 4

    and for 8080 PID 3048, but that does not help

    Attachment(s)

    zip
    netstat_ano.txt.zip   1 KB 1 version
    zip
    tasklist.txt.zip   1 KB 1 version


  • 11.  Re: CA PPM port revisited

    Posted Oct 12, 2016 11:45 AM

    That is what I have on my system with IIS.

     

    Try iisreset /stop

     

    Then netstat -ano

     

    V/r,

    Gene



  • 12.  Re: CA PPM port revisited

    Posted Oct 12, 2016 02:12 PM

    D:\>iisreset /stop
    'iisreset' is not recognized as an internal or external command,
    operable program or batch file.

    D:\>



  • 13.  Re: CA PPM port revisited

    Posted Oct 12, 2016 10:51 AM

    That's a bit strange, but there will be a service behind this.

     

    try running the below in a elevated cmd window, should list out the services using port 80

    NET stop HTTP



  • 14.  Re: CA PPM port revisited

    Posted Oct 12, 2016 11:04 AM

    Thank

    s again Andrew

    I quess I could stop both of those and try to set the port to 80.

    What happens when i reboot the server?  Will those dependeds get another port or force their way to 80?



  • 15.  Re: CA PPM port revisited

    Posted Oct 12, 2016 11:42 AM

    You could try disabling those in device manager (if you don't care) or move http.sys over to ipv6 like in the below.

     

    netsh http add iplisten ipaddress=::

     

    After doing that stop/start http

    NET stop HTTP

    NET start HTTP

     

    Next check if it's still running on port 80.

     

    You should now be free to use it



  • 16.  Re: CA PPM port revisited

    Posted Oct 12, 2016 02:16 PM

    When I issued NET stop HTTP it was the print spooler and Windows Remote Windows Management system

    Stopped those in Services and tried again


    D:\>NET stop HTTP
    The HTTP Service service is stopping........
    The HTTP Service service could not be stopped.



  • 17.  Re: CA PPM port revisited

    Posted Oct 12, 2016 02:45 PM

    Not iisexpress either

    D:\>iisexpress /?
    'iisexpress' is not recognized as an internal or external command,
    operable program or batch file.

     



  • 18.  Re: CA PPM port revisited
    Best Answer

    Posted Oct 13, 2016 12:46 PM

    Was having a think about this last night

    By any chance is this a sandbox with sql express installed on the same server?

     

    If so the reporting service is probably using port 80 

     

    Go to the reporting services configuration manager and change the port under web service url, also change it under report manager (in advanced).  Then stop the sql reporting service for good!

     

    If that works you owe me a large bag of irtokarkki



  • 19.  Re: CA PPM port revisited

    Posted Oct 13, 2016 02:43 PM

    That certainly was it. Thanks.
    The first time I installed MS SQL 2014 I left out something. So the next time it was bells and whistles except (Sharepoint stuff)

    after some configuration and reboot

     

    Any favorite flavor? I bring some the next time I come to the UG meeting.



  • 20.  Re: CA PPM port revisited

    Posted Oct 13, 2016 05:57 PM

    salmiakki is always good