Book Image

Performance Testing with JMeter 3 - Third Edition

By : Bayo Erinle
Book Image

Performance Testing with JMeter 3 - Third Edition

By: Bayo Erinle

Overview of this book

JMeter is a Java application designed to load and test performance for web application. JMeter extends to improve the functioning of various other static and dynamic resources. This book is a great starting point to learn about JMeter. It covers the new features introduced with JMeter 3 and enables you to dive deep into the new techniques needed for measuring your website performance. The book starts with the basics of performance testing and guides you through recording your first test scenario, before diving deeper into JMeter. You will also learn how to configure JMeter and browsers to help record test plans. Moving on, you will learn how to capture form submission in JMeter, dive into managing sessions with JMeter and see how to leverage some of the components provided by JMeter to handle web application HTTP sessions. You will also learn how JMeter can help monitor tests in real-time. Further, you will go in depth into distributed testing and see how to leverage the capabilities of JMeter to accomplish this. You will get acquainted with some tips and best practices with regard to performance testing. By the end of the book, you will have learned how to take full advantage of the real power behind Apache JMeter.
Table of Contents (17 chapters)
Title Page
About the Author
About the Reviewers
Customer Feedback

Chapter 4. Managing Sessions


In this chapter, we'll cover session management in JMeter in detail. Web applications, by their very nature, use client and server sessions. Both work in harmony to give each user a distinct enclosure to maintain a series of communications with the server without affecting other users. For example, in Chapter 2, Recording Your First Test, the server session was created the moment a user logged in to the application, and was maintained for all requests sent to the server by that user until he/she logged off or timed out. This is what protects users from seeing each other's information. Depending on the application's architecture, the session may be maintained through cookies (most commonly used) or URL rewriting (less commonly used). The former maintains the session by sending a cookie in the HTTP headers of each request, while the latter rewrites the URLs to append the session ID. The main difference is that the former relies on a client's browser choosing to...