Error while invoking JConsole Remotely as well as on the server .

[ptc-2878357]

Hi Gurus,

We are facing a challenge in invoking the JConsole Remortely as well as on the server.We have the system on 9.1_M050. Does anybody have an idea what happening wrong here?

JConsole Remotely:-

1) Set the following properties in site.xconf and propagate.

<property name="wt.manager.cmd.common.jmx.args" overridable="true"&lt;/p">

targetFile="wt.properties"

value="-Dcom.sun.management.jmxremote"/>

<property name="-Djmx.remote.protocol.provider.pkgs" overridable="true"&lt;/p">

targetFile="wt.properties"

value="wt.jmx.remote.protocol"/>

<property name="-Dcom.sun.management.jmxremote.authenticate" overridable="true"&lt;/p">

targetFile="wt.properties"

value="false"/>

<property name="-Dcom.sun.management.jmxremote.ssl" overridable="true"&lt;/p">

targetFile="wt.properties"

value="false"/>

<property name="-Dcom.sun.management.jmxremote.ssl.need.client.auth" overridable="true"&lt;/p">

targetFile="wt.properties"

value="false"/>

<property name="wt.manager.cmd.ServerManager.jmx.args" overridable="true"&lt;/p">

targetFile="wt.properties"

value="-Dwt.jmx.rmi.port=6049"/>

2) Invoke JConsole from Start--> Run --> JCosole

3) Add the hoste name : port , userID /Password and say connect.

The Result is “could not connect to the Server”.

Invoking the JConsole on the Server.

1) Open the windchill shell and type "windchill wt.util.jmx.SMJconsole"

2) It returns an error

<<

Exception in thread 'main' java.lang.NullPointException

at wt.util.jmx.SMJconsole.main(SMJconsole.java:38)

>>

Any pointers would be highly appreciated.

Thanks

Mayur

[jessh]

In scenario #2, one of 2 things is going on:

* You're not on a trusted host (i.e. one of the cluster nodes) or
* You have a misconfiguration causing the local JMX connector
startup to fail.
o In M050 this failure is unfortunately silent. In M060, this
will be properly logged.
o If this is occurring then the server status page is almost
certainly not working properly for you either.

As for scenario #1, your properties have issues. I believe the proper
way to do this is covered in the documentation, but a sample (insecure)
configuration would be:

<property name="wt.manager.cmd.common.jmx.args" overridable="true"&lt;br"/> targetFile="codebase/wt.properties"
value="-Dcom.sun.management.jmxremote -Djmx.remote.protocol.provider.pkgs=wt.jmx.remote.protocol -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.ssl.need.client.auth=false"/>
<property name="wt.manager.cmd.ServerManager.jmx.args" overridable="true"&lt;br"/> targetFile="codebase/wt.properties"
value="-Dwt.jmx.rmi.port=6049"/>

You'd want to change "-Dcom.sun.management.jmxremote.authenticate=false"
to "-Dcom.sun.management.jmxremote.authenticate=true" in anything but an
insecure developer/test environment, though.

--
Jess Holle

[ptc-2878357]

Thanks Jess ...
You are correct .... the properties were incorrect, after we modified we
could invoke the JConsole Remotely as well as on the server.

Thanks
Mayur