jmx query

2014-09-16 Thread vicky


 Hi,
Can someone please explain step by step instruction that how to setup the LDAP 
authentication for  JMX console ?


Thanks Guys

Vicky


Re: jmx query

2014-09-16 Thread André Warnier

vicky wrote:


 Hi,
Can someone please explain step by step instruction that how to setup the LDAP 
authentication for  JMX console ?



Pre-requisite : read http://www.catb.org/esr/faqs/smart-questions.html
then

Step 1 : open a browser
Step 2 : go to www.google.com
Step 3 : enter setup LDAP authentication for JMX console in the search box
Step 4 : press the search icon
Step 5 : read the articles listed there

Once you have tried one of the procedures listed there, if you still have a problem, come 
back here for a specific question.




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



JMX query to modify attribute value

2010-03-08 Thread Cummins College
Hello,

I have tried this JMX query to modify the connector properties of
connector.
http://localhost:8080/manager/jmxproxy/?set=Catalina:type=Connector,port=8443att=secureval=false

When I again check the status of the connector with this query,
 http://localhost:8080/manager/jmxproxy/?qry=*:type=Connector,port=8443
the secure attribute is changes to false, but there is no change in the
sever.xml file for the same connector.

So, should I assume that atleast for runtime the secure attribute is false
and https is disabled?


Thank you


Re: JMX query to modify attribute value

2010-03-08 Thread Pid

On 08/03/2010 10:04, Cummins College wrote:

Hello,

I have tried this JMX query to modify the connector properties of
connector.
http://localhost:8080/manager/jmxproxy/?set=Catalina:type=Connector,port=8443att=secureval=false

When I again check the status of the connector with this query,
  http://localhost:8080/manager/jmxproxy/?qry=*:type=Connector,port=8443
the secure attribute is changes to false, but there is no change in the
sever.xml file for the same connector.


Why would there be?  Dynamically changing Tomcat does not automatically 
cause the server.xml file to be updated?



So, should I assume that atleast for runtime the secure attribute is false
and https is disabled?


Umm, yes?  It depends on how YOU configured the server.xml in the first 
place.  You should assume that at least for runtime the attributes are 
what you configured them to be.



I'm wincing as I ask this, but why are you still trying to dynamically 
change this attribute?


The HTTPS connector also needs either a truststore or APR compatible SSL 
configuration setting AS WELL as setting other properties.  Simply 
setting 'secure=true' on a connector does NOT automatically make it an 
HTTPS connector.


Note: the connector is not a per-user object, it is used by all users at 
the same time, so changing it for one user changes it for all users.


Worse, as we've previously stated, the HTTP connector is now likely to 
be broken, so not only do you not have a working HTTPS connector, you 
now don't have a working HTTP connector.



p



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: JMX query to modify attribute value

2010-03-08 Thread Mark Thomas
On 08/03/2010 10:04, Cummins College wrote:
 Hello,
 
 I have tried this JMX query to modify the connector properties of
 connector.
 http://localhost:8080/manager/jmxproxy/?set=Catalina:type=Connector,port=8443att=secureval=false
 
 When I again check the status of the connector with this query,
  http://localhost:8080/manager/jmxproxy/?qry=*:type=Connector,port=8443
 the secure attribute is changes to false, but there is no change in the
 sever.xml file for the same connector.
 
 So, should I assume that atleast for runtime the secure attribute is false
 and https is disabled?

Altering attributes via JMX will never update server.xml

The results of changing attributes whilst a component is running will
vary from having no effect, to causing a crash to having the result you
want. You'll have to check the code for each attribute to see which
applies. Cleaning up the write aspect of JMX access has been on the todo
list for a while but hasn't happened yet.

Mark



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org