Some 'more, in-depth' information on Oracle BPEL PM, ESB and other SOA, day2day things

Friday, February 24, 2006

The infamous javax.naming.NameNotFound exception

Are you hitting this one too, after deploying a jsp application into the BPEL container, and wonder why it's not working, even as it is the same one that we ship?

The reason for this to happen is the EJB access .. BPEL delivery service is based on an EJB, and as we use lookup, you must ensure, that your application is a child of orabpel.

Where to do this?
in $OC4J_HOME/j2ee/home (or OC4J_BPEL on a midtier install)/server.xml
herein all you applications are defined.

check you application entry, for an attribute named parent, with the value set to orabpel. If it's not there, this is the reason.

3 Comments:

Anonymous Oliv said...

You probably mean $OC4J_HOME/j2ee/home (or OC4J_BPEL on a midtier install)/config/server.xml

9:44 PM

 
Anonymous Anonymous said...

Where should I do this? On the BPEL server, or the Application's server that's going to call BPEL?

8:46 AM

 
Anonymous Anonymous said...

Where should I do this? On the BPEL server, or on the Application's server thats going to call the BPEL process?

8:49 AM

 

Post a Comment

<< Home