Xpages Rich Text Editor Problems

When using the new Rich test control in 8.5.2, I can’t seem to upload images to the xpage so that they can be displayed in-line in the rich text item. On the server, I get errors:

22/09/2010 14:28:02 HTTP JVM: CLFAD0211E: Exception thrown. For more detailed information, please consult error-log-0.xml located in C:/Program Files/IBM/Lotus/Domino/data/domino/workspace/logs

22/09/2010 14:28:02 HTTP JVM: CLFAD0246E: Exception occurred servicing request for: /db.nsf/$$OpenDominoDocument.xsp - HTTP Code: 500. For more detailed information, please consult error-log-0.xml located in C:/Program Files/IBM/Lotus/Domino/data/domino/workspace/logs

22/09/2010 14:28:02 HTTP Web Server: Command Not Handled Exception [/db.nsf/$$OpenDominoDocument.xsp?$$axtarget=view:_id1:inputRichText1&$$viewid=!cnjva7stzh!&command=QuickUpload&type=Images&SessionID=CNJUWXFZCO&CKEditor=view%3A_id1%3AinputRichText1&CKEditorFuncNum=1&langCode=en] Simon Boulton

In the upload control, I get error 500. Server and clients are 8.5.2.

Anyone else having this sort of problem?

Cheers

Subject: Digging a little further . . .

I’ve been able to show that this is a problem that occurs only on a previously saved document. When I create a new document, I can insert a image in the text OK using the CKEditor rich text editor - in fact it’s quite slick. However, when I save the document and re-edit it to add another image, I get the error messages described in the first post. It’s a bit odd that no-one else seems to have reported this problem :slight_smile:

This is pretty important to me - in fact this was the main reason why I was keen to take on board 8.5.2. Handling of rich text items using the CKEditor gives almost as much function as the Notes Client Rich text Editor. If anyone else has problems with this (or, indeed does not have problems) I’d be grateful for feedback.

Subject: Similar problems

We are having similar error messages all over our logs and seem to be related to Xpage CK Editor and File/Image Upload/Download

here is an example:

12/10/2010 10:32:01 HTTP JVM: CLFAD0211E: Exception thrown. For more detailed information, please consult error-log-0.xml located in D:/Lotus/Domino/data/domino/workspace/logs

12/10/2010 10:32:01 HTTP JVM: CLFAD0246E: Exception occurred servicing request for: “name-of-our-page.xsp” - HTTP Code: 500. For more detailed information, please consult error-log-0.xml located in D:/Lotus/Domino/data/domino/workspace/logs

When we consult the log it appears there are “FileUploadRequestWrapper” errors

We think its a 8.5.2 issue as this was working fine when we were in 8.5.1

we’ve basically added this comment in the hope that if more people raise this issue IBM will look into it, as it seems to be a bug in 8.5.2

Subject: My issue fixed

FYI The guys here fixed it for mehttp://xpagesblog.com/xpages-blog/2010/7/15/whats-new-in-852-for-xpages.html

Appears to be a known bug with CkEditor, 8.5.2 & XPages Persistance settings

"We have an existing issue with images submitted via the ckEditor in 852 that we’re seeking to address as soon as possible and get a fix into the first fix pack for 852. So if you’re hitting this it’s recommended that you log a support call for it and reference this bug number (SPR#) PHAN88HEKA. With your help we can get this addressed quicker.

There is a workaround, though this will not be to everyone’s liking as it effects performance.

Go to the Application Properties and on the XPages tab set the ‘Server page persistence’ to either “Keep pages in memory” or “Keep only the current page in memory”. You will need to apply this on an app to app basis"

Subject: Crashing?

Could i ask if this was causing a server crash - as we are getting crashes and each time i print off what was happening before the crash i get

15/10/2010 11:59:57 HTTP JVM: CLFAD0211E: Exception thrown. For more detailed information, please consult error-log-0.xml located in D:/Lotus/Domino/data/domino/workspace/logs

i check the logs and its recoded as SEVERE

just wondered if anyone was getting crashes and if by fixing this CLFAD0211E the crashes stopped?

Subject: CKEditor

No - this doesn’t cause a server crash for me.

Subject: Workaround doesn’t work for me

I’m still getting the same issue even when setting the database properties as suggested & restarting the server. This problem seems to be at the point that the server constructs the URL for the newly added image - I can see the image being uploaded to the server, but then I get the old 500 error. Hopefully FP1 will fix this - this is a major problem for me as I was hoping to start using the CKEditor across many of may apps and will have to delay this.

Subject: Similar Issue

I’m experiencing image issues with the CkEditor too. I can embedd images but when going back via a different session as myself or another user they’ve dissapeared.

This comes up in the log

30/09/2010 11:04:57 HTTP JVM: !err.PersistenceServiceResourceProvider.Errorwritingtopersistedcontenttor!. For more detailed information, please consult error-log-0.xml located in D:/Domino/data/domino/workspace/logs

but I can’t get any clues from the log file…

<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

at com.ibm.xsp.webapp.PersistenceServiceResourceProvider$PersistenceServiceResource.write(PersistenceServiceResourceProvider.java:105)

at com.ibm.xsp.webapp.FacesResourceServlet.doGet(FacesResourceServlet.java:109)

at com.ibm.xsp.webapp.DesignerModuleResourceServlet.doGet(DesignerModuleResourceServlet.java:55)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)

at com.ibm.designer.runtime.domino.adapter.ComponentModule.invokeServlet(ComponentModule.java:538)

at com.ibm.domino.xsp.module.nsf.NSFComponentModule.invokeServlet(NSFComponentModule.java:1140)

at com.ibm.designer.runtime.domino.adapter.ComponentModule$AdapterInvoker.invokeServlet(ComponentModule.java:803)

at com.ibm.designer.runtime.domino.adapter.ComponentModule$ServletInvoker.doService(ComponentModule.java:758)
	<values>

at com.ibm.designer.runtime.domino.adapter.ComponentModule.doService(ComponentModule.java:527)

at com.ibm.domino.xsp.module.nsf.NSFComponentModule.doService(NSFComponentModule.java:1124)

at com.ibm.domino.xsp.module.nsf.NSFService.doServiceInternal(NSFService.java:513)

at com.ibm.domino.xsp.module.nsf.NSFService.doService(NSFService.java:342)

at com.ibm.designer.runtime.domino.adapter.LCDEnvironment.doService(LCDEnvironment.java:304)

at com.ibm.designer.runtime.domino.adapter.LCDEnvironment.service(LCDEnvironment.java:261)

at com.ibm.domino.xsp.bridge.http.engine.XspCmdManager.service(XspCmdManager.java:291)
</extendedDataElements>

<sourceComponentId component="Expeditor 6.2" componentIdType="ProductName" instanceId="" location="oval1" locationType="Hostname" subComponent="" threadId="4" 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>

Is this still a problem for you?

Subject: CKEditor

I’ve not seen the behaviour you see. I’m able to go back into a document with an embedded image and see it fine. I can move the image around and delete it. I just can’t add a new image. Googling the whole net for the error codes on the server doesn’t get any hits, and no-one else seems to have run across this problem . . .

Subject: HTTP 500 CLFAD Issues: Memory Leak?

I had a problem yesterday where a number of XPages databases could not be accessed via the web, but opened fine as XPiNC. It started as an intermittent Error 500 with the two CLFAD error codes you mention, then escalated until nothing in those databases could be accessed via the web, but still in XPiNC. All the pages being accessed were in read mode, none had the CK Editor. Other web-based applications on the server and sone XPages applications could still be accessed.

A restart of HTTP task resolved the problem.

The Error 500 is the same symptom as a memory leakage problem one of our customers had with 8.5.0, solved by a full OS-level restart of the server http://www-01.ibm.com/support/docview.wss?rs=463&context=SSKTMJ&dc=DB560&dc=DB520&uid=swg21370292&loc=en_US&cs=UTF-8&lang=en&rss=ct463lotus. In 8.5.0 the CLFAD errors had no error codes, and didn’t point to the error-0.xml file. I think both are logging improvements since 8.5.0.

I’m going to monitor the problem, to see if it is an intermittent problem, in which case I will open a PMR.

Subject: similar problem

just not possible to open a xpage, errors in log are07-10-2010 13:13:06 HTTP Web Server: Command Not Handled Exception [/ghvo/aanvragen.nsf/login.xsp] Anonymous

07-10-2010 13:13:06 HTTP JVM: CLFAD0211E: Exception thrown. For more detailed information, please consult error-log-0.xml located in /Domino/GHVO/Data/domino/workspace/logs

07-10-2010 13:13:06 HTTP JVM: CLFAD0246E: Exception occurred servicing request for: /ghvo/aanvragen.nsf/login.xsp - HTTP Code: 500. For more detailed information, please consult error-log-0.xml located in /Domino/GHVO/Data/domino/workspace/logs

in error-log

<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.domino.xsp.bridge.http.engine.XspCmdManager</values>

</extendedDataElements>

<extendedDataElements name="CommonBaseEventLogRecord:sourceMethodName" type="string">

	<values>service</values>

</extendedDataElements>

<extendedDataElements name="CommonBaseEventLogRecord:Exception" type="string">

	<values>java.lang.ClassCastException: com.sun.faces.context.FacesContextImpl incompatible with com.ibm.xsp.context.FacesContextEx

at com.ibm.xsp.webapp.FacesServlet.service(FacesServlet.java:136)

at com.ibm.xsp.webapp.FacesServletEx.service(FacesServletEx.java:137)

at com.ibm.xsp.webapp.DesignerFacesServlet.service(DesignerFacesServlet.java:86)

at com.ibm.designer.runtime.domino.adapter.ComponentModule.invokeServlet(ComponentModule.java:538)

at com.ibm.domino.xsp.module.nsf.NSFComponentModule.invokeServlet(NSFComponentModule.java:1140)

at com.ibm.designer.runtime.domino.adapter.ComponentModule$AdapterInvoker.invokeServlet(ComponentModule.java:803)

at com.ibm.designer.runtime.domino.adapter.ComponentModule$ServletInvoker.doService(ComponentModule.java:758)

at com.ibm.designer.runtime.domino.adapter.ComponentModule.doService(ComponentModule.java:527)

at com.ibm.domino.xsp.module.nsf.NSFComponentModule.doService(NSFComponentModule.java:1124</values>

	<values>)

at com.ibm.domino.xsp.module.nsf.NSFService.doServiceInternal(NSFService.java:513)

at com.ibm.domino.xsp.module.nsf.NSFService.doService(NSFService.java:342)

at com.ibm.designer.runtime.domino.adapter.LCDEnvironment.doService(LCDEnvironment.java:304)

at com.ibm.designer.runtime.domino.adapter.LCDEnvironment.service(LCDEnvironment.java:261)

at com.ibm.domino.xsp.bridge.http.engine.XspCmdManager.service(XspCmdManager.java:291)
</extendedDataElements>

<sourceComponentId component="Expeditor 6.2" componentIdType="ProductName" instanceId="" location="AS400DSD" locationType="Hostname" subComponent="" threadId="1" 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>