I have a problem with an application using Tibco : a purepath is correctly created on the first instrumented JVM (Tibco API Gateway), but is not continued on the called JVM where a new purepath is created.
It seems to be related to the fact that Tibco uses Apache HTTP Client in an asynchronous way (HttpAsyncClient) not handled by the Java Web Request sensor.
Maybe it is a problem in AppMon 6.5 ? Has anyone had some experience with Tibco API or HttpAsyncClient ?
Thanks for any advice, regards,
Just checked with our TIBCO experts and they also confirmed what I thought: this should be supported out-of-the-box. Make sure you are on the latest verion of 6.5 - there have been several updates since the official 6.5 release.
If you still have issues I suggest to open a support ticket.
what version of HttpAsyncClient are you using?
because based on my recent tests AppMon 6.5 works with 4.0.x versions, as also mentioned in the officially supported systems information.
I also did some tests with the upcoming AppMon 7.0 and there the 4.1.x versions worked, too. that is not to say that we officially support it, but it might solve your issue if you're dealing with 4.1.x.
AppMon only supports the original Apache version of the Async Http Client (see release notes). Just considering the package name, it is unclear if a Apache implementation is used under the hood, or Tibco decided to implement their own async client. But anyway, if Tibco decided to wrap (removing the original package name) the original classes, it is also not supported.
It is also possible that tibco re-used a different project, which is not supported: