Wednesday, May 5, 2010

What do do when deploy fails in OC4J App Server

First of all, this post is WORK RELATED, and not intended for friends/family and is completely boring so feel free to hit "mark as read" now.....

I found NO help whatsoever in google for this issue, so I'm hoping that this post might help some other poor soul trying to figure it out.

Trevor tried deploying TomaxCMAdmin in 10gR3 OC4J App Server and kept getting this error:
"Operation failed with error: oracle.oc4j.admin.internal.DeployerException"

I was able to deploy the same war file to my standalone OC4J just fine. I compared settings, deleting the CMADMIN OC4J Instance and recreating it, but nothing worked. Then I asked the hero of the day: Sudhakar Pyndi, and he had an immediate answer. Man I really respect guys who have a photographic memory!

The fix for this error: "Operation failed with error: oracle.oc4j.admin.internal.DeployerException" is in the second page of the deployment in OC4J.

On the "Bind Web Module to Site" option, DO NOT select default-web-site. (I put it that way because that is how it is set in my standalone OC4J which does deploy properly). But in the OC4J App server, this needs to be set to null. Once I did that, it deployed properly and without errors.

Hoping that this helps someone else out there.

1 comment:

KP said...

Hey Gordon,

This post actually helped. Thanks much. by the way, this is Phani :) its a small world, isn't it :)