Tomcat 6 Install Logged Error - 'ForkingThreadRuleApplier - configure was not called before start!'

[CommunityUser]

We have AppDynamics Lite running on jdk1.6.0_18 and Tomcat 6 on Solaris Unix.
I am getting the following error in the agent.log file:
[main] 01 Oct 2013 14:44:53,551 ERROR ForkingThreadRuleApplier - configure was not called before start!
[main] 01 Oct 2013 14:44:53,551 INFO LifeCycleManager - Started service [TransactionMonitoringService]
[main] 01 Oct 2013 14:44:53,601 INFO ConfigurationChannel - Sending Registration request with: Application Name [Server App], Tier Name [Server Tier
], Node Name [Server Node], Host Name [d00109] Node Unique Local ID [Server Node], Version [Server Agent Lite v3.3.4.0 RC Build Date 2013-03-20 20:23
]
[main] 01 Oct 2013 14:44:53,804 ERROR ConfigurationChannel - Fatal transport error: Connection refused
[main] 01 Oct 2013 14:44:53,804 WARN ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [127.0.0.1], port[8180], exception [Fatal transport error: Connection refused]

The command line for the java invocation had the -javaagent & -Dappdynamics.viewer.port=8180 arguments added

Any help appreciated in particular what are some of the possible reasons for getting
ForkingThreadRuleApplier - configure was not called before start!
which is the first ERROR appearing in the logfile.

[Arun_Dasetty]

Hi Michael,

Thanks for writing to us. For now you can ignore the error "ERROR ForkingThreadRuleApplier - configure was not called before start!" an this should not cause any issue in agent registration and the error message raises because we don't ship default thread correlation rules with the lite version, and this error is already fixed in latest release or will not raised in future lite release, hope that clarifies your query.

Regarding the actual error causing the lite agent registration failed "ERROR ConfigurationChannel - Fatal transport error: Connection refused", we understood that you have started lite viewer at 8180 port, let us know if any disconnect, as we see the default lite viewer port is 8990
we hope you have started liteviewer as follows at the same machine on which lite agent is installed:
shell> java -Dadlite.port=8180 -jar adlite-viewer.jar

If this is the case, please make sure Lite viewer is accessible from lite agent machine, if this is not the case, and lite viewer and lite agent is installed in different machines then we request you to make sure ping is successfull and lite viewer is running:
shell> ping <viewerhost-from-agent-machine>
shell> ping 192.168.1.19  (say: viewer is running on this IP and lite agent is running on different ip)


Now add the following parameter to the server (with lite agent configured), (say: lite agent is installed on 192.168.1.10 and liteviewer is running at 192.168.1.19 host)
in startup script of server (with lite agent configured) add the folowing parmas in addition to -javaagent arg:

export JAVA_OPTS="$JAVA_OPTS -Dappdynamics.viewer.host=192168.1.19 -Dappdynamics.viewer.port=8180 -javaagent:<liteagent_dir>/javaagent.jar"

refer docs: http://litedocs.appdynamics.com/display/ADLite/Installing+the+Viewer
http://litedocs.appdynamics.com/display/ADLite/Apache+Tomcat
http://litedocs.appdynamics.com/display/ADLite/Installing+the+Application+Server+Agent
http://litedocs.appdynamics.com/display/ADLite/Java+Configuration+Properties

Let us know if that information helps

Thanks,

Arun

[CommunityUser]

Resolved - thanks for the answer.

Regarding the first exception in the log "ERROR ForkingThreadRuleApplier - configure was not called before start!" - glad to hear it will be removed due to it being extraneous.

Regarding the second exception - yes I had a firewall problem preventing connection to agent; this is now resolved.