The attached J-link app has been used successfully for months, but now we have a perplexing problem.
Overview: We have a job queuing system (PBS Pro) that runs jobs on our Windchill server.
Each jobs simply runs Pro/E with a trail file to create a plot file of a drawing (per our internal requirements).
The J-Link app's start-class is set to do the following immediately when Pro/E starts:
- Authenticate the browser.
- Register the Windchill server.
- Define & create a workspace
- Add a drawing to the workspace.
The trail file does the rest, which is not important here.
We recently configured PBS Pro to use an additional server (for load balancing).
When a job runs on this new server, the J-Link app hangs at step 2 above.
It is not failing. The try/catch statements should address that. (Lines 112 - 119)
The last-know completed statement is line 108.
The apparent hanging problem is on line 113.
Now here's the perplexing part:
If an admin user happens to be logged unto the new/2nd server (through remote desktop connection) when the job starts, the job will run completely as expected, just as it would on the Windchill/1st server.
Note: The admin user is not launching the job.
The job is actually initiated on the Windchill server by PBS Pro, which sends a message to the PBS Pro service on the new/2nd server, which in turn launches the job (batch file) which includes the Pro/E batch session.
Any ideas before I contact PTC?
Gerry
