Strange null error
We keep getting a strange "null" error on random areas of our site when we try to submit changes. The exact message is "An error occurred during editing: null". Have you seen this before?
- pdf-error.zip 1.43 MB
Showing page 2 out of 2. View the first page
Discussions are closed to public comments.
If you need help with Cascade CMS please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
31 Posted by crcampbel on 16 Feb, 2012 08:51 PM
redirect-jan-2012 is the only file we seem to be experiencing this with error. I went back through the versions and discovered that as of Jan 27 at 9:16am that this file started to throw the "null" error. Before this point the file was working fine, and only contained 167 redirects. At first I thought it may have been some bad data that was causing the problem. I made a comparison between the version that didn't throw an error and the one that did and determined that the only difference was one extra redirect. I thought if I deleted it then the redirect-jan-2012 file should start to work properly again. This didn't happen. I then noticed that every time I attempted to create more than 169 redirects the file starts to throw the "null" error on a consistent basis, and continued to do so even if I started to eliminate redirects from it (actually tested it so that there was only one redirect in the file). Any idea why this would happens?
32 Posted by Bradley Wagner on 16 Feb, 2012 08:59 PM
Thanks for the research. That definitely helps.
So both the current version of the page (what's currently stored as the most recent version) and the version including the edits you've made have to have fewer than 169 redirects in order to successfully edit the page. Is that accurate?
In other words, you would need to revert to a version of the file with fewer than 169 redirects and then make an edit to get it to work successfully.
33 Posted by Bradley Wagner on 16 Feb, 2012 09:25 PM
I believe this issue is related to CSI-71. It looks like you roll these redirect pages over every month based on the page name
redirect-jan-2012
. Is that correct?If so, I think you may be able to work around this issue by changing a Java parameter to tweak the stack size.
Are you using a 32-bit or 64-bit JVM? If, 32-bit please use these directions to set the
-Xss1M
param. If 64-bit try bumping it to-Xss1536k
.This should correct the issue for that page. However, if you were going to continue to add redirects to a single page indefinitely, you will undoubtedly hit a limit again in the future.
Please let me know how you would like to proceed or if I can further explain any of this.
34 Posted by ccc on 27 Feb, 2012 11:49 PM
we're running into this issue as well. I do have one question for crcampbel: did you recently change the metadata definition xml? added, removed, or modified a field? in my case, i had an existing datadef being used by a page with several hundred multiples of a group of items. i added an additional field to the datadef just before this error began appearing....
35 Posted by Bradley Wagner on 28 Feb, 2012 06:22 PM
ccc,
Can you provide any additional information about the page where you're experiencing this issue? Specifically how many data definition fields in total on the affected page? Does temporarily reverting to a version with far fewer fields and editing that version correct the problem?
Would be you willing to make the above change to your environment and see if it corrects the problem?
Thanks!
36 Posted by crcampbel on 28 Feb, 2012 06:55 PM
Hi ccc,
It turned out that there was a limit to a set number of "data blocks" in the asset we created for our redirects. When I reached 170 redirects our page would throw a null error. If I tried to remove a redirect to go below the 170 mark I would continue to get the error. If I went back to an older version of this file that had less that 170 entries it worked again.
Craig
37 Posted by Ryan Griffith on 21 Jun, 2012 06:36 PM
Hi ccc,
I was going over some older discussions and noticed this one is still open. Were you able to determine the cause of the cause of the error message? Are you still experiencing this behavior?
Please feel free to let us know if you have any other questions.
Thanks.
Ryan Griffith closed this discussion on 02 Jul, 2012 01:11 PM.