Re: Performance problem before and after growing WOWorkerThreads number
Re: Performance problem before and after growing WOWorkerThreads number
- Subject: Re: Performance problem before and after growing WOWorkerThreads number
- From: Anthony Paras <email@hidden>
- Date: Tue, 12 Jun 2007 04:07:22 -0400
- Thread-topic: Performance problem before and after growing WOWorkerThreads number
In my apps, I've done the following in my components when I've needed a peer
editing context, and I've never had any problems:
public EditFooInfo(WOContext context) {
super(context);
ec = new EOEditingContext();
}
public void awake() {
super.awake();
ec.lock();
}
public void sleep() {
super.sleep();
ec.unlock();
}
You might want to log the locks and unlocks to see that they match up.
Also, you have so many sessions, yet you say you don't need sessions. You
could structure the app so it does not create sessions, or maybe just use
the session, and then do a...
session().setTimeOut(1);
To make them go away quickly.
- Tony
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden