June 15, 2014

Update: ConfigExport: Out Of Disk Space Fails OSB Build, Too

The failure ‘Application “com.bea.alsb.core.ConfigExport” could not be found in the registry’ can also be due to insufficient disk space on the build partition, and generally any resource shortage.

I have already written about the “ConfigExport cannot be found” problem and how to solve it.

Since then I have encountered the same issue again.

Despite getting an identical error message, the root cause was totally different: a lack of disk space on the build partition.

After some old and large log files were removed, the build completed successfully.

This makes me think that the build application responds the same way to any resource shortage, including lack of disk space, memory, or may be a file handle limitation.

Any time you see that notorious message, first check the resources.

And I hope the Oracle guys provide us with better error reporting in future versions.

Vladimir Dyuzhev, author of GenericParallel

About Me

My name is Vladimir Dyuzhev, and I'm the author of GenericParallel, an OSB proxy service for making parallel calls effortlessly and MockMotor, a powerful mock service.

I'm building SOA enterprise systems for clients large and small for almost 20 years. Most of that time I've been working with BEA (later Oracle) Weblogic platform, including OSB and other SOA systems.

Feel free to contact me if you have a SOA project to design and implement. See my profile on LinkedIn.

I live in Toronto, Ontario, Canada.  canada   Email me at info@genericparallel.com