That bug may have been fixed. Did the SQLException result in an exception
getting thrown from ejbLoad?
On Fri, 30 Mar 2001, Tim Yates wrote:
> Solved half of the problem (we think)
>
> One of the editorial staff was going through an MS proxy which was caching
> everything, and reposting information with the same PK
>
> Still don't know why it locked, and didn't just destroy the erroneous Entity
> bean, but at least now, it shouldn't get in that state...
>
> Tim.
>
> ----- Original Message -----
> From: Tim Yates <[EMAIL PROTECTED]>
>
> > Occasionally, when a user is adding an item of content to the system, the
> > server.log file shows the following error:
> >
> > java.sql.SQLException: ORA-00600: internal error code, arguments: [19942],
> > [], [], [], [], [], [], []
> >
> > we then get
> >
> > [Content] LOCKING-WAITING (TRANSACTION) for id TNSContent0000395443
> ctx.hash
> > 2224828 tx:TransactionImpl:XidImpl:[B@471d2b
> >
> > over and over and over, and the website stops responding...
>
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
--
Dan Christopherson (danch)
nVisia Technical Architect (www.nvisia.com)
Opinions expressed are mine and do not neccessarily reflect any
position or opinion of nVISIA.
---------------------------------------------------------------------------
If you're a capitalist and you have the best goods and they're
free, you don't have to proselytize, you just have to wait.
-Eben Moglen
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
