Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
1.3.3
-
None
-
ODE 1.3.4 JBI, Fuse 3.4.0.5, ODE database in memory
Description
We've recently migrated from ODE 1.2 JBI to ODE 1.3.4 JBI.
We were unable to migrate earlier due to criticial bugs in JBI packages in 1.3.3 and 1.3.2..
We ran the same performance test against new ODE 1.3.4 and previous ODE 1.2
The same configuration, the same environment, the same test case, only different ODE zip...
For example:
A service which has about 7 invokes bpel activities with ODE 1.3.4 spends on processing 5500 ms
with ODE 1.2 600ms.. The timings spend on these 7 services doesn't change. JBI bus time doesn;t change. Nothing has changed except ODE version.
It happens the same for our all orchestrated services.
The only thing which was changed is ODE version.
I can't provide the test itself (prioprietary) but I can provide configuration.
Our services are only in memory.
ODE database is JBI external and it is Derby in memory.
However the results are shocking. We of course abandon ODE 1.3.4 ans stay with ODE 1.2, but if it is not fixed, we may abandon ODE completely.
Attachments
Attachments
Issue Links
- is broken by
-
ODE-759 Unintended modifications of dateTime values while doing copy
- Resolved