Diagnostic & Audit system for Java EE applications

Size: px

Start display at page:

Download "Diagnostic & Audit system for Java EE applications"

Marlene Atkinson
5 years ago
Views:

1 Diagnostic & Audit system for Java EE applications Florent Benoit, BULL/OW2 ] Secure your Java EE project with the performance diagnostic tool provided by OW2 JOnAS # 1

2 Summary Context Environment : OW2 Java EE JOnAS Application server Diagnostic tool Presentation Demo Audit tool Presentation Demo Conclusion # 2

3 Context # 3

4 Why these tools? Java EE specification: Ensure portability of applications Nothing about performance Application performance / Reliability? Applications can be Java EE compliant without being reliable Finding performance problems? Not so easy to find the problem with all components that are linked together. Traceability Get a log for each executed operation «Cost» of services For example, to know the memory used for a request # 4

5 Environment : OW2 Java EE JOnAS Application server # 5

JOnAS: Java EE Application server Java EE 5 certified Java EE

persistence / JPA 1 & 2: EasyBeans (EclipseLink, Hibernate,

CXF/Axis2 Asynchronous Messages: JORAM OSGi: Felix et IPOJO

6 JOnAS: Java EE Application server Java EE 5 certified Java EE services: Web Container: Tomcat (6 & 7) / Jetty EJB3 persistence / JPA 1 & 2: EasyBeans (EclipseLink, Hibernate, OpenJPA) Transactions: JOTM Clustering: CMI Web Services: CXF/Axis2 Asynchronous Messages: JORAM OSGi: Felix et IPOJO Administration: web console, commands, API, JASMINe (Advanced management tool) # 6

org OW2: independent industry consortium dedicated to developing open source code

7 JOnAS : Open Source Server Developed as an open source server (LGPL) within OW2: OW2: independent industry consortium dedicated to developing open source code middleware Major contributors for JOnAS :Bull, France Telecom, Peking University, INRIA, UJF, UNIFOR, SERLI Linked OW2 projects : EasyBeans, JASMINe, JORAM, JOTM, CMI # 7

Extensibility Profiles Enhanced application server

8 OSGi native Architecture Dynamically adaptable platform OSGi based services Modularity / Extensibility Profiles Enhanced application server life cycle On-Demand services Dynamic configuration Adaptable # 8

9 Diagnostic tool # 9

10 Diagnostic tool JDBC Connection leak detector # 10

11 «Pool» of JDBC connections Limit the number of physical connections to the database Optimize the time to provide a JDBC connection to the application datasource.getconnection(); connection.createstatement(); DataSource Pool connection.close(); # 11

12 Forgot to call connection.close()? Busy connections (used by applications) or not yet closed DataSource Pool Empty Pool Problem : No more available connections for new clients Connections never closed don't go back in the pool Other clients are waiting No free connections in the pool! # 12

13 Handling the connection leak? Avoid these connection leaks in production? Automatic close of JDBC Connections by JOnAS At the end of a method call (EJB stateless / HTTP request), remove() on stateful EJB beans. Life-time of JDBC connections If no calls are done on a JDBC connection for a given amount of time, this connection is released and go back in the pool These solutions are only patches Goal: Fix the problem in the application's code Help provided by the JOnAS web console Track the root of the problem # 13

14 Servlet using JDBC connections 55 protected void doget(...) { 56 response.setcontenttype("text/html"); 57 PrintWriter out = response.getwriter(); 58 out.println("<html><body>"); DataSource ds = null; 61 try { 62 ds = (DataSource) new InitialContext().lookup("jdbc_1"); 63 ds.getconnection(); 64 } catch (NamingException e) { 65 e.printstacktrace(); 66 } catch (SQLException e) { 67 e.printstacktrace(); 68 } finally { 69 out.println("</body></html>"); 70 out.close(); 71 } } # 14

15 Screenshot of JOnAS Admin console Line to analyze # 15

16 Servlet with the JDBC error 55 protected void doget(...) { 56 response.setcontenttype("text/html"); 57 PrintWriter out = response.getwriter(); 58 out.println("<html><body>"); DataSource ds = null; 61 try { 62 ds = (DataSource) new InitialContext().lookup("jdbc_1"); 63 ds.getconnection(); 64 } catch (NamingException e) { 65 e.printstacktrace(); 66 } catch (SQLException e) { 67 e.printstacktrace(); 68 } finally { 69 out.println("</body></html>"); 70 out.close(); 71 } } # 16

17 Demo Tracking JDBC connection leaks # 17

18 Diagnostic tool Monitoring/displaying JVM Threads # 18

19 Information about JVM threads # 19

20 Demo Threads monitoring # 20

21 Audit tools # 21

22 Goals of the audit system [1/2] Development Discovery of the software architecture of applications and calls between the Java EE modules Difficult to track (complex/distributed applications ) Tracking the performance problems: Enhance the performance Identify the component that is causing the problem Qualifying Statistics on features/services that are used (top 10,...) Adapt applications to their usage Trends on applications/services Response time,... # 22

23 Goals of the audit system [2/2] Production Audit Traceability Log of services that have been used Billing (You pay what you're using) (Google App Engine) # 23

24 Commercial Tools Commercial tools CA Wily Introscope dynatrace BMC AppSight Compuware Vantage Analyzer # 24

25 Solution based on interceptors Different level of interceptors Enabling/disabling on demand EJB 3 Invocation (Business service calls) Lifecycle (Start/Stop) HTTP requests Servlet filter JNDI access Each call on the context returned by the command new InitialContext()»: lookup, bind, etc. # 25

26 Architecture of the Audit System EasyBeans Tomcat JNDI JMX Notifications JOnAS Admin (Audit module) Audit log Audit System JASMINe Jconsole / JMX Client # 26

27 Collected data [1/2] EJB3 Invocation Bean's name Identity (name + roles) OnMessage Size of method parameters Result Elapsed time in the method Exceptions # 27

28 Collected data [2/2] HTTP URL Encoding Client (protocol,host, port) SessionId Query Status HTTP JNDI Method that is called on the InitialContext bind, lookup,... Parameters (if any) Elapsed time # 28

29 Client of Audit MBeans Collecting data Traceability / Logger Storage in a log file Human readable format [10/03/04 22:05:35] class org.ow2.util.auditreport.impl.invocationauditreport requeststart = requeststop = requestduration = businessmethod = getcalculator@local BeanName = Calculator target = /easybeans/audit-sample.ear/audit-sample-ejb.jar/sessionfacade/getcalculator@local paramsize = 5 returnsize = 0 freememorybefore = totalmemorybefore = freememoryafter = totalmemoryafter = sweepmarktime = 873 scavengetime = 5170 user = ANONYMOUS roles = [JOnAS] requesttimestamp = methodstacktrace = [java.lang.thread.getstacktrace(thread.java:1409) -... ] methodparameters = null Elapsed time Called method Identity Parameters # 29

30 Screenshot of the tool # 30

31 Screenshot of a method's graph # 31

32 Advanced mode Tracking a request on several servers Tracking asynchronous calls Sending to JMS queue / Receiving from a JMS queue ID JMS EJB Servlet ID Server 2 ID Server 1 ID MDB EJB Server 3 Collecting Events Server 4 # 32

33 Demonstration # 33

34 Demo Goal of the demonstration Enhancing the performances of an application Discovering problems Solving problems Checking this with the audit console Traceability of calls in an application # 34

35 Conclusion # 35

36 Conclusion [1/2] Preventing performance problems Secure a project Tools can be used in designing/integrating/production In production, an other Java EE server may be used Tool bundled with JOnAS Key feature comparing to other Java EE servers Ready to use Open Source / LGPL Integrated in JOnAS 5.2 # 36

37 Conclusion: what's next? [2/2] Supervising OSGi service Available OSGi services Links between components/services Supervising JPA Life cycle of Entities Other metrics SQL request Number of requests... Elapsed time of requests # 37

38 Q & A Florent Benoit, BULL/OW2 ] # 38

Reliable asynchronous web-services with Apache CXF

Reliable asynchronous web-services with Apache CXF Florent Benoit, BULL/OW2 [ @florentbenoit ] Guy Vachet, France Telecom [guy.vachet@orange-ftgroup.com] New CXF transport allowing reliable Web Services