Information about No Profiling Data on the data screen showing detailed transaction information in X-View
There are three cases when data screen shows “No Profiling Data” massage in X-View.
1. When all points don’t include detailed profiling information. *
Jennifer Agent doesn’t send any detailed profiling information because of certain cause.
- If you didn’t build jennifer.lwst.XXX.jar through lwst.sh, you should click menu of Problem diagnosis-Utility-patch list and confirm the message ‘LWST did not enabled‘.
Then, execute lwst30.XXX.jar again and check the problem in settings through manual.
In this example, point in X-View means data successfully has transmitted through first port, 6901,
But detailed profiling information which appeared by dragging and clicking certain points, can be transmitted through third port, 6703. Make sure whether above setting was executed correctly.
In spite of opened 6901 and 6902 ports, detailed information monitoring would not be available when 6703 port is closed on fire wall between Jennifer Server and Jennifer Agent.
Note: Confirm the size of Jennifer Server’s file, JENNIFER_SERVER/data/xprof.isam. If it shows 0, this means Jennifer Server didn’t take any related information.
2. When only some part of point shows “No Profiling Data”*
Jennifer Server can be slowed when CPU usage increases or Jennifer Server executes GC at that time. The data can be disappeared because UDP is losable protocol on the technical point of view.
Therefore, detailed data and even point data might not be showed.
In this case, you would better to check CPU/MEM usage of Jennifer Server and confirm that N/W bandwidth is enough.
NOTE: Jennifer is developed after considering the limitation of UDP enough.
However, TCP can bring blocking risk and negative impacts on response time of application operating system.
It’s impossible that performance data gather all transaction data perfectly and the data is not so mission critical.
For example, Jennifer Server is used for monitoring overloading movement, analyzing root cause of problem, classifying application needed tuning and SQL query and overall analysis of performance data movement. The number of TX, 1,234,245 and 1,235,000 is not a big issue (Although it is important as total data, to collect such data is not the purpose of Jennifer). |
