Archive

Archive for February, 2012

‘Broken Pipe’ error in Application Server Logs While Connecting to the Database

February 24, 2012 Leave a comment

I have encountered this problem at several customer sites, where the symptoms are the following:

In the application server logs the following error shows up while attempting a connection to the database:

Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:103)

Read more…

Advertisements

How to Simulate an Exalogic Machine for Training

February 13, 2012 6 comments

In the new “Cloud Computing” era, Oracle is leading it’s private cloud offering with the new complete hardware and software platform for Enterprise applications, Oracle Exalogic. However, even within Oracle it can be quite difficult to gain access to an Exalogic machine, and getting to know the system just by reading the documentation is a daunting task. So this post will walk you through the steps of setting up a simulated Exalogic machine, in a virtual environment, that you can use for training purposes.

After completing these steps, you will have an environment where you will be able to make the same storage, network, operating system and software configurations as on the actual Exalogic machine. Of course, this will not be suitable for production, nor will any benchmarks have any relevance. It’s just something that you can use to get yourself familiarized with the machine. If you are new to the Exalogic machine, I suggest going over the Oracle Exalogic White Paper before continuing with the steps.

So, in order to build the system, you will need:

Read more…

Instrumenting Weblogic Applications with WLDF: Where Does The Application Spend Time?

February 1, 2012 1 comment

The WebLogic Diagnostic Framework is a very powerful tool complementing the WebLogic server that offers virtually unlimited possibilities to monitor, tune and troubleshoot your deployed applications. In this post I will describe how to use WLDF in order to get a better idea on where does an application spend it’s time, broken down by components. This is achieved by using the WLDF application-scoped instrumentation. The main steps for setting it up are:

  1. Enable the Diagnostic Context to track down a request throughout the system;
  2. Enable server-scoped instrumentation;
  3. Enable application-scoped instrumentation;
  4. Define specific Diagnostic Monitors and assign them specific Actions;
  5. Update the application with the new settings;
  6. Access the instrumented application and analyze the collected data;

Let’s get into details with each of these steps…

Read more…