-
Bug
-
Resolution: Fixed
-
P1
-
1.4.0
-
1.4
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2207321 | 7 | Joe Wang | P2 | Closed | Fixed | b112 |
JDK-2189433 | 6u21 | Abhijit Saha | P3 | Resolved | Fixed | b01 |
JDK-2189434 | 5.0u25 | Abhijit Saha | P3 | Closed | Fixed | b01 |
BPEL-SE in the JavaCAPS 6.2 uses the JAXP 1.4 Transformer Pool for transformations. After the transformation of the payload, there is no mechanism to change the state of the transformer to its original state. The reset() method does not clear all the values.
The TransletOutputHandlerFactory within the Tranformer to hold the reference to the writer which inturn holds the result from the transformation.
Since the data of transformation is held within the Transformer, large message transformation resulted in the growth of the memory consumption.
The TransletOutputHandlerFactory within the Tranformer to hold the reference to the writer which inturn holds the result from the transformation.
Since the data of transformation is held within the Transformer, large message transformation resulted in the growth of the memory consumption.
- backported by
-
JDK-2189433 reset() method in the Transformer does not reset to its original state, causes the memory to grow.
- Resolved
-
JDK-2207321 reset() method in the Transformer does not reset to its original state, causes the memory to grow.
- Closed
-
JDK-2189434 reset() method in the Transformer does not reset to its original state, causes the memory to grow.
- Closed