1 Reply Latest reply on Nov 8, 2002 2:02 PM by Adrian Brock

    removing bean lock and it has tx set!

    Andy Post Newbie

      Anybody out there have any idea what causes this? It happens in the middle of a large data load. It's not reproducable (at least as far as on which record it happens). We're running on top of Oracle. Any hints would be appreciated.

      * * * * * * * *

      javax.transaction.TransactionRolledbackException: removing bean lock and it has tx set!Pool 46387; CausedByException is:
      removing bean lock and it has tx set!Pool 46387; nested exception is:
      java.lang.IllegalStateException: removing bean lock and it has tx set!Pool 46387
      at ipanloader.IpanParser.startElement(IpanParser.java:232)
      at org.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:1376)
      at org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLValidator.java:1214)
      at org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanner.java:1806)
      at org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java:1182)
      at org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:381)
      at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1081)
      at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1122)
      at ipanloader.IpanParser.start(IpanParser.java:72)
      at ipanloader.IpanParser.main(IpanParser.java:57)