tomcat提供的xfire接口,访问报错javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1] Message: JAX

服务商作好的服务,使用tomcat提供的webservice服务,咱们去访问时过段时间就会报错。html

这是我把后台日志报错信息,粘贴保存为一个html后打开的效果。java

以前那个200000是37000,常常报错,而后同时调整为了200000,撑的时间长一点,出现异常时就重启一下。git

服务商说是咱们访问时没有断开链接,我检查了咱们本地代码,没什么问题,百度了xfire的访问,也没说要断开链接的。github

这是stackover上一个比较类似的错误   https://stackoverflow.com/questions/20482331/whats-causing-these-parseerror-exceptions-when-reading-off-an-aws-sqs-queue-inweb

翻译:apache

在个人风暴集群中读取AWS SQS队列时,是什么致使了这些ParseError异常?ubuntu

  我正在使用Storm0.8.1从AmazonSQS队列中读取传入消息,并在执行此操做时得到一致的异常:tomcat

2013-12-02 02:21:38 executor [ERROR] 
java.lang.RuntimeException: com.amazonaws.AmazonClientException: Unable to unmarshall response (ParseError at [row,col]:[1,1]
Message: JAXP00010001: The parser has encountered more than "64000" entity expansions in this document; this is the limit imposed by the JDK.)
        at REDACTED.spouts.SqsQueueSpout.handleNextTuple(SqsQueueSpout.java:219)
        at REDACTED.spouts.SqsQueueSpout.nextTuple(SqsQueueSpout.java:88)
        at backtype.storm.daemon.executor$fn__3976$fn__4017$fn__4018.invoke(executor.clj:447)
        at backtype.storm.util$async_loop$fn__465.invoke(util.clj:377)
        at clojure.lang.AFn.run(AFn.java:24)
        at java.lang.Thread.run(Thread.java:701)
Caused by: com.amazonaws.AmazonClientException: Unable to unmarshall response (ParseError at [row,col]:[1,1]
Message: JAXP00010001: The parser has encountered more than "64000" entity expansions in this document; this is the limit imposed by the JDK.)
        at com.amazonaws.http.AmazonHttpClient.handleResponse(AmazonHttpClient.java:524)
        at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:298)
        at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:167)
        at com.amazonaws.services.sqs.AmazonSQSClient.invoke(AmazonSQSClient.java:812)
        at com.amazonaws.services.sqs.AmazonSQSClient.receiveMessage(AmazonSQSClient.java:575)
        at REDACTED.spouts.SqsQueueSpout.handleNextTuple(SqsQueueSpout.java:191)
        ... 5 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1]
Message: JAXP00010001: The parser has encountered more than "64000" entity expansions in this document; this is the limit imposed by the JDK.
        at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.setInputSource(XMLStreamReaderImpl.java:219)
        at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.<init>(XMLStreamReaderImpl.java:189)
        at com.sun.xml.internal.stream.XMLInputFactoryImpl.getXMLStreamReaderImpl(XMLInputFactoryImpl.java:277)
        at com.sun.xml.internal.stream.XMLInputFactoryImpl.createXMLStreamReader(XMLInputFactoryImpl.java:129)
        at com.sun.xml.internal.stream.XMLInputFactoryImpl.createXMLEventReader(XMLInputFactoryImpl.java:78)
        at com.amazonaws.http.StaxResponseHandler.handle(StaxResponseHandler.java:85)
        at com.amazonaws.http.StaxResponseHandler.handle(StaxResponseHandler.java:41)
        at com.amazonaws.http.AmazonHttpClient.handleResponse(AmazonHttpClient.java:503)
        ... 10 more

我已经调试了队列中的数据,一切看起来都很好。我不明白API的XML响应为何会致使这些问题。有什么想法吗?oracle

回答:async

  多年来一直在回答我本身的问题。 

  目前在Oracle和OpenJDK的Java中有一个XML扩展限制处理错误,致使共享计数器在解析多个XML文档时会碰到默认上限。 

  https://blogs.oracle.com/joew/entry/jdk_7u45_aws_issue_123

  https://bugs.openjdk.java.net/browse/jdk-8028111

  https://github.com/aws/aws-sdk-java/issues/123

  虽然我认为咱们的版本(6B27-1.12.6-1ubuntu0.12.04.4)没有受到影响,可是运行OpenJDK bug报告中给出的示例代码确实验证了咱们对该bug的敏感性。 

  为了解决这个问题,我须要将jdk.xml.EntityExpansionLimit=0传递给Storm Workers。经过在集群的storm.yaml中添加如下内容,我能够缓解这个问题。 

  supervisor.childopts:“-djdk.xml.entityExpansionLimit=0”

  worker.childopts:“-djdk.xml.entityExpansionLimit=0”

  我应该注意到,从技术上讲,这会使您面临拒绝服务攻击,可是因为咱们的XML文档只来自于SQS,因此我不担忧有人伪造恶意的XML来杀死咱们的工做人员。

 

  可能还有更多。我在使用Java6时也遇到一样的错误。个人机器上没有安装Java7。

  不要介意。发现这也会影响Java五、六、7和8的特定版本。详情请参见:bugs.openjdk.java.net/browse/jdk-8028111–brianc mar 19'14,15:00

  你们好,我只需在程序中添加“system.setproperty”(“jdk.xml.entityExpansionLimit”,“0”)一行就解决了这个问题。奇怪的是,当使用从命令行传递给程序的参数做为参数时,问题仍然存在。

  根据Java文档,将“JDK.XML.EntEngestExpCurimeLim限度”属性设置为“0”并无限制。应使用负值禁用实体扩展。docs.oracle.com/javase/tutorial/jaxp/limits/limits.html

---------------end------------------------

后续,等待与机构商沟通,有解决办法了再更新

相关文章
相关标签/搜索