Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Oracle SOA Suite 11g Administrator's Handbook

You're reading from   Oracle SOA Suite 11g Administrator's Handbook This book will quickly become your constant companion in achieving the reliability and security you want in your day to day administration of Oracle SOA Suite 11g. Covers both broad concepts and real-world implementation.

Arrow left icon
Product type Paperback
Published in Aug 2012
Publisher Packt
ISBN-13 9781849686082
Length 380 pages
Edition 1st Edition
Arrow right icon
Toc

Table of Contents (16) Chapters Close

Oracle SOA Suite 11g Administrator's Handbook
Credits
About the Authors
Acknowledgement
About the Reviewers
www.PacktPub.com
1. Preface
1. SOA Infrastructure Management: What you Need to Know FREE CHAPTER 2. Management of SOA Composite Applications 3. Monitoring Oracle SOA Suite 11g 4. Tuning Oracle SOA Suite 11g for Optimum Performance 5. Configuring and Administering Oracle SOA Suite 11g 6. Troubleshooting the Oracle SOA Suite 11g Infrastructure 7. Configuring Security Policies for SOA Composites 8. Managing the Metadata Services Repository and Dehydration Store 9. Backup and Recovery

Chapter 6. Troubleshooting the Oracle SOA Suite 11g Infrastructure

It is almost a guarantee that administrators of Oracle SOA Suite 11g will have a need to continuously address issues within the infrastructure. Sometimes developers may report deployment issues in the non-production environments. Other times, the administrator may get an automated alert regarding an infrastructure failure. In many cases, the root causes of these issues are clear. For example, if a composite instance that inserts a record to a database fails with an ORA-12541, that is quite straightforward, as the error indicates that the database listener is unreachable. Simply starting up the listener should resolve this problem.

However, there are many cases where the error thrown requires a deeper level of troubleshooting to resolve. For example, if an SOA managed server crashes or crashes frequently, this is obviously not normal behavior and a root cause needs to be identified. Is it because the JVM ran out of memory?...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime