If you are asking about a problem you are experiencing, please use the following template, as it will help us help you. If you have a different problem, please delete all of this text 
Kibana version: 8.5.1
Elasticsearch version: 8.5.1
APM Server version: 8.5.1
APM Agent language and version: Java 1.36.0
WildFly version (formerly known as JBoss): 20.0.0
Original install method (e.g. download page, yum, deb, from source, etc.) and version: from source
Fresh install or upgraded from other version? Fresh install
Is there anything special in your setup? For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc.
Agent Configuration File -:
transaction_max_spans=10000
environment=production
service_name=xyz
span_stack_trace_min_duration=0ms
stack_trace_limit=-1
recording=true
instrument=true
server_url=apmServerIP
span_frames_min_duration_ms=-1
application_packages=com.xyz
trace_methods=com.xyz.services.*
classes_excluded_from_instrumentation=org.json.*,com.blogspot.*,net.bytebuddy.*,com.fasterxml.jackson.*,io.jsonwebtoken.*,org.jsoup.*,org.springframework.*,org.jboss.*
Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
We are having a microservices architecture and using JBoss as application server where we have attached the java agent via standalone.bat for monitoring and capturing traces for our application.
When we are performing transactions on application UI, only scheduled type transaction are getting captured by the agent and same are displayed on Kibana, no request type transactions are captured by the java agent instead transaction -> 2#run is getting captured every time, refer below screenshot.
service.framework.name: TimerTask
service.language.name: Java
service.language.version: 11.0.22
transaction.name: 2#run
transaction.name.text: 2#run
transaction.sampled: true
transaction.span_count.dropped: 0
transaction.span_count.started: 0
transaction.type: scheduled
Sometimes restarting the application server works and we get traces for http requests but most of the time its 2#run.