Win a copy of Pragmatic AI this week in the Artificial Intelligence forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
  • Paul Clapham
  • Junilu Lacar
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Ganesh Patekar
  • Tim Moores
  • Pete Letkeman
  • Stephan van Hulst
  • Carey Brown
  • Tim Holloway
  • Joe Ess

Instrumentation  RSS feed

Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I am using a proprietary framework in our project. I need a help in regard for an approach to calculate the time elapsed in the different layers of the framework.

We are having different back ends to connect. The current proprietary framework has the layer (tier) wise approach to connect to back end. We are placing our requests through the access layer calling the remote EJB methods, which will in turn connect to builder and builder calls back end.

We already have abstractions for RDBMS/Queues and other back-ends where we can add instrumentation logic. However, we have issue in calculating end to end time elapsed without intruding client code and providing generic solution. It looks like as of now, there are no clear-cut entry and exit methods at client level. (Each client invokes different remote methods on remote objects. No controller in between).Is there any approach that lets to add end - end instrumentation without disturbing existing code.

Please suggest.

Posts: 5782
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Moving to "EJB and Other J2EE Technologies" forum....
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!