Just did some more testing here and it appears to do with the transaction manager.  We’re using jbossts-jta-4.9.0.GA.  If I use the default DummyTransactionManager everything “appears” to work.

When I debugged my JUnit test (I’m not sure how to debug your tests) using the DummyTransactionManager I could see the problem still occurs but on line 263 of DummyTransaction.java the exception thrown is consumed.  A log line is generated but that’s it.  I’m not sure how to view a log in your tests but I couldn’t see the message anywhere in the reports.

You said you tested with the attached jbossts-properties.xml so I assume you were using the same or similar transaction manager so I’m not sure why you can’t reproduce this.  I can now reproduce “success” by using the DumyTransactionManager but I don’t think the DummyTransactionManager is handling this properly or making it apparent.

The problem in the code appears to be when removing the value from the index (QueryInterceptor.java 166) a bit of work is passed in and the value is null because it doesn’t exist in the cache.  In BatchedQueueingProcessor (line 148) in the hibernate-search code the following code is run.

           Class<T> entityClass = work.getEntityClass() != null ?

                     work.getEntityClass() :

                     Hibernate.getClass( work.getEntity() );

The entityClass is the class of the value.  The value is null so therefore it runs Hibernate.getClass(work.getEntity()); and then throws a NullPointerException.  This is the exception that the DummyTransaction.java consumes.

Anyhow, this is what I’m seeing.

Bryan

Hmm, I just did this and ... it worked!