Steve

I have the MaxMSP Runtime 4.6 installed on a Windows XP dual processor machine. I'm trying to run a patcher that uses an mxj object. The mxj object fails in creation with a Java UnsatisfiedLinkError exception.

In the Runtime Max window I can see that Jitter 1.6.2 gets installed okay, and the MXJ CLASSPATH looks fine, too. The Java mxj object that's in trouble is stored in a JAR file, and the JAR file is listed in the CLASSPATH entries shown in the Max window. The mxj object references several other objects (not Jitter or Max objects) and these are all stored in the JAR file, as well.

The stack trace that prints in the Max window indicates that a JitterMatrix object is being instantiated when the error occurs. It's the first Jitter object in a series of such objects that should be instantiated.

The JAR file containing the mxj object runs fine on my separate development machine, which is running the MaxMSP/Jitter development system.

Here is a list from the Max window of the Runtime software. The Java stack trace info has been removed.

C:Program FilesCycling '74MaxMSP 4.6Cycling '74javalibHF001.jar

C:Program FilesCycling '74MaxMSP 4.6Cycling '74javalibjitter.jar

C:Program FilesCycling '74MaxMSP 4.6Cycling '74javalibjode-1.1.2-pre-embedded.jar

C:Program FilesCycling '74MaxMSP 4.6Cycling '74javalibmax.jar

C:Program FilesCycling '74MaxMSP 4.6Cycling '74javaclasses

I have the MaxMSP Runtime 4.6 installed on a Windows XP dual processor machine.  I'm trying to run a patcher that uses an mxj object.  The mxj object fails in creation with a Java UnsatisfiedLinkError exception.

The stack trace that prints in the Max window indicates that a JitterMatrix object is being instantiated when the error occurs.  It's the first Jitter object in a series of such objects that should be instantiated.

Here is a list from the Max window of the Runtime software.  The Java stack trace info has been removed.

Jitter 1.6.2 installed
MXJ System CLASSPATH:
   C:Program FilesCycling '74MaxMSP 4.6Cycling '74javalibHF001.jar
   C:Program FilesCycling '74MaxMSP 4.6Cycling '74javalibjitter.jar
   C:Program FilesCycling '74MaxMSP 4.6Cycling '74javalibjode-1.1.2-pre-embedded.jar
   C:Program FilesCycling '74MaxMSP 4.6Cycling '74javalibmax.jar
MXJClassloader CLASSPATH:
   C:Program FilesCycling '74MaxMSP 4.6Cycling '74javaclasses

java-unsatisfiedlinkerror-in-maxmsp-runtime

The problem appears to be timing-related when the MaxMSP Runtime first detects the Java mxj object in the patcher being loaded. (The patcher also uses Jitter objects.) It appears that the mxj object starts to be instantiated before the Java environment has been completely established. Consequently, the UnsatisfiedLinkError exception occurs.

After the error occurs, if I close the failed patcher, and reload it with no changes (leaving the MaxMSP Runtime executable running), no errors occur. The patcher loads and runs fine. All subsequent closes and loads work fine, as well.

The error does not occur in the demo and licensed versions because the Java environment is completely established before any patcher can be loaded and run.

I have only observed this behavior in the Windows version. I don't know how the Runtime software behaves in the Mac environment.

The problem appears to be timing-related when the MaxMSP Runtime first detects the Java mxj object in the patcher being loaded.  (The patcher also uses Jitter objects.)  It appears that the mxj object starts to be instantiated before the Java environment has been completely established.  Consequently, the UnsatisfiedLinkError exception occurs.

After the error occurs, if I close the failed patcher, and reload it with no changes (leaving the MaxMSP Runtime executable running), no errors occur.  The patcher loads and runs fine.  All subsequent closes and loads work fine, as well.

I have only observed this behavior in the Windows version.  I don't know how the Runtime software behaves in the Mac environment.


Java UnsatisfiedLinkError in MaxMSP runtime