Skip to main content
B
BrianToussaint19-Tanzanite
19-Tanzanite
December 27, 2019
Solved

Set the number of method servers to start

  • December 27, 2019
  • 3 replies
  • 4384 views

Hope someone sees this.  I'm in the middle of a production upgrade and because the production server is much larger than the test server, it decided it needed 7 method servers instead of one and so the upgrade manager is failing when it tries to start up Windchill since it has too many method servers.  What is the option to set the number of method servers starting using xconfmanager?

Best answer by BrianToussaint

so embarrassing, but I had a typo somewhere else in those properties.

3 replies

B
BrianToussaint19-TanzaniteAuthor
19-Tanzanite
December 27, 2019

It isn't the method server but the administrator "wcadmin" login.  Even though it worked before I started the upgrade, the password isn't working now and it worked during the tests that I ran.

B
BrianToussaint19-TanzaniteAuthorAnswer
19-Tanzanite
December 27, 2019

so embarrassing, but I had a typo somewhere else in those properties.

M
22-Sapphire I
MikeLockwood22-Sapphire I
22-Sapphire I
January 2, 2020

One good reason to always set these using WCA rather than changing the property directly.

B
BrianToussaint19-TanzaniteAuthor
19-Tanzanite
January 2, 2020

@MikeLockwood, I didn't actually change that property.  It was one of the properties in the Upgrade Manager that I typed wrong.  It was with one of the ou's.  The wca gave me 7 method servers and 1 background server.

M
22-Sapphire I
MikeLockwood22-Sapphire I
22-Sapphire I
January 2, 2020

Interesting...

I've done many dozens of upgrades / rehearsals and don't recall anywhere in the UI where the number of method servers is called out.

More to learn every day.

T
23-Emerald IV
TomU23-Emerald IV
23-Emerald IV
January 2, 2020

I know you found the root issue, but here are the properties to control the number of method servers:

  • xconfmanager -s "wt.manager.monitor.services=MethodServer" -t codebase/wt.properties -p
  • xconfmanager -s "wt.manager.monitor.start.MethodServer=1" -t codebase/wt.properties -p
  • xconfmanager -s wt.queue.executeQueues=true -t codebase/wt.properties -p

Some related KB articles:

Terms & ConditionsCookie settingsAccessibility statement