Clovertech

5.5: Network Configurator bug/feature?

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › 5.5: Network Configurator bug/feature?

  • Creator
    Topic
  • June 19, 2007 at 8:46 am #49354
    Robert Kersemakers
    Participant

      Hi all,

      We are currently testing CL 5.5 Rev 1 (on HP-UX 11.23) and we have the following bug/feature: when applying a change to a thread in the Network Configurator, the view jumps back all the way to the top. I then need to scroll back to the threads I’m working on.

      This is very annoying when you need to change a lot of threads.

      Does anyone else have this problem or a solution for it?

      TIA,

       Robert

      Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

    • Creator
      Topic
    Viewing 2 reply threads
    • Author
      Replies
      • June 21, 2007 at 2:46 pm #61617
        Russ Ross
        Participant

          Some of what you are talking about reminded me of post

          https://usspvlclovertch2.infor.com/viewtopic.php?p=6856#6856” class=”bbcode_url”>https://usspvlclovertch2.infor.com/viewtopic.php?p=6856#6856

          Russ Ross
          RussRoss318@gmail.com

        • June 22, 2007 at 6:49 am #61618
          Robert Kersemakers
          Participant

            Hi Russ,

            Ah yes: the infamous ‘dragging a thread in the Network Monitor to it’s proper location and when releasing it, it jumps to the upperleft corner’. I’ve had this problem in 3.7 and 5.2, haven’t seen it in 5.5 (although I haven’t had to relocate a lot of threads in the Network Monitor, thanks to the synced views).

            So my bug/feature is something completely different. As no one else seems to have this problem, I’m guessing it relates to our OS (HP-UX 11.23 ia64).

            FYI: I previously had another problem: when scrolling through the Network Configurator (we have a very long, vertical configuration), the screen would ‘flicker’. When searching this forum, I found the JVM Arguments in the Advanced Tab of the Client Options. After inserting ‘-Xmx256m’ as the arguments, the flickering was gone. I wonder which other options I could try here…

            Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

          • June 22, 2007 at 12:37 pm #61619
            Michael Lacriola
            Participant

              Easy solution: Stop the monitor daemon, position your threads, then restart the daemon. BTW, we have 5.5 rev1 and the problem seems to be somewhat fixed. I still prefer stopping the daemon. I just operations to let them know not to freek out when the threads all say dead. Data is still moving.

          • Author
            Replies
          Viewing 2 reply threads
          • The forum ‘Cloverleaf’ is closed to new topics and replies.