Today I experienced a very unusual freezing of Orion when running an application that worked just fine prior to changing database servers. I have an application that uses several Entity EJB's and one Stateless Session EJB. The Entity EJB's have all their methods marked as 'Supports' for transactions. The Session EJB has all of its methods marked as 'Required'. There is a public method in the Session EJB which calls another public method in the same EJB partway through the code. Several Entity EJB's are created at this time. The second (nested) method executes fine, and the first method gets to the return line and freezes. I found that one of my list-mapping tables that was involved in the transaction via the second method had an extra field in it that was marked to disallow nulls, which should have caused an exception to be thrown (and it does get thrown if I turn off 'Required' transactions in my session EJB). For some reason tho, the second method executes, and returns normally. Of course, I've fixed my table as it should not have been that way in the first place, but is this a bug in Orion as well? I hope this information helps someone else out there if they encounter this same seemingly unexplainable at first type of a problem. Tom Bruser Web2Go Corporation
