Error while re-deploying AIAReadJMSNotificationProcess: "javax.naming.NoInitialContextException" and "java.lang.ClassNotFoundException" (Doc ID 1372882.1)

Last updated on JANUARY 27, 2017

Applies to:

Oracle Application Integration Architecture Foundation Pack - Version 2.3 to 2.5 [Release 2]
Information in this document applies to any platform.

Symptoms

AIA Version 2.3 and Patch 9238236
SOA Suite version 10.1.3.4

Errors are thrown while deploying AIAReadJMSNotificationProcess.

<patch 9238236> was applied on the environment. Before applying the patch AIAReadJMSNotificationProcess was invoked for all error messages but after applying patch it was not getting invoked.Oracle has suggested to undeploy and redeploy this BPEL Process as a fix but we are getting Errors while redeploying the AIAReadJMSNotificationProcess .

There are no new Instances of AIAReadJMSNotificationProcess have been created after applying the patch in spite of many error messages.

Error :-
------------
deployDecisionServices:
    [echo]
    [echo] --------------------------------------------------------------
    [echo] | Deploying decision services for AIAReadJMSNotificationProcess on pokxipsdev05.infoprint.com, port 8888
    [echo] --------------------------------------------------------------
    [echo]
[deployDecisionServices] There are no decision services to deploy


bsrPublish:
[registerBPELWsdl]
java.lang.Exception: Failed to create "ejb/collaxa/system/DomainManagerBean" bean; exception reported is: "javax.naming.NoInitialContextException: Cannot instantiate class:
com.evermind.server.rmi.RMIInitialContextFactory [Root exception is java.lang.ClassNotFoundException:

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms