有没有人看到这个错误

有没有人看到这个错误

本文介绍了有没有人看到这个错误?err.PersistenceServiceResourceProvider.Errorwritingtopersistedcontenttor的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在我的 Domino 服务器 (9.0.1, FP2) 上,我收到以下错误.

On my Domino server (9.0.1, FP2) I am getting the following error.

11/20/2014 01:00:39 PM HTTP JVM:!err.PersistenceServiceResourceProvider.Errorwritingtopersistedcontenttor!.更详细的信息请参考位于 D:/Program Files/IBM/Lotus/Domino/data/domino/workspace/logs

11/20/2014 01:00:39 PM HTTP JVM: !err.PersistenceServiceResourceProvider.Errorwritingtopersistedcontenttor!. For more detailed information, please consult error-log-0.xml located in D:/Program Files/IBM/Lotus/Domino/data/domino/workspace/logs

当我查看 log-0.xml 文件时,我看到如下错误.其他人以前见过这个吗?我在网上搜索,只在 8.5.2 天左右找到了类似的东西.

When I look in the log-0.xml file I see errors like the following. Anyone else ever see this before? I searched the web and only found something similar back around 8.5.2 days.

<CommonBaseEvent creationTime="2014-11-20T16:49:03.506-05:00" globalInstanceId="ELac14b30a000149b8a6bc5c00000ab2" msg="!err.PersistenceServiceResourceProvider.Errorwritingtopersistedcontenttor!" severity="50" version="1.0.1">
    <extendedDataElements name="CommonBaseEventLogRecord:level" type="noValue">
        <children name="CommonBaseEventLogRecord:name" type="string">
            <values>SEVERE</values>
        </children>
    </extendedDataElements>
    <extendedDataElements name="CommonBaseEventLogRecord:sourceClassName" type="string">
        <values>com.ibm.commons.log.AbstractLogMgr</values>
    </extendedDataElements>
    <extendedDataElements name="CommonBaseEventLogRecord:sourceMethodName" type="string">
        <values>log</values>
    </extendedDataElements>
    <extendedDataElements name="CommonBaseEventLogRecord:Exception" type="string">
        <values>java.lang.NullPointerException&#xD;&#xA;&#x9;at com.ibm.xsp.webapp.PersistenceServiceResourceProvider$PersistenceServiceResource.write(PersistenceServiceResourceProvider.java:105)&#xD;&#xA;&#x9;at com.ibm.xsp.webapp.FacesResourceServlet.doGet(FacesResourceServlet.java:110)&#xD;&#xA;&#x9;at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)&#xD;&#xA;&#x9;at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)&#xD;&#xA;&#x9;at com.ibm.xsp.webapp.FacesModuleResourceServlet.service(FacesModuleResourceServlet.java:85)&#xD;&#xA;&#x9;at com.ibm.designer.runtime.domino.adapter.ComponentModule.invokeServlet(ComponentModule.java:576)&#xD;&#xA;&#x9;at com.ibm.domino.xsp.module.nsf.NSFComponentModule.invokeServlet(NSFComponentModule.java:1335)&#xD;&#xA;&#x9;at com.ibm.designer.runtime.domino.adapter.ComponentModule$AdapterInvoker.invokeServlet(ComponentModule.java:853)&#xD;&#xA;&#x9;at com.ibm.designer.runtime.domino.adapter.ComponentModule$ServletInvoker.doService(ComponentModule.java:796)&#xD;&#xA;</values>
        <values>&#x9;at com.ibm.designer.runtime.domino.adapter.ComponentModule.doService(ComponentModule.java:565)&#xD;&#xA;&#x9;at com.ibm.domino.xsp.module.nsf.NSFComponentModule.doService(NSFComponentModule.java:1319)&#xD;&#xA;&#x9;at com.ibm.domino.xsp.module.nsf.NSFService.doServiceInternal(NSFService.java:662)&#xD;&#xA;&#x9;at com.ibm.domino.xsp.module.nsf.NSFService.doService(NSFService.java:482)&#xD;&#xA;&#x9;at com.ibm.designer.runtime.domino.adapter.LCDEnvironment.doService(LCDEnvironment.java:357)&#xD;&#xA;&#x9;at com.ibm.designer.runtime.domino.adapter.LCDEnvironment.service(LCDEnvironment.java:313)&#xD;&#xA;&#x9;at com.ibm.domino.xsp.bridge.http.engine.XspCmdManager.service(XspCmdManager.java:272)&#xD;&#xA;</values>
    </extendedDataElements>
    <sourceComponentId component="Expeditor 6.2" componentIdType="ProductName" instanceId="" location="st2cnmtl01" locationType="Hostname" subComponent="" threadId="2" componentType="http://www.w3.org/2001/XMLSchema-instance"/>
    <situation categoryName="ReportSituation">
        <situationType xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ReportSituation" reasoningScope="INTERNAL" reportCategory="LOG"/>
    </situation>
</CommonBaseEvent>

推荐答案

访问磁盘上的文件时使用持久性提供程序.这可以是持久化的附件(用于 CKEditor)或全局资源,如 JS 库或 CSS 文件(存储在 notesdata/domino/)

The persistence provider is used when files on the disks are accessed. This can be persisteted attachments (for CKEditor) or global resources like JS libraries or CSS files (stored in notesdata/domino/)

在您的情况下,似乎找不到/丢失了资源.请在错误发生之前检查浏览器想要打开的所有 URL(例如,使用 Firebug 等 Firefox 扩展程序来嗅探客户端和服务器之间的流量).URL 应包含 /.ibmxspres/.

In your case, it seems that a resource could not be found / is missed. Please check all URLs (e.g. with a Firefox extension like Firebug to sniff the traffic between client and server) which the browser wants to open before the error occurs. The URL should contain a /.ibmxspres/.

更新:

该错误也可能因 RichText 项目中的附件而发生.当您打开 CK 编辑器时,所有文件都被分离到磁盘中的持久文件夹中,因此 CK 编辑器可以显示它们(或可以下载文件)

The error can also occur because of an attachment in a RichText item. When you open a CK Editor, all files are detached to disk in a persistence folder, so the CK Editor can display them (or the files can be downloaded)

一旦您使用 xsp/.ibmmodres/persistence/ 打开 URL,资源 servlet 将尝试打开 URL 末尾的文件 (/DominoDoc-CD2-Body/_1_14129733906‌ 540-76E.gif)并将其发送回客户端.但是当会话超时或服务器重新启动时,这些持久化文件将从磁盘中丢弃并且不再可用.

As soon you open a URL with xsp/.ibmmodres/persistence/, the resource servlet will try to open the file at the end of the URL (/DominoDoc-CD2-Body/_1_14129733906‌​540-76E.gif) and send it back to the client. But when a session times out, or the server is restarted, these persisted files are discarded from disk and are no longer available.

就您而言,Bing Bot 已抓取您的页面并找到了这样一个持久化文件.现在他想检查这个文件是否仍然存在(现在已经不是这样了).这就是 servlet 抛出错误的原因.

In your case, the Bing Bot has crawled your page and found such an persisted file. And now he wants to check if this file still exists (which is no longer the case). That's why the servlet throws an error.

这篇关于有没有人看到这个错误?err.PersistenceServiceResourceProvider.Errorwritingtopersistedcontenttor的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-20 22:46