Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8175663 | 10 | Aleksej Efimov | P2 | Resolved | Fixed | b02 |
During removal of SAAJ dependencies to JDK xml internal apis, there were removed a piece of code, resetting SymbolTable in cached SaxParsers. This may cause heap OOM error. Here is original issue, which induced resetting SymbolTables:
https://java.net/jira/browse/SAAJ-46
Resetting SymbolTables was pushed as temporary fix, until this is resolved:
https://java.net/jira/browse/JAXP-59
I have checked a SAAJ code and didn't found any better solution, than to not cache sax parsers at all. But I am not sure what performance impact it may have on saaj/jaxws.
Aleksej can you check if resetting SymbolTable can be done in SaxParser#reset ?
https://java.net/jira/browse/SAAJ-46
Resetting SymbolTables was pushed as temporary fix, until this is resolved:
https://java.net/jira/browse/JAXP-59
I have checked a SAAJ code and didn't found any better solution, than to not cache sax parsers at all. But I am not sure what performance impact it may have on saaj/jaxws.
Aleksej can you check if resetting SymbolTable can be done in SaxParser#reset ?
- backported by
-
JDK-8175663 Investigate SymbolTable in SAXParser
-
- Resolved
-
- relates to
-
JDK-8174735 Update JAX-WS RI integration to latest version
-
- Closed
-
-
JDK-8176168 Performance drop due to SAXParser SymbolTable reset
-
- Closed
-
-
JDK-8166745 Eliminate SAAJ dependency on JAXP internal API
-
- Resolved
-