In a quest to figure out why the spurious "closing connection for you,
please close it yourself" INFO error messages that some CMT+SpringTx
applications exhibited in JBoss 3.2.3, developed into the same INFO
message in JBoss 3.2.5, along with an ERROR, I've updated the ejbtest
integration sample. There is now a test for calling into a CMT ejb
which delegates to a SpringTx wrapped POJO, as well, as one which does
this, then delegates to a further SpringTx wrapped POJO which does a
Hibernate transaction.
I haven't gotten so far as duplicating the connection problem, since I'm
getting a situation where Spring is getting a null pointer expression on
trying to close a Hibernate Session. This may be a config error of some
sort. Will keep digging (since the JBoss connection issue has turned
from annoying to dangerous and needs to be pinpointed as either a Spring
or JBoss bug), possibly only in a week or so since this has taken too
much time already. I do however think these real life integration tests
are good for trying to pick up all the obscure stuff we can't unit test,
and people using the lib get only under certain combinations of configs.
Colin
|
