Using Safari 5.1.1 on Mac OS X 10.6.8 and Chrome 16.0.912.63 m on Windows 7, receiving an Error after posting:
An error occurred while processing your request.
Refreshing forum page shows post was completed.
Keep Smiling
Same issue as in http://community.logos.com/forums/t/42878.aspx.
Since forum thread is updated, wonder if error message happens when trying to refresh discussion to show reply added ?
Keep Smiling [:)]
I'm not sure of the cause but I've hit the same error several times on Chrome's latest beta build, and at least once on the latest dev build for ChromeOS.
This happens to me too from time to time, and seems to be happening more often of late. The post works. The error is spurious. I'm also using Chrome (browser, not the OS -- on Win 7), but not the beta.
I'm also using Chrome (browser, not the OS -- on Win 7), but not the beta.
For clarification I'm using Chrome Beta on my windows 7 machine & using Chrome Dev on my ChromeOS machine.
It's definitely a server-side problem because it's cross platform, and evidenced above; cross browser.
I should note that nearly EVERY single post is giving me the same error now.
Here's another example for anyone who's trying to figure this out:
Please note an additional problem I see often enough: the edit dialog (quick reply) for no reason expands to full screen height.
Also have seen file attachment expand to full height until javascript completes loading to resize dialog box.
Wondering if Logos web site is feeling bit overwhelmed so dropping some stuff ? (refreshing forum pages seems to take awhile at various times)
The forum is DRIVING ME CRAZY because of this error.
Wondering if Logos web site is feeling bit overwhelmed so dropping some stuff ? (refreshing forum pages seems to take awhile at various times)Now that you mention it, that fits perfectly with the intermittentcy of it.
Make me wonder if some other process (like a live backup or a db optimizer) is interfering with the server availability.
The fact that it does actually post a message whenever the error does occur points to a timeout when talking to the database (i.e., the db got the update request, and processed it, but it took so long to do so, that the web application gave up waiting).
EDIT: this response posted without error, but it took about 15 seconds to do so.
