This week's book giveaway is in the Jobs Discussion forum.
We're giving away four copies of Java Interview Guide and have Anthony DePalma on-line!
See this thread for details.
The moose likes Performance and the fly likes WorkManagers Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Java » Performance
Bookmark "WorkManagers" Watch "WorkManagers" New topic


shweta misra

Joined: Jun 06, 2012
Posts: 10

We have an .ear application deployed on the weblogic server. In this application a piece of logic is being handled by a different work manager.
The following logic (given below) is written to create the work manager. We are using the APIs
No work manager is created in the Weblogic Administrtaion console and we also have also not defined the Work Manager in weblogic-aplication.xml

This code was working fine and the performance was good previously.

Recently we added additional logic in the run() {} method. Since then the overall performance per request has deteriorated. We have a load of approx 200TPS coming to this application.
We feel this is because the work manager has not been defined properly hence the threads execution has slowed down.

Please give your comments if any.

public class XYZ
implements Work
private static WorkManager workmanager = WorkManagerFactory.getFactory().getWorkManager("WorkManager-PluginConnector");

public void run()
<logic is written here>

public void schuduleTask()
wi = workmanager.schedule(this);
catch (IllegalArgumentException e)
} catch (WorkException we) {
I agree. Here's the link:
subject: WorkManagers
It's not a secret anymore!