Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About ccbc

  • Rank

FileMaker Experience

  • Skill Level
  • FM Application

Platform Environment

  • OS Platform
  • OS Version
    macOS 10.15.1 Catalina
  1. Hello Ryan Sorry for the delay in replying. I can reliably and consistently reproduce this problem. It is very simple. When the ScriptMaster 5.2/5.3 plug in is first enabled it attempts to start up and launches a java process which it then fails to connect to. When it is enabled a second and subsequent times it launches a new Java process as before but connects to the Java process launched previously. The plug in then operates correctly albeit with an additional unused Java process. So it appears to start up correctly if there is a Java process still running from a previous attempt to enable the plugin. To reliably reproduce the issue I quit any existing Java processes using activity monitor. The first attempt to enable the plug in will then fail. Subsequent attempts then succeed. Basically the scriptmaster plug in 5.2/5.3 is not managing the Java processes and connections correctly. The email plug in appears to work ok. Regards Chris PS Having said that the email plugin may be picking up Java process launched previously too! Chris
  2. FYI The same problem occurs with v5.3 although the error message is slightly different. Unable to start child process JVM However after two or three attempts to restart the plug in manually I can get it going.
  3. Hello Ryan I am wondering whether there has been any progress with resolving this issue after my screen share session with Joe Martin a few weeks ago. Thanks Chris
  4. Sorry. Should have mentioned that: macOS fully up to date. ScriptMaster latest freshly installed.
  5. "Unable to read from stdout on JVM startup after 3 seconds" This happens intermittently. Sometimes it starts up perfectly. Is there any way to increase the timeout? Thanks
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.