Hi Markus,
This could be due to the server monitored is not an OOTB supported server (OOTB means there are no servlet, struts, ejb. spring jms, ws interceptors hit in your app) . In such cases, you would need we have different approach to monitor such servers, find the steps below:
a) enable find-entry-points node level property to boolean value true (default false) from Servers -> Appserver -> <tier> -> click <node name with jvm stats showing up> -> Either select Actions -> Configure appserver Agent Or select Agents tab and click "Configure" button to see and update node properties popup from controller UI
b) find the find-entry-points property and update to true and save the changes
c) generate load on the Business transactions on the jvm node
d) Either send us the latest Business-transactions-<timestamp>.log under <agent_dir>/logs/<nodename>/ path Or select the class/name that is listed in latest Business-transactions-<timestamp>.log among the possible entry points listed for load generated from find entry points node property output.
e) Define pojo custom rule from Configure -> Instrumentation -> Transaction detection -> Navigate to "Custom match rules" section -> Click "+" icon and select pojo type and define class and method details that you want to monitor as BT and that making JDBC/HTTP exit calls.
Make sure you disable find entry points flag if you define custom pojo rules and leave as is if you send us the BT.log to assist you further.
Hope that information helps.
Regards,
Arun
