AppD Archive

No load detected for Java App Server Agent

CommunityUser
Splunk Employee
Splunk Employee

Hello,

I am trying out AppDynamics. I am running a few Java based app servers in separate JVM's on the same host. The host also has a postgresql database. 

I have installed the App Server Agent in three of our app servers. All three app servers are configured in AppDynamics under a single Business Application. All three servers are configured as separate nodes under separate tiers. Two of the three servers are showing transactions in the dashboard. But the third server shows absolutely zero transactions. 

Reading through this forum I found some thread in which it was mentioned to "" enable node level property "find-entry-points" flag"" I have done so to help in diagnosing the problem. After enabling the flag I started getting data in the BusinessTransactions.<timeStamp>.log. I have attached all the log files pertaining to this node here. Could you please help me solve this problem of no transactions showing in dashboard?

0 Karma

Arun_Dasetty
Super Champion

Hi,

Apologies for delay in response we have access to your saas trial UI and we see couple of BTs got discovered for customESB rule you defined and WS BT. We see from logs the following are possible entry points listed:

=============================
Thread pool-10-thread-1
[pool-10-thread-1] 02 Oct 2014 17:02:35,588 INFO - 0. POJO com.sun.proxy.$Proxy15 commit

=============================

- Can you please let us know if the following classes are part of webapp customer api:
=============================

org.wso2.carbon.mediation.registry.WSO2Registry.lookup(WSO2Registry.java:131)
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:116)

found above apis as part of thread stack trace from below thread:
[PassThroughMessageProcessor-343] 02 Oct 2014 17:04:56,299 INFO - Logging request stack for Thread PassThroughMessageProcessor-343 >>

=============================

If the above said is correct, can you please define custom pojo rule under Configure -> transaction detection screen -> under section "Custom match rules" as referred in doc section defineof type POJO rules :

=============================

Rule1:
Class: com.sun.proxy.$Proxy15
Method: commit

Rule2:
Class: org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask
Method: run

=============================

Also we see find-entry-points is still set to true on this node, please make sure you disable once you define custom rule on target api that you want to see as BT, above said is evident from below listed screenshot:

image.png

Let us know if that information helps.

Regards.

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee
Hi,
Thanks for the reply and the information. Although the classes you
suggested did not detect any business transactions, I did manage to get all
outgoing transactions with the pojo classes that extend
org.apache.synapse.mediators.AbstractMediator. But this detects only
outgoing transactions from the node. I have failed to get incoming
transactions inspite of trying various ways such as different servlet /
pojo entry points ( e.g.
org.apache.synapse.transport.passthru.PassThroughHttpListener pojo), trying
to configure on URI part of incoming path (/services/ uri) or trying to
configure port (port 8282) on which the app server listens etc. If it helps
you in guessing, this app server is a WSO2 ESB server (version 4.7.0). Its
based on Apache Synapse and Axis2 with tomcat as the container. Could you
please guide me as to how I can get incoming transactions recognized?

0 Karma

Arun_Dasetty
Super Champion

Hi,

We understood that you want to monitor the incoming requests on agent nodes under ESB2 tier as BTs under ESB2 tier, let us know if any disconnect here.

If the above said is correct, Can you help us try the following details to debug further:

- Regarding the existing rules, is the user making request in browser to webapps deployed on node under ESB2 tier port 8282 we see the reason for rule on port not working is due to connector port is 9443 and 9763 and not 8282 as referred in screenshot below

image.png

- Can you provide the API details or package details that is serving the incoming requests at server associated under ESB2 tier/node ?

We request you to provide the agent logs from esb2 tier agent node to see whether the class referring is actually interceptors or not from logs.

Let us know if that information helps.

Regards,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi,
Thanks for the quick reply.

1) Ports 9443 and 9763 are the web admin ports. Actual clients connect to
services running on this node on port 8282 using url such as
http://xyz.com:8282/services/JmsStore2.0 The clients pass
http headers and JSON payload as POST params. So in this example
JmsStore2.0 should be the incoming entry point detected.

2) Abount the API details I am not very sure but it could be
https://github.com/wso2/platform/blob/master/dependencies/synapse/2.1.1-wso2v8/modules/transports/co...
or
https://synapse.apache.org/apidocs/org/apache/synapse/core/axis2/SynapseMessageReceiver.html

or

https://github.com/wso2/platform/blob/master/dependencies/synapse/2.1.1-wso2v8/modules/transports/co...

Please find the logs attached.

Also one more thing. I have sent a query for a quote of AppDynamics Pro
through the Contact us form as well as couple of emails to Sandy Mappic <
smappic@appdynamics.com> but haven't received any reply. Could you please
get someone in sales to provide us with pricing info?

Appreciate your help. Hope you can help me get this working using the info
provided above.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

I have got it to recognise ESB business transactions with pojo class org.apache.synapse.core.axis2.ProxyServiceMessageReceiver method receive and transaction splitting configured on parameter index 0 and getter chain getTo().getAddress() This gives me business transaction names like ProxyServiceMessageReceiver./services/TPunchInsertion 

However I am unable to get it to show me incoming calls. Is it because this is the edge tier? The calls coming in are from outside?

How can I now get a complete end to end view of a particular business transaction across tiers? The above transaction for example (ProxyServiceMessageReceiver./services/TPunchInsertion) hits the ESB tier which gets authenticated and authorized at the identity tier then gets passed on to dss tier where the payload gets stored to the database and a response is sent back from dss tier to esb tier and then back to the client. I would like to get end to end metrices of this entire transaction. Is it possible?

0 Karma

Arun_Dasetty
Super Champion

Hi,

If i am not wrong ootb support for correlation on ESB tiers is not supported and might need to use custom correlation , but we see this is not the case for all ESB types we see if you are using Mule ESB you should see correaltion if orignating call is part of tier with agent node configured and associated at same application in UI

https://docs.appdynamics.com/display/PRO39/Mule+ESB+Support

We see Webservice calls are correlated between ESB2 and identity tier as listed in below screenshot and also we see ESB2 is correlated to DSS tier as per app flow view. If this is not the case, Can you confirm the Orignating BT details ,is ProxyServiceMessageReceiver BT itself is originating BT hereimage.png

we also see mediator BT is making calls from ESB2 to DSS tier which in turn calls DB, Are you monitoring the correlated BT as separate BT usign custom pojo rule if that is the case we might not see correlation between Identity and DSS as the downstream tier BT is monitored as separate BT

image.png

Let us know if any disconnect in our understanding here.

Regards,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee
Humm. The flow is client --> ESB --> Identity --> ESB --> DSS --> Database
Then a response goes back to client like DSS --> ESB --> client. This is
one complete business transaction round trip.

What we are seeing is two separate sets ESB --> Identity and ESB --> DSS
--> Database. I haven't been able seen the response flow.

Any suggestions?

0 Karma

Arun_Dasetty
Super Champion

Hi,

Thanks for clarification. We understood your concerns but we see this is expected behavior given that we are either monitor the calls made from ESB -> DSS as separate BT and DSS -> DB as separate BT , refer below listed screenshot where mediator is the api calling ESB -> DSS tier and ProxyServiceMessageReceiver is separete BT

image.png

Is the same user request is calling all the above BTs if yes we need to disable rules for other BTs and define custom rule on API on originating tier that invokes all the flow between three tiers, Hope that clarifies.

Regards,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee
Hi,
Thanks for the patient replies. You wrote "Is the same user request is
calling all the above BTs if yes we need to disable rules for other BTs and
define custom rule on API on originating tier that invokes all the flow
between three tiers,"

Could you please guide how we can do this? I have been trying ( by
disabling mediator pojo rule for example) but have not succeeded.


PS : Still haven't received any word on the commercials..

0 Karma

Arun_Dasetty
Super Champion

Hi,

Please find the doc with steps to exlude and configure BT detection https://docs.appdynamics.com/display/PRO39/Configure+Business+Transaction+Detection

Can you send email to sales@appdynamics.com with your queries listed regarding pricing and see if you get help.

Regards,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

* Still * no reply from yur sales team. Its our last day of the trial. Humph!! 

Looks like you have a good product but your company is not ready for business yet..

0 Karma

Arun_Dasetty
Super Champion

Hi,

I wonder the delay is due to holiday in U.S. on 13th October could be the reason here. Also have you sent email to sales@appdynamics.com ? Can you try to contact the dial numbers in contact us page in appdynamics page after 1 day.

Regards,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee
Hi
I have used the contact us form. I have sent email to sales@appdynamics.com.
I have replied to marketing emails from Sandy Mapic. Frankly I'm now
wondering whether we should give business to such an unresponsive company.
Its a shame because you have a good product + you have provided good
support during the trial.

0 Karma

Greg_Brown
Engager

Hi,

Sorry to hear of the problems you are having engaging with our us and ultmately our sales team.

It is certainly uncharacteristic for us not to respond promptly and must sincerely appologise we have under-delivered here.  As Arun mentioned previously there was a US public holiday on Monday 13th so this might have been the reason if your communications were at this time.

I have now directly contacted our sales account management team here in the UK.  As we don't have your details to contact you please feel free to contact Andrew Westcott directly:

Andrew Westcott | Account Manager - UK
Mobile / Cell: +44 (0) 7855 234 671

Email: Andrew.Westcott@appdynamics.com

Andy is more than happy to help get you up and running or re-direct you to an account manager in one of our other worldwide offices depending on where you are based.

Regards

Greg

0 Karma

CommunityUser
Splunk Employee
Splunk Employee
Hi Greg,
Thanks for the details. In the meanwhile, Sonali has contacted me and
Naveen has provided us with a commercial quote. I will follow it up with
them.

You have a great product and I was impressed by the support provided by
akumar. Kudos and I wish AppDynamics all the best in future..

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...