how can we increase the timeout value for method server in windchill?

[vmg]

As my system is very slow the method server takes 900 secs to start?

there is no possiblities that our organization will increase the processor

speed and ram size for me. as method server takes more time to start

i get 2 - 3 instances of method server. i searched in community that

if timeout is increased we wont get 2 - 3 instances of method server.

where to change the properties.

"wt.manager.serverStartTimeout=180"

is the one i should change?

can i directly change in wt.properties.

or should i run xconf manager?

if yes how to run the xconf manager ?

is there any tutorial for the same ?

[MatthewKnight]

As the comment in wt.properties says, "YOU SHOULD NEVER EDIT THIS FILE DIRECTLY!"

Add or set the property in <wchome>/site.xconf.

Open Windchill Shell.

Run "xconfmanager -p"

[vmg]

hi mattew,

i could not find timout property in

c:/ptc/windchill_9.1/windchill/site.xconf

where should i edit the timeout and run "xconfmanager -p"

thank you

VJN

[MatthewKnight]

I think Patrick's responses have you covered. But your entry in site.xconf would look like this:

<Property name="wt.manager.serverStartTime" overridable="true" targetFile="codebase/wt.properties" value="900"/>

You can set or create any property value you want in site.xconf.

I'm curious though. How much ram does your machine have? Do you have all the log4j debugging turned on?

[vmg]

Hi Matthew,

Thanks for reply.

i solved the problem, my machine has only 2 GB of ram.

As the Windchill_9.1 is freshly installed in my system.

I think all the log4j debugging is turned on.

How to turn off ?

If i turn off, whether the errors will be written in log file or not?

As i am a developer, i am creating some new java file in eclipse IDE for doing

some customization. For the new program to take effect in Windchill.

i am compiling the java file, and i restart the windchill. This the area i feel much

depressed that it takes too much time for restarting the Windchill.

Thank you

VJN

[MatthewKnight]

Going from memory, the log4j properties files are under codebase/web-inf. One of them will have "methodServer" in the name. There may also be a "serverManager" property file.

Make sure that you don't have many packages set to =DEBUG. Definitely make sure you don't have wt=DEBUG or com.ptc=DEBUG.

Errors will still be written to the log files. I'm really guessing here, though. I don't know how your properties are configured.

[PatrickMcEvoy]

Run this command from a windchill shell:

xconfmanager -t codebase/wt.properties -s wt.manager.serverStartTime=900 -p

That means

1. run the xconfmanager

2. the target file is "codebase/wt.properties"

3. you want to set the property "wt.manager.serverStartTimeout" to value "900"

4. you want to propagate the changes from the xconf files to the properties files

Note that this value gets set into WT_HOME/site.xconf and then pushed to wt.properties.

[vmg]

Hi Patrick,

thank you for the detailed procedure.

but for the problem.

To avoid the creation of 2 - 3 instances of method server.

we should edit "wt.manager.serverStartTimeout"

so that server manager will wait for that much time and wont create another instance.

I am not clear, is it right.

THANK YOU

VJN

[PatrickMcEvoy · Accepted solution]

Why is it starting the 2nd and 3rd MS instance? If it is because the 1st has not finished starting, then it seems likely that this will solve the problem.

It is easy to try this solution to see if it works and easy to revert if it does not work.

[PatrickMcEvoy]

Also you can run "xconfmanager -h" to have it print the help information.