#67 1.1.0rc1 fails to create/connect to local manager from ICF

open
nobody
None
5
2012-04-02
2012-04-02
Brian Colby
No

Running 1.1.0-rc1 on 64bit windows trying to control a remote dynamo process on a linux machine. I created a saved ICF, but when I try to launch iometer in batch mode from this config file the test run is aborted from a timeout because Iometer is unable to connect to the local manager.

The default behavior of the save configfile button is to leave the network address of the local manager blank, upon attempting to launch iometer from the saved config file, no dynamo process is launched, and the iometer instance aborts after 10 seconds for not being able to find a local dynamo.

If the network address of the local dynamo is filled out correctly (replicating the behavior of the 2006 release) a local dynamo process is launched, but never connected to.

Discussion

  • Vivek

    Vivek - 2013-04-02

    Encountered the same bug. Would like to know if there is a fix for this. Thanks in advance.

     
  • Brian Colby

    Brian Colby - 2013-04-02

    Not a fix, but we did come up with an effective work around. Since we are never actually interested in running a local Dynamo, what we did was remove DYNAMO.exe from the folder where we installed Iometer.

    Removing the EXE alone is not sufficient, as Iometer will simply complain about not being able to find it. To get around this, we created a file named DYNAMO.cmd which is a simple text file containing a single line:

    exit

    When Iometer is launched from the saved ICF file, it opens the dynamo process which immediately closes itself. Luckily Iometer is too dumb to check the extension, and since the ICF doesn't actually care if Dynamo is running locally everything works out fine.

    Cheers

     
  • Vivek

    Vivek - 2013-04-02

    Thank you Brian. It is definitely an effective work around. Its working fine for me.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks