Win a copy of Escape Velocity: Better Metrics for Agile Teams this week in the Agile and Other Processes 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Tim Cooke
  • Paul Clapham
  • Jeanne Boyarsky
Sheriffs:
  • Ron McLeod
  • Frank Carver
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Frits Walraven
  • fred rosenberger

Default stack of interceptors execution time

 
Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,
I am having performance related problems with an app that is using Struts 2.0.
I was wondering if the "default" stack of interceptors takes a lot of time to execute (1-2 sec)?

Thanks in advance
 
Bartender
Posts: 9626
16
Mac OS X Linux Windows
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Unlikely. When you are hunting for a performance problem, as our Enterprise Performance FAQ says, Measure, Don't Guess. I used the JAMon tool mentioned in the FAQ and highly recommend it.
 
Andrei Antonescu
Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for the info. I will try using JAMon to monitor performance and hopefully I will find the problem.
 
Greenhorn
Posts: 28
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have been profiling my app (Netbeans profiler) and indeed I can see where a simple request takes time.

The DefaultActionInvocation.executeResult takes the 87.4% of the request, anybody knows what takes really the
time here?
Is it building the beans from the HttpRequest parameters? is the actual execution of the result (dispatching the JSP)?

Any tip to make it lighter/quicker (without updating com.opensymphony code)?

Tnx
Beppe
 
Joe Ess
Bartender
Posts: 9626
16
Mac OS X Linux Windows
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The JavaDoc says:

Uses getResult to get the final Result and executes it


So I would assume that means it is processing your JSP. What's your JSP doing that is taking so long? Creating a huge table from a result set perhaps?
 
I think he's gonna try to grab my monkey. Do we have a monkey outfit for this tiny ad?
Garden Master Course kickstarter
https://coderanch.com/t/754577/Garden-Master-kickstarter
reply
    Bookmark Topic Watch Topic
  • New Topic