Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Differentiating license issues with connection issues

Open
#22 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
tooling

Research direction

Start at RemoteMatlabProxyFactory.java:176 and trace how proxy-creation timeouts surface through the matconsolectl source. Reproduce the license-exhaustion case if possible, compare it with a network failure, and identify whether the MATLAB license-manager message is available; done means the two failure types are distinguishable or the limitation is documented.

Written by the indexing model from the issue text.

Description

enhancement

We're running matconsolectl in a server job and using a corporate license pool.
Sporadically, we're getting this exception:

Exception in thread "main" matlabcontrol.MatlabConnectionException: MATLAB proxy could not be created in 180000 milliseconds
at matlabcontrol.RemoteMatlabProxyFactory.getProxy(RemoteMatlabProxyFactory.java:176)

I suspect that this is caused by being out of matlab licenses, but as far as I can tell from the matconsolectl source code, it does not have any special handling of license issues compared to e.g. network issues. Or am I misdiagnosing this and license errors will not get MatlabConnectionException timeouts?

It would be really nice if one could get the error message we get when running matlab directly, i.e.

"License checkout failed.
License Manager Error -4
Maximum number of users for MATLAB reached.
Try again later."

I'm not sure where to start looking for the above output though, so not sure how to fix it (if this really is the issue that I think it is)

Dominant language
Java
Stars
50
Forks
16
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.