Team Center Experience Cards Showing "No Traffic" or "No Data"

Article Id: 103307
Status: Published
Updated On: 13-08-2018 03:36
Products:
CA Application Performance Management Agent (APM / Wily / Introscope) INTROSCOPE
Issue/Introduction:

We noticed this morning that the experience cards are no longer showing data/traffic. We are still able to see metrics via Investigator (or drilling down to the vertices in Map view). We noticed in the logs that we started getting an Internal Server error:

03:07:01.288 AM PDT [ERROR] [pool-23-thread-4] [Manager.AppMap.RESTFederate] Error when invoking internal controller. 
java.lang.reflect.InvocationTargetException 
 at sun.reflect.GeneratedMethodAccessor621.invoke(Unknown Source) 
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
 at java.lang.reflect.Method.invoke(Method.java:498) 
 at com.wily.introscope.appmap.em.services.impl.AGCServiceImpl$FollowerInvocationHandler$1.run(AGCServiceImpl.java:486) 
 at com.wily.introscope.appmap.em.services.impl.AGCServiceImpl.callFollowers(AGCServiceImpl.java:144) 
 at com.wily.introscope.appmap.em.services.impl.AGCFollowerServiceImpl.callFollowers(AGCFollowerServiceImpl.java:100) 
 at com.wily.introscope.appmap.em.services.ResponseWrapper.doRequest(ResponseWrapper.java:88) 
 at com.wily.introscope.appmap.em.services.ResponseWrapper.doRequest(ResponseWrapper.java:83) 
 at com.wily.introscope.appmap.rest.controllers.agc.AGCMetricController.getMetricValues(AGCMetricController.java:211) 
 at com.wily.introscope.appmap.rest.controllers.agc.AGCLandingControllerImpl.getMetricValuesWitthoutCache(AGCLandingControllerImpl.java:1659) 
 at com.wily.introscope.appmap.rest.controllers.agc.AGCLandingControllerImpl.loadCacheRangeMetrics(AGCLandingControllerImpl.java:1859) 
 at com.wily.introscope.appmap.rest.controllers.agc.AGCLandingControllerImpl.loadCacheRangeMetrics(AGCLandingControllerImpl.java:1842) 
 at com.wily.introscope.appmap.rest.controllers.agc.AGCLandingControllerImpl.loadCache(AGCLandingControllerImpl.java:1878) 
 at com.wily.introscope.appmap.rest.controllers.agc.AGCLandingControllerImpl.synchronizeCache(AGCLandingControllerImpl.java:1717) 
 at sun.reflect.GeneratedMethodAccessor803.invoke(Unknown Source) 
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
 at java.lang.reflect.Method.invoke(Method.java:498) 
 at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:65) 
 at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) 
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) 
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) 
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
 at java.lang.Thread.run(Thread.java:745) 
Caused by: com.wily.introscope.appmap.rest.exceptions.RestApiException: INTERNAL_SERVER_ERROR 
 at com.wily.introscope.appmap.rest.controllers.MetricControllerImpl.getMetricValues(MetricControllerImpl.java:92) 
 ... 26 more 
Caused by: com.wily.introscope.spec.metric.BadlyFormedNameException: "Frontends|Apps| Web Application|URLs|" is not a legal Metric name

Cause:

 Trouble handling the illegal metric name in the path. Some Frontend names ends with “|” and thus creating a bad metric name. In customer’s case its "Frontends|Apps|Booking Web Application|URLs|". “|” @ the end of URLs has caused this.

Environment:

APM 10.7.0 SP 1

Resolution:

Obtain the desktop fix in DE368014 or DE370152 and place on top of APM 10.7.0 SP1 .
This is now addressed in APM 10.7.0 HF11 and later.