aspose file tools*
The moose likes Websphere and the fly likes WAS Entity Beans killing performance Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "WAS Entity Beans killing performance" Watch "WAS Entity Beans killing performance" New topic
Author

WAS Entity Beans killing performance

Max Tomlinson
Ranch Hand

Joined: Jul 17, 2001
Posts: 365
Hi-
I'm seeing a situation where in WSAD where retrieval of entity beans (some 600-700) is locking up WSAD for 20 minutes+ after the finds have finished. Is this some sort of background process e.g. ejbStore? How to modify this?
thanks,
max
Max Tomlinson
Ranch Hand

Joined: Jul 17, 2001
Posts: 365
I understand most app servers can be set to not kick off ejbStore + ejbLoad so ofter...does anyone know where a WAS 4.0 configuration PDF might be?
thanks
Vinod Bijlani
Ranch Hand

Joined: Mar 06, 2002
Posts: 133
"some 600-700" whts tht?
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
    
    5
Max,
do a kill -3 on the app server to force it to do a thread dump (http://www.websphere-world.com/html/threaddump.html). Then look through the dump and find out what method your thread is working on. That's probably going to hone in on your problem.
There's no special post-processing that WebSphere does outside of what the EJB spec wants. I think you should be enlightened by what you see in the thread dump. If not, post the results here and we'll see what we can do.
Kyle


Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at http://www.kyle-brown.com/ for other WebSphere information.
Max Tomlinson
Ranch Hand

Joined: Jul 17, 2001
Posts: 365
Kyle-
Thanks. The work being done is ejbStore which is running once per bean and taking FOREVER...(we are usign BMP which generates a SQL update)...we decided to use simple DAOs called from a session bean for large queries that return collections of beans and use entity beans for indiviual bean access.
ax
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
    
    5
Good. You've found the problem, and you've arrived at the most common solution. That should help...
Kyle
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: WAS Entity Beans killing performance