It is a stable solution. I would rate the stability an eight out of ten.

The tool is stable. I rate the product’s stability an eight and a half out of ten.

I would rate it as highly stable. I would give it a nine out of ten. In terms of stability, we experience very minimal issues with our live applications.

And if any issues arise, Orcale support providers and upgrade solutions help us resolve them promptly.

It is stable enough but rested if it crosses thresholds.

Oracle SOA Suite is a stable solution.

No, we have not faced any major issues.

It is definitely a stable match solution.

Stability-wise, I'd rate Oracle SOA Suite as nine out of ten. Sometimes my company has some problems with stability, but the solution is mostly pretty stable.

It is stable because it's quite an old product from Oracle.

The solution is stable.

We had issues with the early versions but lately the product is performing well.

I rate the tool’s stability a four out of ten. The stability could be improved.

The solution is scalable. I rate it a seven out of ten, and six people currently use the solution in our organization.

Stability is sometimes a challenge.

We've had no issues with stability.

By and large it is a stable product in my experience. There are down sides as well, however. I think handling very high load, the product has to develop some more maturity. For example, the stability becomes problematic when we are processing millions of records at the same time. Putting up more infrastructure can always help.

We faced some issues, particularly in clustered environments.

Oracle SOA Suite is stable.

It has been stable for us, so far.

You need a qualified team to support production environments.

It’s pretty robust and stable.

It runs fine without any huge stability issues. It's when we try to use it with certain packages that we are trying to do around the AIP that we had some issues.

I would say it is and is not a stable solution, not because of a fault in the product, but because we have a combination of legacy systems and also modern ERP systems. The challenge has been with information moving between the interfaces. When you send information, it's a black box. You don't get a confirmation that information has come back, so it's asynchronous, whereas our applications are synchronous. The ongoing challenge is knowing whether your data been sent completely and accurately. We've had to work to build very good reporting at least. The biggest challenge is getting useful information to troubleshoot when something goes wrong.

It is a very stable product.

It's stable enough. It has its problems as with any other Java application. Java, you know, sometimes can go down; JVM crashes; it has stuck threads. So as with any Java applications, it has its fair share of minor issues; but it's getting better.

There were no issues in v11.1.1.7, but in 12c, the very early releases were a bit unstable. However, with Oracle's new release cycles were able to release patches very quickly, and now v12.1.3.x and v12.2.1.x are very stable products.

SOA has been stable through the years, other portions of the suite have had issues when they rolled out. Customer support is very responsive when issues are found and the product is stable.

We've experienced no issues with performance.

Oracle SOA Suite is stable as long as you do the correct installation, with the architecture. It's good and very stable. I have quite a lot of services that run using it.

There have been no issues aside from the local development environment.

It's been stable during the time we've been using it.

I have not encountered many stability issues caused by the product, but sometimes there are issues from poor implementation or maintenance.

It is a stable product. Of course, it's an IT product, so sometimes there's versions that need patches, but the patches are being released regularly. In production, the product is extremely stable. I think sometimes the development tool could have issues, especially with new versions. The first version sometimes needs a patch, but the production environment has always been very stable.

The product is stable if implemented properly.

The platform historically has had stability issues with every new release. The platform moved from 10g to 11g, had around seven releases in 11g, then moved to 12c, with a further five releases in 12c. These issues are then addressed through a lot of patches and patch sets, and that's a problem with the platform. A lot of times it's a combination of a platform and an application which can cause stability issues. We've seen a lot of stability issues with Oracle Server Suite when they release new versions.

Speed/memory consumption on processing of large (XML) documents did have some issues.

Most of the time.

I have encountered the occasional JDeveloper memory leak.

We're using it for a minimum of it's capabilities, so no stability problems. But we have talked to various other people who said that when they deploy more components in SOA Suite, they run into more performance issues and the like. We're afraid to do that, so we're staying with the minimal.

We have encountered no issues with its stability.

We had issues with BAM. We couldn't get it to work. Right now, we are looking for other solutions, as it's clear for us that in 12c BAM is not usable at all.

In the previous versions, we used to get stability issues. It has improved a lot since then.

A new deployment or proper deployment takes a lot of time, planning and researching. Once you get your topology right, then scaling the infrastructure is not a big issue. Again, the documentation needs to be more specific about the things you need to keep in mind when starting with a new deployment.

We've had issues surrounding our B2B and BAM process. There's quite a few issues, but that's speaking from a developer's standpoint and not a DBA's or Technical Lead's.

The product is stable, but we have seen less stability with JDeveloper.

SOA Suite 12c has improved stability considerably. In the past, we had encountered some minor stability issues with WSM. However, in 12c this has been greatly improved and we have not noticed major problems in production. Also, JDeveloper has been improved.

There were no issues with stability.

Parts of it are stable. When they release a new version, it can be unstable. A lot of times we have seen that, even though they claim in the documentation to have implemented or enhanced certain things, when you start actually implementing it, you realize it's not really been done. For each major release – for example, from 10 to 11 or 11 to 12 – there can be some performance and stability issues in the initial phase. But, overall the patches and the releases are pretty stable.

There are some stability issues. On a few occasions, it behaves abnormally and technical support is unable to come up with a proper solution. Just looking at logs and changing config files is not proper debugging.

Also, we have a specific Oracle SOA server that is not very stable even after following their best practices (which are sometimes very hard to follow).
But it's not a bad software, you just need a good admin to run it.

I have found version 12c to be stable.

The stability is good. We've had no issues with instability.

There were regular issues with the stability of SOA Suite, but they were fixed with help from Oracle technical support.

Yes, this product is not that stable.

Overall the platform is stable. We haven't had any issues with instability.

There have been no stability issues.

I think it's quite stable.

Initially, during our first time, we had some problems. Now, we are good.