AIAReadJMSNotificationProcess [1.0] in unknown state in SOA 11g EM Fusion Middleware Console

AIAReadJMSNotificationProcess [1.0] in unknown state in SOA 11g EM Fusion Middleware Console


Are you seeing AIAReadJMSNotificationProcess [1.0] composites in unknown states in your SOA enterprise manager console?


Errors as below:

<Error> <oracle.integration.platform> <SOA-20020> <Deployment of composite "AIAReadJMSNotificationProcess" failed: Error in getting XML input stream: http://soa.localhost.com:port/soa-infra/services/default/AIAErrorTaskAdministrationProcess/AIAErrorTaskAdministrationProcess.wsdl: Connection reset.>
====> CubeEngine load AIAErrorTaskAdministrationProcess/AIAErrorTaskAdministrationProcess took 476 ms

AIAReadJMSNotificationProcess appears in unknown state on SOA cluster nodes

Composite is in Failed state because it may not have got deployed when soa_server has been started. This may be because you have dependencies between your SOA Composites and AIAReadJMSNotificationProcess that has been deployed before AIAErrorTaskAdministrationProcess it depends on. 

For quick fix:

- restart soa_servers but it may happen again because deployment order of SOA Composites cannot be configured

or 

- redeploy AIAReadJMSNotificationProcess composite


For long term fix, follow:

Doc ID 1151973.1 Boot Order Of The Composites Upon Soa Suite Restart


Doc ID 1369101.1 SOA Server With AIA Unable to Look Up WSDL's At Startup

associated with bug: 12979076 - SOA11G MANAGED SERVER WITH AIA FAILS LOOKING UP WSDL AT STARTUP