Spl-d1-soa-sar-2.2.0.3.0.zip -> BulkRequest. Incorrect .jca File Location In Configuration Files.
(Doc ID 2503063.1)
Last updated on SEPTEMBER 30, 2022
Applies to:
Oracle Utilities Smart Grid Gateway - Version 2.2.0.3.0 to 2.3.0.0.0 [Release 2.2 to 2.3] Information in this document applies to any platform.
Symptoms
On : 2.2.0.3.0 version, General Issues ISSUE ------------------- The JMS options in the deployment of the BulkRequest composite fail to take effect. The following error was observed during deployment: [exec] javax.naming.CommunicationException: Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms. [exec] [Login failed for an unknown reason: ^U^C^C^@^B^BP] [Root exception is weblogic.socket.UnrecoverableConnectException: [Login failed for an unknown reason: ^U^C^C^@^B^BP]]
EXPECTED BEHAVIOR ----------------------- Â BulkRequest JMS destinations should be updated correctly
STEPS ----------------------- The issue can be reproduced at will with the following steps: 1. Update Delivered configuration plan xml file with desire JMS destination name. then, 2. Try to deploy delivered MDF->BulkRequest SOA composite by attaching delivered configuration plan xml . 3. Now you will desire JMS destination name is not reflected in SOA composite reference.
BUSINESS IMPACT ----------------------- The issue has the following business impact: Due to this issue, users cannot test SGG-NMS integration which is planned to include in UAT phase. This may delay schedule of UAT exit on 2/8/2019.
Changes
Cause
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
