This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal



Oct 21, 2012, 7:28 PM
3 Posts
topic has been resolvedResolved

Broken link in view

  • Category: Other
  • Platform: Windows
  • Release: 8.5.3
  • Role: Developer,Administrator
  • Tags: noteid documentid view link
  • Replies: 5
I have an xPage with a view (list of companies) , and another xPage used to render document selected from the previous view.
I have documents that open correctly, other documents that fire the dreaded
Error 500 - HTTP Web Server: Command Not Handled Exception

 
The document xpage is VERY simple, it only displays one text field (the company Name).
There is no reason why one document opens and other dont.
 
The only thing I was able to see is that the url for opening documents is built this way:
 
 http://servername/appname.nsf/Company.xsp?action=openDocument&documentId=<NOTEID>
 
and that all the documents that do open correctly have a NoteID higher than 1200 HEX,
while all the documents that do not open (error 500) have a NoteID up to HEX 11FF.
 
 All other views generate links with document unids, this view is different from the others because it is taken from another database.
 Is it the reason why noteids are used instead of documentids?
 
So:
1) Does it all makes  sense? This is so strange I cannot give an explanation, is there anybody who knows?
2) is there any place to go and configure xpages to use document unids instead of noteid?
 
 Cheers
 
Francesco
Oct 22, 2012, 3:33 AM
366 Posts
Re: Broken link in view
 You need to figure out what is throwing the error 500.  Look in log.nsf or look in the console.log file or xpages exec error log in the IBM Technical Support folder on the client or server where you are executing the XPage.
 
There should be a stack trace.  That will tell you why the document will not load. 
 
You can also enable the "Display XPage Runtime Error instead" in the application properties to display the stack trace if there is one. 
 
If you're not sure what the error output is telling you then post that content here. 
Oct 22, 2012, 3:06 PM
3 Posts
Re: Broken link in view
Paul,
 
here I paste the content of the stack trace. 
The same thing is written in xpages_exec_..... file.
 
I cannot tell anything from this 102 lines long error message;
it is a sequence of internal calls, nothing seems to point to my code. 
 
The only thing I see is a generic java.lang.NullPointerException
thrown somwhere in the middle of these calls. 
 
Now i try to investigate which differences (if any) there are among the documents with noteIDs lower than HEX 1200 and the other documents; 
BTW, I built a view sorted by NoteID and I can confirm that all the documents with noteID lower than 1200 throw the error, while all the other document are opened correctly.
 
com.ibm.xsp.FacesExceptionEx: Could not open the document
com.ibm.xsp.model.domino.DominoDocumentData.doOpenDocument(DominoDocumentData.java:505)
com.ibm.xsp.model.AbstractDocumentDataSource.openDocument(AbstractDocumentDataSource.java:148)
com.ibm.xsp.model.AbstractDocumentDataSource.load(AbstractDocumentDataSource.java:100)
com.ibm.xsp.model.AbstractDataSource.getDataContainer(AbstractDataSource.java:474)
com.ibm.xsp.model.domino.DominoDocumentData.getDataObject(DominoDocumentData.java:146)
com.ibm.xsp.model.AbstractDataSource.pushData(AbstractDataSource.java:576)
com.ibm.xsp.util.DataPublisher.publishControlData(DataPublisher.java:181)
com.ibm.xsp.component.UIDataPanelBase.publishControlData(UIDataPanelBase.java:310)
com.ibm.xsp.component.UIDataPanelBase.initBeforeContents(UIDataPanelBase.java:451)
com.ibm.xsp.component.UIIncludeComposite.initBeforePageContents(UIIncludeComposite.java:668)
com.ibm.xsp.page.compiled.AbstractCompiledPage.initComponent(AbstractCompiledPage.java:325)
com.ibm.xsp.page.compiled.AbstractCompiledPage.createTree(AbstractCompiledPage.java:256)
com.ibm.xsp.page.compiled.AbstractCompiledPage.addComponent(AbstractCompiledPage.java:389)
com.ibm.xsp.component.UIIncludeComposite.buildContents(UIIncludeComposite.java:453)
com.ibm.xsp.page.compiled.AbstractCompiledPage.initComponent(AbstractCompiledPage.java:334)
com.ibm.xsp.page.compiled.CompiledComponentBuilder.buildChildren(CompiledComponentBuilder.java:123)
com.ibm.xsp.page.compiled.CompiledComponentBuilder.buildAll(CompiledComponentBuilder.java:84)
com.ibm.xsp.component.UIOutputEx.buildContents(UIOutputEx.java:92)
com.ibm.xsp.page.compiled.AbstractCompiledPage.initComponent(AbstractCompiledPage.java:334)
com.ibm.xsp.page.compiled.CompiledComponentBuilder.buildChildren(CompiledComponentBuilder.java:123)
com.ibm.xsp.page.compiled.CompiledComponentBuilder.buildAll(CompiledComponentBuilder.java:84)
com.ibm.xsp.component.UIOutputEx.buildContents(UIOutputEx.java:92)
com.ibm.xsp.page.compiled.AbstractCompiledPage.initComponent(AbstractCompiledPage.java:334)
com.ibm.xsp.page.compiled.CompiledComponentBuilder.buildChildren(CompiledComponentBuilder.java:123)
com.ibm.xsp.page.compiled.CompiledComponentBuilder.buildAll(CompiledComponentBuilder.java:84)
com.ibm.xsp.component.UIViewRootEx.buildContents(UIViewRootEx.java:1649)
com.ibm.xsp.component.UIViewRootEx2.buildContents(UIViewRootEx2.java:246)
com.ibm.xsp.page.compiled.AbstractCompiledPage.initComponent(AbstractCompiledPage.java:334)
com.ibm.xsp.page.compiled.AbstractCompiledPage.createTree(AbstractCompiledPage.java:256)
com.ibm.xsp.page.compiled.AbstractCompiledPage.createViewRoot(AbstractCompiledPage.java:167)
com.ibm.xsp.application.ViewHandlerExImpl._createViewRoot(ViewHandlerExImpl.java:511)
com.ibm.xsp.application.ViewHandlerExImpl.createViewRoot(ViewHandlerExImpl.java:557)
com.ibm.xsp.application.ViewHandlerExImpl.doCreateView(ViewHandlerExImpl.java:141)
com.ibm.xsp.application.ViewHandlerEx.createView(ViewHandlerEx.java:90)
com.ibm.xsp.webapp.FacesServlet.serviceView(FacesServlet.java:238)
com.ibm.xsp.webapp.FacesServletEx.serviceView(FacesServletEx.java:200)
com.ibm.xsp.webapp.FacesServlet.service(FacesServlet.java:160)
com.ibm.xsp.webapp.FacesServletEx.service(FacesServletEx.java:137)
com.ibm.xsp.webapp.DesignerFacesServlet.service(DesignerFacesServlet.java:103)
com.ibm.designer.runtime.domino.adapter.ComponentModule.invokeServlet(ComponentModule.java:576)
com.ibm.domino.xsp.module.nsf.NSFComponentModule.invokeServlet(NSFComponentModule.java:1267)
com.ibm.designer.runtime.domino.adapter.ComponentModule$AdapterInvoker.invokeServlet(ComponentModule.java:847)
com.ibm.designer.runtime.domino.adapter.ComponentModule$ServletInvoker.doService(ComponentModule.java:796)
com.ibm.designer.runtime.domino.adapter.ComponentModule.doService(ComponentModule.java:565)
com.ibm.domino.xsp.module.nsf.NSFComponentModule.doService(NSFComponentModule.java:1251)
com.ibm.domino.xsp.module.nsf.NSFService.doServiceInternal(NSFService.java:598)
com.ibm.domino.xsp.module.nsf.NSFService.doService(NSFService.java:421)
com.ibm.designer.runtime.domino.adapter.LCDEnvironment.doService(LCDEnvironment.java:341)
com.ibm.designer.runtime.domino.adapter.LCDEnvironment.service(LCDEnvironment.java:297)
com.ibm.domino.xsp.bridge.http.engine.XspCmdManager.service(XspCmdManager.java:272)
java.lang.NullPointerException
com.ibm.xsp.model.domino.DominoDocumentData.doOpenDocument(DominoDocumentData.java:500)
com.ibm.xsp.model.AbstractDocumentDataSource.openDocument(AbstractDocumentDataSource.java:148)
com.ibm.xsp.model.AbstractDocumentDataSource.load(AbstractDocumentDataSource.java:100)
com.ibm.xsp.model.AbstractDataSource.getDataContainer(AbstractDataSource.java:474)
com.ibm.xsp.model.domino.DominoDocumentData.getDataObject(DominoDocumentData.java:146)
com.ibm.xsp.model.AbstractDataSource.pushData(AbstractDataSource.java:576)
com.ibm.xsp.util.DataPublisher.publishControlData(DataPublisher.java:181)
com.ibm.xsp.component.UIDataPanelBase.publishControlData(UIDataPanelBase.java:310)
com.ibm.xsp.component.UIDataPanelBase.initBeforeContents(UIDataPanelBase.java:451)
com.ibm.xsp.component.UIIncludeComposite.initBeforePageContents(UIIncludeComposite.java:668)
com.ibm.xsp.page.compiled.AbstractCompiledPage.initComponent(AbstractCompiledPage.java:325)
com.ibm.xsp.page.compiled.AbstractCompiledPage.createTree(AbstractCompiledPage.java:256)
com.ibm.xsp.page.compiled.AbstractCompiledPage.addComponent(AbstractCompiledPage.java:389)
com.ibm.xsp.component.UIIncludeComposite.buildContents(UIIncludeComposite.java:453)
com.ibm.xsp.page.compiled.AbstractCompiledPage.initComponent(AbstractCompiledPage.java:334)
com.ibm.xsp.page.compiled.CompiledComponentBuilder.buildChildren(CompiledComponentBuilder.java:123)
com.ibm.xsp.page.compiled.CompiledComponentBuilder.buildAll(CompiledComponentBuilder.java:84)
com.ibm.xsp.component.UIOutputEx.buildContents(UIOutputEx.java:92)
com.ibm.xsp.page.compiled.AbstractCompiledPage.initComponent(AbstractCompiledPage.java:334)
com.ibm.xsp.page.compiled.CompiledComponentBuilder.buildChildren(CompiledComponentBuilder.java:123)
com.ibm.xsp.page.compiled.CompiledComponentBuilder.buildAll(CompiledComponentBuilder.java:84)
com.ibm.xsp.component.UIOutputEx.buildContents(UIOutputEx.java:92)
com.ibm.xsp.page.compiled.AbstractCompiledPage.initComponent(AbstractCompiledPage.java:334)
com.ibm.xsp.page.compiled.CompiledComponentBuilder.buildChildren(CompiledComponentBuilder.java:123)
com.ibm.xsp.page.compiled.CompiledComponentBuilder.buildAll(CompiledComponentBuilder.java:84)
com.ibm.xsp.component.UIViewRootEx.buildContents(UIViewRootEx.java:1649)
com.ibm.xsp.component.UIViewRootEx2.buildContents(UIViewRootEx2.java:246)
com.ibm.xsp.page.compiled.AbstractCompiledPage.initComponent(AbstractCompiledPage.java:334)
com.ibm.xsp.page.compiled.AbstractCompiledPage.createTree(AbstractCompiledPage.java:256)
com.ibm.xsp.page.compiled.AbstractCompiledPage.createViewRoot(AbstractCompiledPage.java:167)
com.ibm.xsp.application.ViewHandlerExImpl._createViewRoot(ViewHandlerExImpl.java:511)
com.ibm.xsp.application.ViewHandlerExImpl.createViewRoot(ViewHandlerExImpl.java:557)
com.ibm.xsp.application.ViewHandlerExImpl.doCreateView(ViewHandlerExImpl.java:141)
com.ibm.xsp.application.ViewHandlerEx.createView(ViewHandlerEx.java:90)
com.ibm.xsp.webapp.FacesServlet.serviceView(FacesServlet.java:238)
com.ibm.xsp.webapp.FacesServletEx.serviceView(FacesServletEx.java:200)
com.ibm.xsp.webapp.FacesServlet.service(FacesServlet.java:160)
com.ibm.xsp.webapp.FacesServletEx.service(FacesServletEx.java:137)
com.ibm.xsp.webapp.DesignerFacesServlet.service(DesignerFacesServlet.java:103)
com.ibm.designer.runtime.domino.adapter.ComponentModule.invokeServlet(ComponentModule.java:576)
com.ibm.domino.xsp.module.nsf.NSFComponentModule.invokeServlet(NSFComponentModule.java:1267)
com.ibm.designer.runtime.domino.adapter.ComponentModule$AdapterInvoker.invokeServlet(ComponentModule.java:847)
com.ibm.designer.runtime.domino.adapter.ComponentModule$ServletInvoker.doService(ComponentModule.java:796)
com.ibm.designer.runtime.domino.adapter.ComponentModule.doService(ComponentModule.java:565)
com.ibm.domino.xsp.module.nsf.NSFComponentModule.doService(NSFComponentModule.java:1251)
com.ibm.domino.xsp.module.nsf.NSFService.doServiceInternal(NSFService.java:598)
com.ibm.domino.xsp.module.nsf.NSFService.doService(NSFService.java:421)
com.ibm.designer.runtime.domino.adapter.LCDEnvironment.doService(LCDEnvironment.java:341)
com.ibm.designer.runtime.domino.adapter.LCDEnvironment.service(LCDEnvironment.java:297)
com.ibm.domino.xsp.bridge.http.engine.XspCmdManager.service(XspCmdManager.java:272)

Oct 22, 2012, 3:49 PM
135 Posts
Re: Broken link in view
As a workaround you could build the link in the view column and make it use UnID.
 
- Panu 
Oct 22, 2012, 4:22 PM
366 Posts
Re: Broken link in view
 I was hoping there would be a "Caused by..." in the stack trace that pointed to the issue.  Null Pointer could be just about anything.
 
How were the documents that do not open created?  Through the client?  Through code? 
 
Can you open those documents from the notes client?  Re-save them? 
 
Run Updall / Fixup on a copy of the application and see if that helps as well. 
 
 
Oct 23, 2012, 8:59 AM
3 Posts
RESOLVED Re: Broken link in view
The problem was in the target xpage, and it is anyway very strange.
 
The target xpage had two custom controls,
one control with one single computed field
the other control with just plain text.
 
Looking at the source of the second custom control I found that (maybe due to a cut&paste)
there was a definition of a data source that did not relate to anything.
 
<?xml version="1.0" encoding="UTF-8"?>
<xp:view xmlns:xp="http://www.ibm.com/xsp/core">
    <xp:this.data>
        <xp:dominoDocument var="document1" action="openDocument"
            formName=".Scheda">
        </xp:dominoDocument>
    </xp:this.data>

    <div id="lotusContent">
        <h2>Contacts list</h2>
     </div>
</xp:view>

 
This is wrong, but i would expect that it simply does not work!
It is very strange that for some documents it works and for others it gives an error....
 
By deleting the fake <xp:this.data> tag all is working.

This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal