This content has been marked as final. Show 6 replies
there may be a problem with weblogic server also. can you build a simple hello-world process and deploy that in to serve. if you get the same we can conclude that the problem with weblogic server. otherwise you have to check you process again and find the root cause of the problem.
It seems, there is problem with your soa-infra that is in soa/admin server. It might be not working properly. First make sure it is up and running fine. To make it up bounce the both admin & soa servers once and check.
Basically its not the problem with composites that you have deployed, its the problem with infra/servers. Try with that you will get some benefit.
Looks like you are running into some other problem.
Have you observed the SOA domain log files, you can find the real reasons for the failures there.
Is your database is up and running ? your MDS database.
Then see whether your admin is up and running, how about the managed server ?
If you find any exception in the domain logs, share here.
In my case issue got resolved after I added java.naming.provider.url
Log into EM then select the domain in use and use the following the menu path, WebLogic Domain> Web Services > Platform Policy Configuration
From there, select the Policy Accessor tab., then click Add to add a property.
In the Add Property window, specify the following values:
In the Name field, enter this property: java.naming.provider.url