0 Replies Latest reply on Nov 27, 2002 10:03 AM by Florin Duroiu

    IllegalArgumentException: Attempt to get lock ref with a nul

    Florin Duroiu Newbie

      Hi all,
      I am trying to migrate a project from 2.4.0 to 2.4.10 and I'm getting frustrated by some exception messages when testing the deployment.
      So here's what I have:
      Jboss v. 2.4.10
      Oracle DB 8.1.7

      First, I have configured the DataSource to use my Oracle DB and I got a warning message when first initializing the DataSource and subsequently when testing the application:
      XAConnectionImpl: org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@bbf9e has no current tx!

      Here is the DataSource configuration in jboss.jcml:

      OracleDS
      org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl

      jdbc:oracle:thin:@SERVER:1521:S2
      user
      pwd
      10


      I have searched the forum for this and I have found very little info about this (I am deliberatly using some bean methods with Supported transaction attribute). Although I am getting this message all the time, the DB reads go fine and from all I can tell right now there is no error in reading the DB data.

      My next testing step was to try to write something in my tables using the bean logic. Here another strange thing happened and although the data was saved correctly into the database, I got this exception trace:

      [14:21:39,574,STDERR] java.lang.IllegalArgumentException: Attempt to get lock ref with a null object
      [14:21:39,574,STDERR] at org.jboss.ejb.BeanLockManager.getLock(BeanLockManager.java:55)
      [14:21:39,574,STDERR]
      [14:21:39,594,STDERR] at org.jboss.ejb.plugins.AbstractInstanceCache$1.execute(AbstractInstanceCache.java:517)
      [14:21:39,594,STDERR]
      [14:21:39,594,STDERR] at org.jboss.util.WorkerQueue$QueueLoop.run(WorkerQueue.java:206)
      [14:21:39,594,STDERR]
      [14:21:39,594,STDERR] at java.lang.Thread.run(Unknown Source)

      From what I can tell, this exception shows up after an EEJB ejbStore gets called by the container. As I have mentioned, the data _is_ saved into the database correctly.

      Everything works perfectly fine on 2.4.0. If someone has any idea on what's happening, please let me know.

      Thanks a lot!
      florin