Configure Job Processor Use Limits for CAD Services for custom jobs

Configure Job Processor Use Limits for CAD Services for custom jobs

Majjek
Advocate Advocate
347 Views
7 Replies
Message 1 of 8

Configure Job Processor Use Limits for CAD Services for custom jobs

Majjek
Advocate
Advocate

Hello,

 

According to the topic below in help, you can configure how many jobs per type will be processed, before restarting the CAD services (Inventor Server for example).

 

But how can we configure this for custom Vault jobs?

I couldn't find a setting for this.

Or is there a command to restart the services from the custom job itself?

 

https://help.autodesk.com/view/VAULT/2025/ENU/?guid=GUID-41C135C2-C437-45D3-9134-FD94CBDD6781

 

0 Likes
Accepted solutions (1)
348 Views
7 Replies
Replies (7)
Message 2 of 8

Nick_Hall
Collaborator
Collaborator

Hi Majjek

I've not seen any mention of this functionality working for custom jobs, so I would handle the restart process myself.

Hope that helps

Nick

0 Likes
Message 3 of 8

Majjek
Advocate
Advocate

Hi Nick,

 

What would be the proper way to restart them?

0 Likes
Message 4 of 8

Nick_Hall
Collaborator
Collaborator

Hi Majjek

 

There is an example of connecting to the Vault Inventor Server component here.

 

https://forums.autodesk.com/t5/vault-customization-forum/vault-2018-2-custom-jobs-using-vaultinvento...

 

I've not tried it, but I would expect a Quit method for Inventor Server API,  as there is for the Inventor API.

 

If you count the number of times your job has run, you can restart Inventor Server however often you feel is necessary.

 

Hope that helps

Nick

 

0 Likes
Message 5 of 8

Majjek
Advocate
Advocate

Hi Nick,

 

Yes, I know that post and also read through the example.

I couldn't find any 'closing' routine in that example.

The InventorServer object doesn't have a Quit method or something similar I could find.

So I hoped anyone else could help with this.

0 Likes
Message 6 of 8

Nick_Hall
Collaborator
Collaborator
Accepted solution

Hi Majjek

 

I did say I hadn't tried it ...

 

But, as you can't close it tidily, I'd probably resort to the brute force method of killing the process, because life's too short (IMO). 

 

You can get the process using Process.GetProcessesByNamehttps://learn.microsoft.com/en-us/dotnet/api/system.diagnostics.process.getprocessesbyname?view=net-...

 

The process name is VaultInventorServer.exe

 

Then use Process.Kill to kill it - https://learn.microsoft.com/en-us/dotnet/api/system.diagnostics.process.kill?view=net-8.0

 

It's not subtle, but it is effective. 😁

 

Hope that's of some use

Nick

 

0 Likes
Message 7 of 8

Majjek
Advocate
Advocate

Hi Nick,

 

Ok thanks for your reply.

That would be the only way then probably.

Since the VaultInventorServer.exe process is already automatically closed after a job has finished, I didn't look into this.

Maybe the automatic closing still holds some references in the JobProcessor process, to be able to restart it much quicker.

And maybed force killing it, will prevent this.

 

I will mark it as solved for now.

0 Likes
Message 8 of 8

Nick_Hall
Collaborator
Collaborator

If I ever get through my huge pile of jobs, I'll have a look at using Inventor Server from a job handler.

 

But that is a BIG if

 

Nick

 

0 Likes