This week's book giveaways are in the Refactoring and Agile forums.
We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line!
See this thread and this one for details.
Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

WorkManagers

 
shweta misra
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

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 commonj.work 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()
{
try
{
wi = workmanager.schedule(this);
}
catch (IllegalArgumentException e)
{
} catch (WorkException we) {
}
}
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic