Probe

Description

See official documentation here: http://code.google.com/p/psi-probe

Using Probe

Probe is most useful for checking long running requests. Since javamelody only shows you stats on requests that finish, probe can fill in the blank if you have a never ending request.

to check long running requests in probe.

Go to a probe url,

click on the 'Connectors' tab at the top right

their should be two tables headed by graphs,

one for port 8080 (tomcat HTTP connector, used for Kuali Service Bus communication between nodes),

and another for port 8009 (tomcat AJP connector that the load balancer directs traffic to.

If you see a long running request, you can check where in the code it is stuck by putting your mouse cursor over the thread name, and it will show the code trace.
If you see 'socket connect' or something similar in the trace, that means the thread is stuck waiting or communicating between Tomcat and Apache.
If you see 'oracle' in the trace, it's a good bet that there is a really long running query to the database that is suspect.
The code trace should be reviewed by a developer if this is a standard user procedure that is taking an unacceptably long time to complete.

If you experience errors reaching Probe on a particular environment, ensure in the URL path of your browser it isn't re-directing to the wrong server. If that is the case, check the value of parameter

serverName in the file probe.xml in /etc/tomcat6/Catalina/localhost on the target node.

Probe URLs

Environments where probe is casified should allow you in with a valid cas ticket (netid/password). If you receive a 401 error message, this is because you are not in the list of users who can access probe for that host.

Casifying probe

Configuring Probe with CAS

http://linux.uits.uconn.edu/dfm04001/

cas-client-core-3.2.1.jar cas-client-integration-tomcat-common-3.2.1.jar cas-client-integration-tomcat-v6-3.2.1.jar commons-codec-1.4.jar commons-logging-1.1.jar opensaml-1.1.jar xmlsec-1.3.0.jar

<?xml version="1.0" encoding="UTF-8"?>
<Context path="/probe" privileged="true" >
  <!--
    The following configuration uses the CAS 2.0 protocol and a static
    properties file to define allowed users to the Tomcat manager application.
    The content of manager-users.properties contains entries like the following:
      admin=manager-gui,manager-script,manager-jmx,manager-status
      operator=manager-status
      deployer=manager-script
    Where admin, operator, and deployer are valid logins for the CAS server.
    The path to the properties file is relative to $CATALINA_HOME.
    This example also configures the container for CAS single sign-out.
  -->
  <Realm
    className="org.jasig.cas.client.tomcat.v6.PropertiesCasRealm"
    propertiesFilePath="/srv/uconn_configs/probe/users-roles.properties"
    />
<Valve
 className="org.jasig.cas.client.tomcat.v6.Saml11Authenticator"
 encoding="UTF-8"
 casServerLoginUrl="https://login.uconn.edu/cas/login"
 casServerUrlPrefix="https://login.uconn.edu/cas/"
 serverName="dev.kfs.uconn.edu"
 />
<!-- Single sign-out support -->
<Valve
 className="org.jasig.cas.client.tomcat.v6.SingleSignOutValve"
 artifactParameterName="SAMLart"
 />
 </Context>

currently in /home/tomcat/tmp/probe_cas on jenkins

Access List for probe

/srv/uconn_configs/probe/users-roles.properties

####################################################################
#
# PSI Probe requires four security roles
# (in order of increasing privileges):
#
#               probeuser
#               poweruser
#               poweruserplus
#               manager - This is the same role required by
#                       Tomcat Manager and has the highest
#                       level of privileges.
#
####################################################################
#########################
# uconn cm & sa
#########################
jag04008=manager
gms02004=manager
bld98001=manager
#########################
# uconn rice and workflow
#########################
shw07005=manager
yih07002=manager
dac04010=manager
mio02003=manager
#########################
# uconn kfs
#########################
btp98001=manager
dar12006=manager
rad04002=manager
rgw02001=manager
ror11004=manager
ppk11002=manager
kaa02003=manager
#########################
# rsmart
#########################
als12010=manager
anp11006=manager
jad12008=manager
jur11001=manger
gec12002=manager
lep12004=manager
mel12007=manager
shf12004=manager