Quick update. No definitive progress, but some potential info that may lift the blame from JPA Persister.

I installed SQL 2008 Express locally, and my test case does not crash my DB there.

In addition, our DBA is seeing wierd behavior on our SQL Server since a .NET update was pushed down.

We rolled back the update, and will test against the same server with debugging on Monday.

I'll be looking into Hibernate vs JPA Persistence this weekend.

Thanks!

From: Mauricio Salatino <salaboy@gmail.com>
To: Rules Users List <rules-users@lists.jboss.org>
Sent: Fri, October 16, 2009 8:51:45 AM
Subject: Re: [rules-users] [droolsflow] JPAVariablePersister Crashing SQL Server RPC?

Great to hear that you are using it.
Obviously need some improvements. I will try to help you guys on that.
Would be nice to activate the debugging option of MS SqlServer to see the queries that are being generated. If you have that information please let me know.
Greetings.

2009/10/16 Bill Tarr <javatestcase@yahoo.com>

Hi Mauricio,

I don't actually have a stack trace. Every time I've run the test, it has completed without errors exactly once.

There is nothing in the stack indicating anything bad happened, but immediately after SQL Server is unresponsive to any clients.

As to Hibernate Mappings, you are ahead of me already.

I am currently testing with annotated JPA entities (for Claims and Role) which mirror my real Hibernate mapped entities.

I've haven't found anything absolute on this, but think you CAN'T use Hibernate mappings within JPA.

That means we will need a new Variable Persister, but presumably one similar to the JPA Persister.

I'll be testing more today, as I'll can and let you know if my DBA can get any more info to see if SQL Server is telling us anything useful.

Thanks! And great work on the variable persister, the timing was perfect for us!

Bill