JMP suddenly closes ,often but not always, when being run through the Interop.JMP module for C#

Question

Hello, We use JMP as the main statistical app in our company and up until a few months ago everythin was fine.

We used the Interop.JMP module to run jsl files (that were tested manually many times and work).

These jsl files produce 1 or more jmp tables that allow aour engineers to do their job, no charts or graphics is generated in the script.

We started noticing that JMP opens the table (using the script), then after about 10 seconds (the time frame is random) JMP closes suddenly on its own.

This was first exhibited on a single machine, then others joined the mix, today i think it happens on all machines but with different randomness.

We mostly use JMP 11 & 13 (most of us use 11).

This is really annoying and work needs to be done again (or special saves in between to prevent the loss of analysis data, after the basic tables were created).

Can you help ?

By the way, the code that is being run from C# is:

JMP.Application jmpApp;

jmpApp = new JMP.Application(scriptPath);

bool res = jmpApp.RunJSLFile(scriptPath);

where scriptPath is the path to the jsl script.

Thanks in advance,

Yossi.

briancorcoran · Answer

Yes, JMP.  It is easier to see in  a Visual Basic application, but if the JMP object is defined within something like a button handler then once the function completes, the OS can shut JMP down.

myButttonHandler

{

JMP.Application myJMP = new JMP Application();

myJMP.Visible = True;

.....

//Once the processing leaves this function, JMP will close down

}

yossi_tokash · Answer

Thanks for the quick answer, briancorcoran.

"once the variable holding the JMP object goes out of scope, reference counts go to 0 and the OS can close the application"

Which application? JMP ?

I've never ancountered such a behavior before...

Can you please elaborate on the subject ?

Regards,

Yossi.

briancorcoran · Answer

Please keep in mind that once the variable holding the JMP object goes out of scope, reference counts go to 0 and the OS can close the application.  One thing to check is to make sure jmpApp is global to the application, meaning that is defined outside of the procedure where you are using it.  Then, JMP will stay up as long as you don't issue a Quit command.

Brian Corcoran

JMP Development