PDA

View Full Version : Insight does not have any application or trace...



cgeyma@gmail.com
Nov 16th, 2010, 03:07 PM
I am using STS tc Server Developer Edition v2.0.
My application uses Spring 2.5.6.
It starts up and runs fine in Insight but no application or trace is displayed when the application is running.

I have read most the threads in this forum with similar problem but could not find a solution.

When the server starts up, I get the following log output.
I thought "ASPECTJ: aspectj.overweaving=true: overweaving switched ON" would indicate things are loading up find in Insight.

However, everything started up fine, application is running with no problem and just no application and trace displayed in http://localhost:8080/insight.

Any ideas?

Thanks.

Nov 16, 2010 4:03:57 PM com.springsource.insight.tcserver.WeavingHelper findRepositoriesForClassPath
INFO: file:/C:/springsource/tc-server-developer-2.0.4.RELEASE/spring-insight-instance/insight/collection-plugins/insight-collection-1.0.0.M3.SR02.jar: aspects will be woven into the main Tomcat classloader
Nov 16, 2010 4:03:57 PM com.springsource.insight.tcserver.WeavingHelper findRepositoriesForClassPath
INFO: file:/C:/springsource/tc-server-developer-2.0.4.RELEASE/spring-insight-instance/insight/collection-plugins/insight-plugin-jdbc-1.0.0.M3.SR02.jar: aspects will be woven into the main Tomcat classloader
ASPECTJ: aspectj.overweaving=true: overweaving switched ON
Nov 16, 2010 4:03:57 PM com.springsource.tcserver.security.PropertyDecoder <init>
INFO: tc Runtime property decoder using memory-based key
Nov 16, 2010 4:03:58 PM com.springsource.tcserver.security.PropertyDecoder <init>
INFO: tcServer Runtime property decoder has been initialized in 357 ms
Nov 16, 2010 4:03:58 PM com.springsource.tcserver.serviceability.rmi.JmxSo cketListener init
INFO: Started up JMX registry on 127.0.0.1:6969 in 130 ms
Nov 16, 2010 4:03:59 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Nov 16, 2010 4:03:59 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1277 ms
Nov 16, 2010 4:03:59 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina

sandrews
Nov 16th, 2010, 08:34 PM
Even though the Insight dashboard is deployed, it may be configured to not collect traces. If you double click on the server, there will be a configuration section and checkbox to enable Insight collection.

Let us know if you have trouble.

cgeyma@gmail.com
Nov 16th, 2010, 09:57 PM
Yes, in the SpringSource tc Server Developer Edition v2.0 view, there is an Insight tab. In this tab, there is a checkbox for "Enable gathering of metrics". This is checked.

I have also read in other threads about the context.xml needing some extra configuration. I tried those and it did not help. In fact, when I put those suggestions in, the tc server did not start up correctly. My current context.xml is the following. Should it be different?

<Context>

<!-- Default set of monitored resources -->
<WatchedResource>WEB-INF/web.xml</WatchedResource>

<!-- Uncomment this to disable session persistence across Tomcat restarts -->
<!-- <Manager pathname="" /> -->

<!-- Uncomment this to enable Comet connection tacking (provides events
on session expiration as well as webapp lifecycle) -->
<!-- <Valve className="org.apache.catalina.valves.CometConnectionManagerV alve"
/> -->

</Context>

cgeyma@gmail.com
Nov 16th, 2010, 10:07 PM
Additional information. My applications are configure in C:\springsource\tc-server-developer-2.0.4.RELEASE\spring-insight-instance\conf\catalina\localhost directory. This directory has the xml file for the application and the xml file has the <Context docBase="xyz" /> where xyz is the webroot of the application.

Is this why Insight is not picking up the app even though tc Server is able to load and run the app?

I see in the tc Server config in STS there is a Deploy path attribute and default to wtpwebapps. Should my app be deployed to this directory? I changed this attribute to point to the webroot of my application and it does not make a difference.

Thanks.

cgeyma@gmail.com
Nov 18th, 2010, 11:17 AM
OK. Problem resolved.
I tried another STS setup in Linux and Insight has no problem displaying metrics. I then compare the config between my Windows STS setup and Linux STS setup and found the the tcserver.node in Properties is different. My Windows setup has the value of "tcServer" and Linux has "spring-insight-instance-07156". I changed the Windows setup to use "spring-insight-instance-07156" and it is working now. Although I still don't know what tcserver.node is and what the value "spring-insight-instance-07156" represents.

I will read the doc to find out and if anyone can explain, it will be great.

Thanks.

cgeyma@gmail.com
Nov 19th, 2010, 12:57 PM
Forgot to mention that the following was also missing from the context.xml file. With the following added and the tcserver.node defined, all is well.

<Valve className="com.springsource.insight.collection.tcserver.reque st.HttpRequestOperationCollectionValve"/>

<Loader loaderClass="com.springsource.insight.collection.tcserver.ltw.T omcatAspectJWeavingClassLoader" useSystemClassLoaderAsParent="false"/>

<Listener className="com.springsource.insight.collection.tcserver.lifec ycle.ApplicationLifecycleCollectionListener"/>