posted 18 years ago
Time flows up -- the method on the bottom called the one above it, which called the one above it, etc. The one on the very top is the line that actually threw the exception.
As far as where to look, it's always prudent to assume any problem is in your code, not the application server or database driver (that's not to say the problem always is in your code, but it's a good hypothesis to start with.) First read the error message at the top of the trace, and So find your own code on the stack, and see if that message suggests what your code might be doing wrong.
In this particular case, though, it strikes me that the problem is not your fault, but rather an issue with the driver, the database, the app server, or some combination of the three. It looks like the container-managed persistence mechanism is abusing the database. I'd go ask about this in our WebLogic forum with a subject like "CMP with MS SQL Server?" or some such. You can also try googling for the exact text of the error message in quotes.