Win a copy of Microservices Testing (Live Project) this week in the Spring 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 ...
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

Web application moved from Websphere6.0 to 6.1 has Performance Issues

Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Trying to migrate Java Web Application (JDK1.4) from Websphere 6.0 to 6.1 to upgrade to Java5.
To test loaded on local server , gives performance issues while loading or displaying a page.
Performance issue is predominant while loading any page with query.
Being a Java developer and not so much of Websphere admin experience..tried tracing, logging , debugging to identify the problems.
Did set Tivoli performance Viewer to see performance issues via Admin console..nothing unusual as in hung threads or pool connection issue is noticeable via Tivoli other than CPU usage hikes while loading the page.
Can anyone guide on what will be the best way to trace the performance issue as in -
Which tool will help me track down transaction management issues or Hung thread issues ?
What could be problem areas which I should be looking into considering JDK1.4 app compatibility with websphere 6.1?

Any help to get some direction would be appreciated


author & internet detective
Posts: 41184
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Do you know what is taking the time? If it is literally rendering the page, maybe you have memory issues. WebSphere does use a larger memory footprint with each release.
Don't get me started about those stupid light bulbs.
    Bookmark Topic Watch Topic
  • New Topic