WebLogic Server Deep Dive

Transcription

1 WebLogic Server Deep Dive Stephan Rudolph ( rudolph AG ) & Michael Fuhr ( Oracle Deutschland BV & CoKG )

2 Agenda Whole Server Migration WorkManager Parameter Injection via Deployment Plan

3 Whole Server Migration When typical Whole Server Migration comes in use: Power Supply Interrupt Split Brain Weblogic Server Instance run into status FAILED

4 Whole Server Migration Power Supply Interrupt Node 1 Domain_30 Node 2 Node 3 Server_30 Cluster Server_31 Server_32 Server_33

5 Whole Server Migration Power Supply Interrupt Node 1 Domain_30 Node 2 Node 3 Server_30 Cluster Server_31 Server_32 Power Supply Inter ruption Server_33

6 Whole Server Migration Power Supply Interrupt Node 1 Domain_30 Node 2 Node 3 Server_30 Cluster Server_31 Server_32 Server_33

7 Whole Server Migration Power Supply Interrupt Node 1 Domain_30 Node 2 Node 3 Server_30 Cluster Server_33 Server_31 Server_32 Server_33

8 Whole Server Migration Configuration

9 Whole Server Migration Power Supply Interrupt

10 Whole Server Migration Power Supply Interrupt

11 Whole Server Migration Split Brain Node 1 Domain_30 Node 2 Node 3 Server_30 Cluster Server_31 Server_32 Server_33

12 Whole Server Migration Split Brain Node 1 Domain_30 Node 2 Node 3 Server_30 Cluster Server_31 Server_32 Server_33 Connection Interrupt

13 Whole Server Migration Split Brain Node 1 Domain_30 Node 2 Node 3 Server_30 Cluster Server_33 Server_31 Server_32 Server_33 Unter brechung

14 WSM Split Brain Simualtion

15 WorkManager - The unknown tuning option

16 WorkManagers

17 The WebLogic Self Tuning thread pool Network Socket Handlers ( Muxers ) Request Queue Self Tuning Thread Pool Active Standby Stuck Hogging Asynchronously dispatched work from WebLogic kernel, subsystem, or application 1 Monitor rate of request processing 2 Adjust thread pool size accordingly

18 Work Managers - The WebLogic Self Tuning thread pool Why partition work? Fair share between applications Dead-lock avoidance Strict ordering Prioritisation of classes of work Efficient resource utilization - Self-tuning Throttling Every request is associated with a Work Manager Dispatch Policy Statistics Work Managers Every application has its own Work Manager WebLogic sub-systems have Work Managers Can configure additional Work Managers for applications and modules

19 Work Managers The Default WorkManager This is implemented to handle thread management and perform self-tuning This instance will be used also by an application if no other WorkManager is configured in the application's deployment descriptors Global WorkManagers These WorkManagers have the scope of the domain and are defined in configxml An application can use a Global WorkManager as a blueprint and create its own instance The work associated with that application can then be distinguished from the work from other applications Application-scoped WorkManagers It is possible to create WorkManagers which are available only to a specific application or module These can be specified in either weblogic-applicationxml, weblogic-ejb-jarxml, or weblogicxml

20 What Is and does a WebLogic WorkManager? WebLogic Server maps incoming requests to a WorkManager instead of executing queues Multiple WorkManagers can be present WorkManager can contain four types of components Request Classes (Context-based, FairShare, ResponseTime Goal) MaxThreadsConstraints MinThreadsConstraints Capacities

21 WLS Work Managers Self Tuning Threading Model Resource management and scheduling is delegated to WLS Leverages work managers across the System, eliminating manual tuning for performance

22 Optimizing Work Managers Data source connections auto adjust max thread constraint that manages relative capacity of work managers Incoming Requests Internal Process Other Processes

23 Configuration with WLST try: connect('adminuser','adminpasswd','t3://adminhost:adminport') edit() startedit() c=input('enter the Max Thread Count: ') mtc='maxthreadsconstraint'+str(c) cd('/selftuning/wd1') cmocreatemaxthreadsconstraint(mtc) cd('/selftuning/wd1/maxthreadsconstraints/'+mtc) cmosetcount(c) set('targets',jarrayarray([objectname('combea:name=appclstr,type=cluster')], ObjectName)) cd('/selftuning/wd1') wm = cmocreateworkmanager('pwm1') cd('/selftuning/wd1/workmanagers/pwm1') set('targets',jarrayarray([objectname('combea:name=appclstr,type=cluster')], ObjectName)) cmosetmaxthreadsconstraint(getmbean('/selftuning/wd1/maxthreadsconstraints/'+mtc)) save() activate() except (WLSTException, BeanAlreadyExistsException), e: print 'Error in script:', e canceledit('y') else: disconnect() Output: Starting an edit session Started edit session, please be sure to save and activate your changes once you are done Enter the Max Thread Count: 50 Saving all your changes Saved all your changes successfully Activating all your changes, this may take a while The edit lock associated with this edit session is released once the activation is completed Activation completed Disconnected from weblogic server:

24 Configuration with WLST (2) try: connect('adminuser','adminpasswd','t3://adminhost:adminport') edit() startedit() cd('/selftuning/wd1') cmocreatecapacity('pcap2') cd('capacities/pcap2') set('count',10) set('targets',jarrayarray([objectname('combea:name=appclstr,type=cluster')], ObjectName)) cd('/selftuning/wd1') wm = cmocreateworkmanager('pwm2') cd('/selftuning/wd1/workmanagers/pwm2') set('targets',jarrayarray([objectname('combea:name=appclstr,type=cluster')], ObjectName)) cmosetcapacity(getmbean('/selftuning/wd1/capacities/pcap2')) save() activate() except (WLSTException, BeanAlreadyExistsException), e: print 'Error in script:', e canceledit('y') else: disconnect()

25 Summery of the WorkManager WLST commands create(workmanagername,'workmanagers') create(maxthreadconstraintname,'maxthreadsconstraints') create(minthreadconstraintname,'minthreadsconstraints ) Set('Count',10) create( TestFairShare', 'FairShareRequestClass') set("fairshare", 100) create('testcontextrequest', 'ContextRequestClass') set('target', MyServer')

26 Summery of the WorkManager WLST commands (2) create('testcontextcase', 'ContextCase') set("requestclassname", "RequestClassName") set("groupname", "Deployers") set( UserName", "maindeployer") create('testresponsetimerequest', 'ResponseTimeRequestClass') set("goalms", 500)

27 Sample weblogicxml <?xml version="10" encoding="utf-8"?> <wls:weblogic-web-app xmlns:wls=" xmlns:xsi=" xsi:schemalocation=" <wls:weblogic-version>1036</wls:weblogic-version> <wls:context-root>workmanagerweb</wls:context-root> <wls:work-manager> <wls:name>mycustomworkmanager</wls:name> <wls:max-threads-constraint> <wls:name>5maxthreads</wls:name> <wls:count>5</wls:count> </wls:max-threads-constraint> <wls:capacity> <wls:name>7maxcapacity</wls:name> <wls:count>7</wls:count> </wls:capacity> </wls:work-manager> </wls:weblogic-web-app>

28 Advantage of using the WorkManager Fine-grained tuning Option Stability of the system Monitoring and Analysing Options

29 Parameter Injection via Deployment Plan

30 Parameter Injection via Deployment Plan Imagine, for example, situations like these: You want to tune a Java EE application It consists of a huge amount of EJB s, but no EJB tuning parameters (max-beans-in-free-pool, etc) are configured You want to configure and access them all You want to replace a default implementation of a Java EE application by adding your own library references Always, you want it be done easily, on multiple, different WebLogic Server environments, without modifying any deployment descriptor file, included in the Java EE application archive

31 Parameter Injection via Deployment Plan

32 Parameter Injection Sample: Adding Tuning Parameters <deployment-plan> <variable-definition> <variable> <name>statefulsessiondescriptor_maxbeansincache_planit_ </name> <value>1000</value> </variable> </variable-definition> <module-override> <module-descriptor> <variable-assignment> <name>statefulsessiondescriptor_maxbeansincache_planit_ </name> <xpath>/weblogic-ejb-jar//stateful-session-cache/max-beans-in-cache</xpath> </variable-assignment> </module-descriptor> <module-override> </deployment-plan>

33 Parameter Injection Sample: Adding Tuning Parameters

34 Parameter Injection Sample: Adding Tuning Parameters before after

35 Parameter Injection Sample: Adding Library References <deployment-plan> <variable-definition> <variable> <name>weblogicapplication_libraryname_pi_ </name> <value>slf4j-api-175</value> </variable> </variable-definition> <module-override> <module-descriptor> <variable-assignment> <name>weblogicapplication_libraryname_pi_ </name> <xpath>/weblogic-application//[context-root="null",library-name="slf4j-api-175"]/library-name</xpath> </variable-assignment> </module-descriptor> <module-override> </deployment-plan>

36 Parameter Injection Sample: Adding Library References

37 Parameter Injection Sample: Adding Library References

38 Parameter Injection Sample: Adding Library References

39 Questiones and Answers???!!!