Automic Workload Automation

 View Only
  • 1.  Have I been drinking again!?

    Posted Nov 11, 2019 06:22 AM
    Edited by Carsten Schmitz Nov 11, 2019 06:22 AM
    ... because I am seeing double:


    Either the methanol was bad, or something is really rotten in the state of Denmark.

    In reality, of course there is only one process on 2250 (our PWP port), and that process is PID 2910. However, the server thinks the PWP is PID 2144, causing all manner of funky ill effects.

    PID 2144, in reality then, appears to be a regular worker that's presumably a zombie process.

    My colleague thinks he has seen this before and suspects that this started occasionally happening when the new syntax for server ports was introduced.

    Anyone else seen this?

    We've not yet filed a ticket yet because ... reasons.

    Thanks.


  • 2.  RE: Have I been drinking again!?
    Best Answer

    Posted Nov 12, 2019 07:46 AM
    Ahoi,

    so far in 3 12.3 ENVs I did not see this.
    We have 2 Servers for AE - and only for JCP we use the same port on both servers. 
    => Could it be the same port on 2 different servers (on screenshot it seems to be the same, right)
    => can it be an AWI refresh issue? I discovered some "funny" things caused by "stay tuned, AWI still refreshing"

    cheers, Wolfgang

    ------------------------------
    Support Info:
    if you are using one of the latest version of UC4 / AWA / One Automation please get in contact with Support to open a ticket.
    Otherwise update/upgrade your system and check if the problem still exists.
    ------------------------------