Can no longer run matlabpool (possibly after today's Java update?)

1 view (last 30 days)
I get the following error message when I try to run "matlabpool open":
??? Error using ==> matlabpool at 125 The class distcomp.typechecker has no property or method named 'getDefaultValue'.
This morning, I updated Java to 1.6.0_39 (Update 12). Yesterday all was working smoothly.
MATLAB Version 7.12.0.635 (R2011a) Operating System: Mac OS X Version: 10.6.8 Build: 10K549 Java VM Version: Java 1.6.0_39-b04-442-10M4008 with Apple Inc. Java HotSpot™ 64-Bit Server VM mixed mode
Many thanks in advance!
  5 Comments
Andi
Andi on 8 Feb 2013
Will, thanks for your help! Nevertheless, the Java version they advise (in 2011) is 1.6.0_22, which is pretty old in view of how fast vulnerabilities are discovered and exploited. I have downloaded 1.6.0_37 (the one before _39) from Apple and I am thinking of installing that rather the older 0_22.
Corina
Corina on 1 Apr 2013
Edited: Corina on 1 Apr 2013
The link given by Walter worked for me! Thanks for sharing the link.
It did not required to do anything to Java.

Sign in to comment.

Answers (2)

Will
Will on 8 Feb 2013
  1 Comment
Andi
Andi on 8 Feb 2013
Will, apparently Mathworks is working on this. Here's a quote from a parallel post on the same topic:
"This issue was brought to the attention of MathWorks Technical Support earlier this week. This issue is reproducible and being investigated together with Development. In case you contact MathWorks Technical Support, you can refer to this thread and 'SR 1-LF8FNT'."

Sign in to comment.


Daniel Golden
Daniel Golden on 4 Mar 2013
Here's the official Mathworks bug report and a patch to solve the problem: http://www.mathworks.com/support/bugreports/919688
  2 Comments
Nicholas
Nicholas on 22 Mar 2013
It works perfectly, however it still does not work with compiled versions (MCR installation I mean, even applying that patch to the MCR folder)
any idea?
Thomas Ibbotson
Thomas Ibbotson on 22 Mar 2013
Hi Nicholas,
Can you paste the error you are getting when using the MCR here? Is it the same matlabpool problem, or a different issue? The patch was only meant to fix the problems in the PCT code. It's possible you've hit a different issue with the MCR and the new JVM versions.

Sign in to comment.

Products

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!