The Math Forum

Search All of the Math Forum:

Views expressed in these public forums are not endorsed by NCTM or The Math Forum.

Math Forum » Discussions » Software » comp.soft-sys.matlab

Notice: We are no longer accepting new posts, but the forums will continue to be readable.

Topic: Matlab dedicated automation server issue
Replies: 0  

Advanced Search

Back to Topic List Back to Topic List  
Carl Banks

Posts: 7
Registered: 8/23/07
Matlab dedicated automation server issue
Posted: Mar 19, 2014 7:20 PM
  Click to see the message monospaced in plain text Plain Text   Click to reply to this topic Reply

Here is the documentation on starting a dedicated Matlab automaton server using Windows COM (emphasis is mine):

Starting a Dedicated Server

To specify a dedicated server, use the ProgID, matlab.application.single, (or the version-specific ProgID, matlab.application.single.N.M).

Each client that requests a connection to MATLAB using a dedicated ProgID creates a separate instance of MATLAB; IT ALSO REQUESTS THAT THE SERVER NOT BE SHARED WITH ANY OTHER CLIENT. Therefore, there can be several instances of a dedicated server running simultaneously, since the dedicated server is not shared by multiple clients.

However, in my own testing, I found out that the emphasized part isn't true at all. To wit, here is a Python session showing me starting a dedicated server that turns out to be not so dedicated:

>>> server1 = win32com.client.Dispatch('Matlab.Application.Single')
>>> server2 = win32com.client.Dispatch('Matlab.Application')
>>> server1.Execute('a = 1')
>>> print server2.Execute('a')

a =

So an instance was started as a dedicated server, but then attempting to create a non-dedicated server, it ends up connecting to the previously created dedicated server. The same behavior occurs if the two clients are started from different Python processes.

This a bug in Matlab; the documentation doesn't match the behavior. Besides the fact that this violates containment, it's also a potential security issue.

Is there a workaround for this; a way to prevent other clients from connecting even when started as a server? Version is 2013a if it matters.


Carl Banks

Point your RSS reader here for a feed of the latest messages in this topic.

[Privacy Policy] [Terms of Use]

© The Math Forum at NCTM 1994-2018. All Rights Reserved.