Book Image

JBoss ESB Beginner's Guide

By : Len DiMaggio, Kevin Conner, Magesh Kumar B, Tom Cunningham
Book Image

JBoss ESB Beginner's Guide

By: Len DiMaggio, Kevin Conner, Magesh Kumar B, Tom Cunningham

Overview of this book

<p>You may often have wondered if there is a better way to integrate disparate applications than error-prone "glue code". JBoss ESB is just that solution as it can help solve common but difficult problems: writing new code that can be re-used and maintained, and integrating together new and old systems. JBoss ESB takes care of routing and processing service requests, leaving you to concentrate on your system's design and development.</p> <p>The JBoss ESB Beginner’s Guide gets you up and running quickly with JBoss ESB to build your own service-based applications, with enhanced communication and organization. You will learn how to create new applications or to integrate combinations of new and legacy applications. Detailed examples get you creating your own services, and deploying and administering them with other JBoss Open Source tools.</p> <p>Through hands-on examples, this book shows you how JBoss ESB enables you to design your system as services that are loosely coupled together by sending and receiving messages. Your services can execute your own custom code, or make use of JBoss ESB’s extensive set of out-of-the-box actions to perform specific tasks. The JBoss ESB Beginner’s Guide shows you the tools you can use to build re-usable and maintainable service-based applications with JBoss ESB, and teaches you by example how to use these tools.</p>
Table of Contents (18 chapters)
JBoss ESB
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Prologue—the need for an ESB
Preface
Index

Registry maintenance and performance


What can happen with a hard crash? As the ESB shuts down, the ESB unregisters endpoint references and services. When the ESB has finally shut down, it will have removed all ESB-related services and endpoints—therefore if you hard crash your server, your service will leave behind dead EPRs—EPRs that represent an endpoint from a previous session, that are no longer available.

One hard crash alone probably won't have much effect, but if you allow your system to hard crash a great deal, you'll continue to accrue dead EPRs. These extra EPRs can have a visible effect on your runtime performance. Your startup times will increase a great deal, the time that it takes to call a service with ServiceInvoker will increase—basically any EPR lookup will become slower and slower.

How can you stop these EPRs slowing down your ESB instance?

  • The first way you can speed things up is with the brute force method. Stop your server, and completely clear your jUDDI database. On...