geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Smith (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GEODE-135) Building fail with IBM JAVA
Date Wed, 29 Jul 2015 16:52:05 GMT

     [ https://issues.apache.org/jira/browse/GEODE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dan Smith resolved GEODE-135.
-----------------------------
    Resolution: Fixed

Applied pull request.

> Building fail with IBM JAVA 
> ----------------------------
>
>                 Key: GEODE-135
>                 URL: https://issues.apache.org/jira/browse/GEODE-135
>             Project: Geode
>          Issue Type: Bug
>          Components: build, core
>    Affects Versions: 1.0.0-incubating
>         Environment: Redhat Enterprise Linux 6 & 7, SUSE Linux Enterprise Server
11 & 12, IBM J9 VM (build 2.7, JRE 1.7.0 Linux s390x-64)
>            Reporter: Lei Zhang
>            Assignee: Dan Smith
>            Priority: Blocker
>
> During building process, the following error happens when performing integrationTest:
> "While parsing XML, caused by java.io.IOException: Stream closed
>  at com.gemstone.gemfire.internal.cache.xmlcache.CacheXmlParser.parse(CacheXmlParser.java:241)
> ...."
> This error is not observed by using OpenJDK, since the default javax.xml.parsers.SAXParserFactory
is set as com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl. However, with IBM
JAVA, the default SAXParserImpl is alwyas org.apache.xerces.jaxp.SAXParserImpl, and the error
shows while using the IBM Java default SAXParser.
> The essential reason for such a failure lies at line 203 at file "gemfire-core\src\main\java\com\gemstone\internal\cache\xmlcache\CacheXmlParser.java",
where the InputStream is reset after being parsed. However, the InputStream will always be
closed after parsing, thus will not be able to be reset, leading to the error. A temp workaround
is to apply a filter to the InputStream where its close function does nothing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message