Failed to initialize the application "SB_JMS_Proxy_N7de264e1.N2efb99d.2.1553951a327.N7ffe" due to error weblogic.management.DeploymentException: Exception occured while downloading files

Hello Viewer,

Today i faced one issue while bringing up the OSB servers.Servers were not coming up. After reaching to Admin state it again went to force shutting down mode.

After seeing the logs i got the below error:

 <Error> <Deployer> <BEA-149205> <Failed to initialize the application "SB_JMS_Proxy_N7de264e1.N2efb99d.2.1553951a327.N7ffe" due to error weblogic.management.DeploymentException: Exception occured while downloading files
weblogic.management.DeploymentException: Exception occured while downloading files
        at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:50)
        at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:59)
        at w
        Truncated. see log file for complete stacktrace
Caused By: java.io.IOException: [DeploymentService:290066]Error occurred while downloading files from Administration Server for deployment request "0". Underlying error is: "null"


Solution: Login to Admin console and goto deployments, search the ear for which you are facing the error, it should be in failed state.
It will not allow you to untarget this ear.just delete it from deployments and try to restart the server. This time servers should come up.

Thanks a lot for your patience!!!

Regards
-Ashish

Email Notification from ORACLE MFT 12C(12.1.3.0.2)

Hello Viewer,

For an efficient support it is always a smart choice to make the work easier and productive.Oracle has provided new tool ORACLE MFT to manage the file transfers. But in case of any failed transfer , our system should be well equipped with the method which can give us an alert rather than keep on monitoring the console and wasting most of the time in sitting ideal like zombie.  

ORACLE MFT has a build in feature of email notification for different kind of events.In this blog i  will provide you the steps to enable notification for few of the events.

This is two step process:

1) configure the email driver configuration.

2) Enabling event , creating contact and associating this contact with event.

Step(1) 

             1) Goto EM console

             2) Expand User Messaging Service.

             3) Click on usermessagingdriver-email (mft_server1)> click on Email Driver properties from                    drop down list.

             4) click on create and provide the details:

                  essential field that you should know is :>

                  a) Outgoing Mail Server, Outgoing Mail Server port

                  b) Default sender Address

                  c) Outgoing Username and password(Make sure this user should be there in your security                        realm)

             5) After providing all the values click on OK  and logout. Login again and see the updated                      values should be there.

Steps(2) 

          

               1) Login to you MFT machine(node) on which you have installed it.

               2) run the ./wlst.sh

               3) connect to your MFT server using connect() wlst command and execute the below wlst                        commands.

              a)  connect('username','password',t3://Adminhost:MFTserverPORT)

              b)  updateEvent('RUNTIME_ERROR_EVENT', true)

              c)   createContact('Email', 'ABD@host.com') 

              d)   addContactToNotification('RUNTIME_ERROR_EVENT', 'Email',            'ABD@host.com') 

Note: Here i have given example taking one of the event there are many other as well.

1) RUNTIME_ERROR_EVENT

               This event tracks the errors occurred at runtime. For example:

                               • Any errors that occur during the message processing 

                               • Server start errors 

                               • System event failure errors

2) DEPLOY_ARTIFACT_EVENT

This event tracks the artifact deployment events.

etc...

Restart the managed server and replicate any error scenario in MFT transfers and check if you are receiving email on email id: ABD@host.com

Thanks a lot for your patience!!!

Regards
-Ashish

 [12.2.1.0.0] Failed to start the BAM Alert Engine

Hello Viewers,

I was trying to configure the BAM Alerts with Email Notification feature. I created the BAM alerts in BAM composer and configured the BAM properties and user messaging driver.


while deactivating the alert I was getting the pop up saying "unable to deactivate the alert" but actually it gets deactivate. same behavior when i was trying to activate it.
When i was trying to save the alert it is "showing unable to load the alert"

In logs i was getting the below error:

-------------------------------------------------------------------------------------------------------------------------------------------------------------
<Apr 3, 2016 1:54:44 AM EDT> <Warning> <oracle.beam.server> <BEA-000000> <BAM Alerts Engine Service failed to start. 
Exception: java.lang.StringIndexOutOfBoundsException: String index out of range: 4 
at java.lang.String.substring(String.java:1963) 
-------------------------------------------------------------------------------------------------------------------------------------------------------------

Applied all the mandatory patches for BAM and restarted the server after clearing tmp, cache and data folder but still got the same issue.

Solution :

1) Go to EM -> Navigate to Business Activity Monitoring -> BAMServer -> BAM Properties
2) Click on "More Advanced configuration
3) Search for ScheduledDataPurgeTimeForDataObject property, change its value from 1:0:0 to 01:00:00
4) Save your changes.
5) Restart the environment.

Thanks a lot for your patience!!!

Regards
-Ashish

Oracle Coherence GE 12.2.1.0.0 <D5> (thread=ReplicatedCache:SOAReplicatedCache, member=15): Member 13 joined Service SOAReplicatedCache with senior member 15> 

Hello Viewer,

I have 2 unix box on which  two TEST environment were built with SOA and OSB domain for each.

Taking reference of only SOA domain :

SOA_TEST1_DOMAIN:

Admin server(Machine1)

BAM server1(Machine1)

BAM server2(Machine2)

SOA_server1(Machine1)

SOA server2(Machine2)

SOA_CLUSTER: SOA_server1, SOA server2

BAM_CLUSTER: BAM server1,BAM server2

SOA_TEST2_DOMAIN:

Admin server(Machine1)

BAM server1(Machine1)

BAM server2(Machine2)

SOA_server1(Machine1)

SOA server2(Machine2)

SOA_CLUSTER: SOA_server1, SOA server2

BAM_CLUSTER: BAM server1,BAM server2

Note: cluster name in both the domain is same i.e SOA_CLUSTER and BAM_CLUSTER.

Issue:

===

--Whenever i was trying to deploy a service in TEST2 environment, I see errors in the TEST1 Env and the deployment hangs and/or timeouts with errors..

--When I shutdown TEST2 Env, than the Deployment goes through fine.

-- After bringing up the TEST2 environment again , already deployed composite becomes inaccessible in TEST1

Error in logs:

<Trace> <com.oracle.coherence> <soaXXXX.cos.XXXX.com> <soa_server1> <Logger@9215997 12.2.1.0.0> <<anonymous>> <> <a3379798-6804-442d-a3de-4a5576fc5975-00000004> <1458800884649> <[severity-value: 256] [rid: 0:6] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <[com.tangosol.coherence.component.util.logOutput.Jdk:log] 2016-03-24 02:28:04.649/212.173 Oracle Coherence GE 12.2.1.0.0 <D5> (thread=ReplicatedCache:SOAReplicatedCache, member=15): Member 13 joined Service SOAReplicatedCache with senior member 15>

After going through all the possible cause , we ended up on coherence factor.Actually whenever i was trying to bring up the servers in TEST2 environment , servers were getting registered as a member of already running SOA_CLUSTER i.e cluster of TEST1.

we tried to add the coherence parameter with different port in both the domains but still issue was occurring.

In 12c , while creating a domain we get a wizard to configure coherence cluster, by default weblogic provides us the coherence cluster named as defaultCoherenceCluster with all the Weblogic cluster(SOA_CLUSTER and BAM_CLUSTER) of the domain in its member list.

While creating the domain we accepted all the default setting for defaultCoherenceCluster, also name of the cluster in both the domain was same, so it seems it was not able to differentiate between weblogic clusters in both the domain and hence all the running servers were getting registered under only one cluster name SOA_CLUSTER.

Solution: 

we removed the SOA_CLUSTER and BAM_CLUSTER from the member list of defaultCoherenceCluster in one of the domain.

Alternatively other solution could be to create 2nd domain with different cluster name.

Although i am not sure if configuring defaultCoherenceCluster is mandatory or not :) 

since it resolved the issue for me , we accepted this solution.

Thanks a lot for your patience!!!

Regards
-Ashish