On 10/23/07, David Jencks [EMAIL PROTECTED] wrote:
I would guess that you haven't defined a non-jta-datasource
Yes.
and specified it in the persistence.xml.
No.
My experience, while only with derby, is that openjpa's sequences don't work
without a separate non-transactional datasource.
On 10/23/07, Jacek Laskowski [EMAIL PROTECTED] wrote:
On 10/23/07, David Jencks [EMAIL PROTECTED] wrote:
Hope this helps :-)
Sure! If you'd pointed out what needed to be changed, it'd have been
better, but hints are also of great help :P
Okey, I got it running fine. Thanks Dave. If you
At this point I think everything is working correctly except
transaction logging in the tm, so unless your server crashes during
the commit process you should be getting the effects you want.
For reasons that escape me the openejb3 mdb support wasn't written to
work with our tms recovery
On 10/23/07, David Jencks [EMAIL PROTECTED] wrote:
At this point I think everything is working correctly except
transaction logging in the tm, so unless your server crashes during
the commit process you should be getting the effects you want.
The server works fine despite the ERRORs about tx.
I would guess that you haven't defined a non-jta-datasource and
specified it in the persistence.xml. My experience, while only with
derby, is that openjpa's sequences don't work without a separate non-
transactional datasource.
Hope this helps :-)
david jencks
On Oct 22, 2007, at 3:49 PM,
