cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - If community subscription notifications are filling up your inbox you can set up a daily digest and get all your notifications in a single email. X

Eclipse debugging for custom utility

krthk86g
13-Aquamarine

Eclipse debugging for custom utility

Hello Everyone,

 

I have setup windchill eclipse configuration and set up values for the method server as shown below but when I attempt to debug configuration it says refused to connect can someone please help me out to overcome this. 

 

value="true"/>


<Property name="wt.manager.cmd.MethodServer.debug.args" overridable="true" targetFile="codebase/wt.properties" value="-Xnoagent -Xdebug -Xrunjdwp:transport=dt_socket,address=host name:8000,server=y,suspend=n"/>

 

Regards,

Karthik

3 REPLIES 3
shin1h
13-Aquamarine
(To:krthk86g)

Hi, 

 

Is there BackgroundMethodServer in your env?

I think removing BackgroundMethodServer is worth to try.

HelesicPetr
22-Sapphire I
(To:krthk86g)

Hello,

Be sure that the value is correct. 

there are some differences within JDK9+ 

 

for example JDK9 the value looks like "-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8005"

for 5-8JDK -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8005

 

Also if you configure debug mode for Method server and also Background server you have to use separate configuration with different port number.

<Property name="wt.manager.cmd.MethodServer.debug.args" overridable="true"
targetFile="codebase/wt.properties"
value="{15}"/>
<Property name="wt.manager.cmd.BackgroundMethodServer.param.15" overridable="true"
targetFile="codebase/wt.properties"
value="-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:9006"/>
<Property name="wt.manager.cmd.MethodServer.param.15" overridable="true"
targetFile="codebase/wt.properties"
value="-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:9005"/>

 

Regards 

PetrH

Also be sure that site.xconf changes are propagated to the wt.properties.

Many times I forgot to do so 😄

 

Next issue could be cases with Firewall and wrong port number which is not allowed.

 

PetrH

Announcements

Top Tags