During a refresh design of a database Notes-Domino I have received the following error
Design Refresh Failed, Memory allocation request exceeded 65,000 bytes
I have tried to move all Xpages and all Custom Controls into another database, and then I switched to "Show Eclipse Views - Package Explorer." I have also deleted residual files under Custom Control Folder, and then I have pasted all Custom Controls and all XPages. I have cleaned and I have rebuilded the project, but the problem persists.
Server release 9.0.1 FP3
My Designer release 9.0.1
Related
I am trying to figure out why my global object selection is no longer available when I am using server side javascript. Also my data sources are blank when looking at the side panel on right but the xpage does have a data source assigned. If I removed the data source from the panel and re-add the data source, then my data source shows correctly(with all the fields available).
This just started happening recently. I am running 9.0.1 FP10 SHF380.
Any help would be appreciated.
Kevin
I have installed IBM Notes and Domino Designer 9.0.1 locally for testing purposes. Attemping to open any XPage in a database created from the Teamroom template gives HTTP Web Server: Command Not Handled Exception. This also occurs with a simple XPage containing just the word TEST and nothing else. Previously I had IBM NOtes 8.5.3 installed and opening XPages worked fine. Could this problem be related to the installation?
Make sure that the code is signed by an id with access to run XPages code. Also, install XPages Log File Reader in order to see the detailed error message (which is also available in the XPages log files in the IBM_TECHNICAL_SUPPORT folder on the Domino server)
I am using Name picker provided by extension library. Since I need to retrieve names for active directory instead of names.nsf, I used beanNamePicker to get names from Active Directory. It is working fine, but sometime I am getting the below error. The error goes off if I refresh the database in designer. Any idea on how to avoid this error without refresh?
com.ibm.xsp.FacesExceptionEx: !BeanNamePickerData.Bean0doesnotexist!
!BeanNamePickerData.Bean0doesnotexist!
Domino Version : 8.5.3 UP1.
Where in the NSF is the code for your bean, and which version of DDE 8.5.3 are you using? There were problems with the Java design element in early versions of 8.5.3 which caused this behaviour of making them fall out of the build path. I think they were fixed in FP3.
You can resolve the problem completely by using the latest version of Designer. You can still set the minimum supported release in xsp.properties to 8.5.3 with confidence that you're not accidentally using any new functionality.
Scenario:
User preview xpage for editing in web browser.
Developer replicate a local replica to the server.
User click save button and trigger save action partial/full refresh
In 8.5.2 crash the whole database based on can't find java design classes. In 8.5.3 no error CS/SS accrued but there are no changes applied to the document. Seems like if you replicate the sessionID is overridden. Is there a way to fix/detect it?
Any ideas?
thx
It relates to this effect: Meaning of java.lang.ClassCastException: someClass incompatible with someClass.
Simply said, every design change resets XSP engine. Since 8.5.3 you can control it by property "Refresh entire application when design changes" in XPage properties - turning it off (default since that version) will just "soft reset" XSP engine.
Anyway, you may loose some scoped variables and beans. This concludes to some rules to obey:
Do not allow developers to change design in production during working hours.
Notify users about the problem (onError event for partial refresh) - Tim's comment explains, that you won't get an error from partial refresh after design change, unfortunately. Simple CSJS code pinging app availability and report problem when app does not respond could work, but I don't advise that: we use "keep alive" control from ExtLib, and troubleshooting in domlog.nsf became a nightmare - it is full of pings (almost all the time - many users keep their browsers open overnight).
If data are very important, implement auto save mechanism similar to Google apps.
BTW: This effect is similar to time-outed session - partial refreshes will fail and user need to reload the page (and possibly loose edits).
Server: Domino 8.5.3 / Window 2003 5.2
We have a strange Problem. Since a few days, we cannot apply changes to our XPage application. Even, if we make some few text changes and open the application, the changes are not displayed. We looked into the generated XPage-Java-classes, here we can see, that the changes were applied to these classes.
Also, we tried to create a new Test-XPage, but if we open this xpage, the error "404 item not found" is displayed.
We also tried this http://www-01.ibm.com/support/docview.wss?uid=swg21327454 but it doesn't help....
We have already restarted the http task and the server.
It looks very much like your XPages don't compile anymore. You can check that by opening the Navigator view in the Domino Designer and check webContent/web-inf/classes. Every XPage translates into a Java class and it seems that has stopped. You can try the Project menu option "clean" and you want to right click on the nsf and check the project properties if a builder has been disabled or is missing.
Next stop: reinstall Designer. Since the compilation happens in Designer, that's where you need to look