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.
SBX
YE
DR
DEV
- DEV.KFSÂ http://dev.kfs.uconn.edu:8080/probe
- DEV.KRÂ http://dev.kr.uconn.edu:8080/probe
- DEV.KRAPPSÂ http://dev.krapps.uconn.edu:8080/probe
TST
- TST.KRAPPSÂ https://tst.krapps.uconn.edu/probe
TRN
UAT
- UAT1.KFSÂ http://uat1.kfs.uconn.edu:8080/probe
- UAT2.KFSÂ http://uat2.kfs.uconn.edu:8080/probe
- UAT1.KRÂ http://uat1.kr.uconn.edu:8080/probe
- UAT2.KRÂ http://uat2.kr.uconn.edu:8080/probe
SUP
- SUP1.KFSÂ http://sup1.kfs.uconn.edu:8080/probe
- SUP2.KFSÂ http://sup2.kfs.uconn.edu:8080/probe
- SUP1.KRÂ http://sup1.kr.uconn.edu:8080/probe
- SUP2.KRÂ http://sup2.kr.uconn.edu:8080/probe
PRD
- PRD1.KFSÂ http://prd1.kfs.uconn.edu:8080/probe
- PRD2.KFSÂ http://prd2.kfs.uconn.edu:8080/probe
- PRD3.KFSÂ http://prd3.kfs.uconn.edu:8080/probe
- PRD4.KFSÂ http://prd4.kfs.uconn.edu:8080/probe
- PRD1.KRÂ http://prd1.kr.uconn.edu:8080/probe
- PRD2.KRÂ http://prd2.kr.uconn.edu:8080/probe
- PRD3.KRÂ http://prd3.kr.uconn.edu:8080/probe
- PRD4.KRÂ http://prd4.kr.uconn.edu:8080/probe
- PRD.KRAPPSÂ http://prd.krapps.uconn.edu:8080/probe
Â
Casifying probe
Â
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