Jon,
Thanks for the info. I seemed to have 'fixed' my problem as well, although
I'm not sure what I did to fix it. I built a new JBoss from this morning's
CVS, using jdk1.4 (due to that horrible protected instance variable not seen
by subclasses' inner classes bug in jdk 1.3) and now the
I am getting the very same error message in a very similar use case. The only
difference I can see is that all the methods of the offending bean are set to
'Required' rather than 'RequiresNew'. The error occurs when I try to call
the get methods of the bean through a local interface in a
Thanks Justin for sharing the pain. I thought I was alone.
I am very interested to see the source where you have duplicated this issue.
I would like you to also include your ejb-jar.xml sections. If I can find
the exact situation, I may be able to come up with a test case, a work
around,
Jon,
Here is the original forum post that I found that talks about the same error
in a similar case:
http://main.jboss.org/forums/thread.jsp?forum=47thread=11678
they talked about messing with the AutoCommit property of the oracle driver.
I'm not sure if our problems are related to this or
Thanks, Justin, for the quick response. I had hoped that there would be
simularities between the two issues, but I don't see any other than the error
message. I am using PostGre on the same machine as JBoss. I have other code
that does something very simular to yours without issue. I guess
Well Justin, I have solved the issue, although I think this may qualify for a
bug. Basically, it boils down to returning null in a custom finder. I
couldn't find documentation on implementing a custom finder in which a single
record was returned instead of a Collection. The method signiture
I am using JBoss3.0.0RC2 and have a complex process that creates new orders
as they are submitted from the web. On order submission, a credit card is
authorized via SSL. If the credit card is declined then the order is rolled
back, however the credit card information must stay because we
