SQL Power Software Forum

Hi there,

I'm tunneling in (and then using a browser bookmark with Mozilla Firefox 3.0.6) to our internal server on my MacOSX 10.4.11. When I tried to log in this morning, I got:

The application has experienced an internal inconsistency. Please contact SQLPower Support.

I tried refreshing the page and actually got in and was able to make changes with no perceptible lag times or other problems.

I tried to log in about an hour and a half after that and was unable to regain access using that trick. Instead, it kicked up:

HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Servlet execution threw an exception
root cause
java.lang.OutOfMemoryError: Java heap space
note The full stack trace of the root cause is available in the Apache Tomcat/6.0.13 logs.

However, when I tried to log in about an hour later using the exact same tunneling/bookmarking approach, I had no problems getting in and was able to use all of the functionality. I am now unable to replicate the error... so I guess this is really just a long-winded fyi!

thanks.

Thanks for this report. From the symptoms you describe, it sounds like you may have discovered a server-side memory retention bug. I believe you're just using the scorecarding feature, is that correct?

The application has experienced an internal inconsistency. Please contact SQLPower Support.

When you see one of these, there's a stack trace available. We'd really appreciate if you could send these to us, especially when the problem is reproducible. If you view the page source (On mac, it's Command-U on Firefox and Option-Command-U on Safari), you will see the stack trace. You might have to scroll down to see it.

-Jonathan

I am just using the scorecarding feature.

Thanks for the information about the stack trace - not being very technical, I thought I had found all of the error coding available. If I have any further problems, I'll be sure to add the stack trace to the report.

thanks!