Hi,
Sorry I broke your app, I was kind of worried when I realized the xa rar
had never been assembled, but noone said "no". Is there some usable or
automatic way to mark in cvs all the changes that go together like the ones
I made?
Can you provide any more details of what's going on? Did you get the
Oracle XA driver to work? Are you using mdb? Is 2pc happening?
One difference between the XADataSourceLoader connection management and the
xa-rar management is that the old way routed all work on one transaction to
the same managed connection, no matter how many beans were in the
transaction. The jca stuff does not do this, whenever you need to do some
work it gets a random connection, calls start (on the XAResource), does the
work, calls end. This for instance breaks the XADataSourceImpl which has a
check that when you call start, and the connection has done work on some
transaction, you need to be supplying that same xid. The last time I
looked I couldn't find the spec saying we can be calling start(xid) with
any xid, but I did find a part saying the tm can call commit on any
xaresource, not necessarily one any work was done on.
I found this problem trying the banktest with the xa-rar using
XADataSourceImpl as the "xa" driver. The problem occurred in
testMultiThread and TestMultiTest2 after some time, but for me pretty
consistently in each run. What happens when you run banktest with your
Oracle driver? Maybe it has a similar problem. Dr. Jung was proposing a
ConnectionManager to provide 2pc but send all work in one transaction to
one ManagedConnection, maybe that would help here too.
If there's any other way I can help let me know.
david jencks
On 2001.08.16 21:01:52 -0400 Jason Dillon wrote:
> It looks like the recent jca & datasource loaders have introduced
> inconsistency in the transaction integrety of the entity system.
>
> I have not yet been able to track this down, but based on an application
> that was working the day before yesterday, which is now non-functional
> after
> more than one run, I would guess that there was a change between now and
> then that has broken something.
>
> I am seeing problems commiting transactions that invole entity beans.
> Where
> a client calls a method, which updates a field, sets a modified flag.
> Sometimes the isModified() method will be called, sometimes it won't.
> There
> are a few different beans getting called in a specific order, but I am
> not
> seeing some of the latter JDBCCommand* logs showing that the database is
> actually getting updated.
>
> My application has not changed and will appear to function with small
> message quantities (1) the first time. After running it again it will
> not
> work, even though the functionality is performed, the database just never
> gets up dated and thus my clients are left in the dark (pooling, waiting
> for
> the dogs...).
>
> I think it would be a really good idea if we could stabale and branch a
> 2.6
> before any other changes are added. 2.5 (or pre-3.0 as it is called) is
> much, much better than 2.4... if we would stop breaking things trying to
> make it even better.
>
> Personally I would like to see this happen... so I could stop chasing
> around bugs that break my app and actually start working on other JBoss
> bits (like documentation of the build system, integration of the
> testsuite
> and other such things).
>
> JBossMQ has come leaps and bounds, so has the locking system. Lets tidy
> up
> what we have then branch and keep going for full RH in 3.0!
>
> It is nice to troll through the code, but I ernestly just want something
> working. I have been playing "chase the bug" for over a month now. It
> is
> getting closer...
>
> If someone knows what is wrong with the tx stuff please let me know. My
> guess is that David might have a clue =P Or I guess I could have broken
> something, but I don't think I did.
>
> =|
>
> --jason
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development