« SOLUTION: When to specify an empty default constructor! | Main | Reclaim your disk space »

UPDATE: "RMIConnection Disconnected" Issue

At a specific project in the US, colleagues of mine faced the "RMIConnection Disconnected" issue. Unfortunately, this wasn't a problem that could be easily solved like in my earlier post on that one.

This one is different as it involves two different OC4J/AS versions (10.1.2 and 10.1.3). It is really a bug and fixed in patch 6114217 for OC4J/AS 10.1.3.[012] and also made it into the 10.1.3.3 one-off patch 6148874.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

About This Entry

This page contains a single entry from the blog posted on July 10, 2007 5:18 PM.

The previous post in this blog was SOLUTION: When to specify an empty default constructor!.

The next post in this blog is Reclaim your disk space.

Many more can be found on the main index page or by looking through the archives.

Top Tags

Powered by
Movable Type and Oracle