AppD Archive

ERROR: Rolling file C:\JavaAgent\App**

CommunityUser
Splunk Employee
Splunk Employee

Hi,

I am getting the above error and the application start after 15 minutes. Whereas when I remove the appdynamic's -javaagent argument from the application it starts normally. 

This is a unique problem because sometime the error is there and sometime it does not appear. But when it appreas it even stops my application(to be monitored) from starting for a very long time.

When I change the javaagent then again one time it starts correctly but then there is no guarantee that this will work another time.

Tags (2)
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

We have installed appdynamic on IBM liberty profile.we already enabled log level of jvm as INFO.After this app dynamic installation , we are getting only error logs alone and we are not getting other logs.will any one able to help me on this?

<logging traceSpecification="com.worklight.adapters=debug:com.worklight.integration=debug" consoleLogLevel="INFO"/>

0 Karma

Arun_Dasetty
Super Champion

Hi Nagendra,

Can you please send the following to debug further:

- Provide 5-10 thread dumps when delay in server startup issue happens

- zipped version of logs under <agent_install_dir>/logs path

- complete error console logs

Once you collect all above logs can you add the following jvm arg in addition to -javaagent entry in server startup script and 

see if jvm/webapp starts bit faster after jvm restart:

-Dappdynamics.bciengine.class.lookahead=*

Regards,

Arun

Tags (2)
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

The error occurs in my application window. But they are not in the log files of agent not the server. 

Due to security reason I cannot provide the log files of my application. 

Please let me know if you need more information. 

Tags (2)
0 Karma

Arun_Dasetty
Super Champion

Hi Nagendra,

If you have concerns you can send the logs requested in a private message, hope that is fine with you.

Also did you checked the behavior with lookahead jvm arg and restart jvm as suggested earlier?

Regards,

Arun

Tags (2)
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

We are testing in a test environment. And our log files are pretty confidential. I can just say that the error which is appered in in the scree shot above. 

Please let me know what is causing it?

And this argument: -Dappdynamics.bciengine.class.lookahead=*​  does not help the application. 

I have seen in bytecodetransformer log file. It is reading all my classes name, saying got successfully verified, but this really slows my application down. Please suggest. My applicaton has millions of classes.

0 Karma

Arun_Dasetty
Super Champion

Hi Nagendra,

As per discussion in your help ticket # 28614 , Can you leave node-name element in controller-info.xml blank if you want to use same agent_dir but want to name each JVM instance using -javaagent arg a unique node dynamically and see how it goes after server restart with following -D jvm args in place:

-Dappdynamics.agent.reuse.nodeName=true -Dappdynamics.agent.auto.node.prefix=myPrefix

Also regarding the delay in agent startup Can you please change the jvm lookahead arg as below if you are using older agent version say pre-3.8.3 version: 

 -Dappdynamics.bciengine.class.lookahead=!*  (note the addition of symbol in the new arg)

Let us know if that information helps. 

Regards,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Arun, 
I am getting this error after adding that -D jvm agrgs

[WARN]: AgentInstallManager - Invalid Edition [Java Agent]. Keeping current edition [S
[INFO]: JavaAgent - Using Java Agent Version [Server Agent v3.9.2.1 GA #2014-09-05_20-
[INFO]: JavaAgent - Running IBM Java Agent [No]

Could not start Java Agent because unable to determine Tier Name or Node Name

Agent Logging Directory [C:\JavaAgent\AppServerAgent3921\logs\unknown]

Here are the agent log files:

0 Karma

Arun_Dasetty
Super Champion

Hi Nagendra,

Somehow the tier name is also left blank i guess under C:\JavaAgent\AppServerAgent3921\conf\controller-info.xml and also it looks the node related JVM args are not picking up under jvm startup settings file in whcih you have added -javaagent:"C:\JavaAgent\AppServerAgent3921\javaagent.jar" entry, Can you please and correct and restart JVM if issue still persists please provide the controller-info.xml at C:\JavaAgent\AppServerAgent3921\conf path and jvm startup settings in addition to following command output:

cmd> JPS -v

JPS is command from JDK_HOME/bin path that list output like ps -ef | grep "java" in linux for windows

Regards,

Arun

0 Karma
Get Updates on the Splunk Community!

What You Read The Most: Splunk Lantern’s Most Popular Articles!

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

See your relevant APM services, dashboards, and alerts in one place with the updated ...

As a Splunk Observability user, you have a lot of data you have to manage, prioritize, and troubleshoot on a ...

Index This | What goes away as soon as you talk about it?

May 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this month’s ...