Hi Philippe!
It seems I have found the problem with the not rolled
back transaction.
Contrary to the description in the Migration.html document,
it seems that the now deprecated use of java.rmi.RemoteException
is not supported in Jonas. If my method throws RemoteException
no rollback happens, if I throw javax.ejb.EJBException a
rollback happens.
Please can you confirm that my impression is correct that
changing my methods to throw javax.ejb.EJBException
will solve the transaction problem?
Thanks, Max
> Hello Philippe!
>
> Do you have any idea if the transaction problem we
> have with JOnAS 2.0 is our fault or if it is a problem
> with Jonas?
>
> It is essential for us to get this problem solved,
> we need a decision today.
>
> If we do anything wrong, can you give me a hint what
> it could be so we can fix it?
>
> (We solved the problem with the finder method that
> does not find modified data, we us our own cache in
> the sessin bean an therefor we can always use
> findByPrimaryKey() for the BMP beans which always works,
> but we see no way how to solve the rollback problem,
> cause a rollback may be nessecairy for other reasons,
> like bad data we want to import)
>
> I attach you the relevant part of the last message
> once more, so we can be shur to talk about the same
> problem.
>
>
> Thanks, Max
> ----------------------------
>
> Max:
> > > But with Jonas 2.0 we got a still more drastic problem:
> The rollback
> > > we do cause we can not find the modified data does not work
> > any more.
> > > Even if the finder Exception is thrown and the
> transaction should be
> > > rolled back, the modified data is in the Datatbase!!!
>
> Philippe:
> > I cannot understand what you do exactly.
> > Could you explain more ?
> > What bean does what ? Who does the rollback ?
>
>
> We use implicit transaction management (so there is no
> tx.begin() and no
> tx.commit() or tx.rollback())
>
> We start the transaction from the client by calling a method
> in our session Bean which has the following attributs:
> <container-transaction>
> <method>
> <ejb-name>DataImport</ejb-name>
> <method-name>*</method-name>
> </method>
> <trans-attribute>Required</trans-attribute>
> </container-transaction>
>
> The Session Bean calls methods from our CMP Bean which has
> the following attributes:
> <container-transaction>
> <method>
> <ejb-name>Buchungszeile</ejb-name>
> <method-name>*</method-name>
> </method>
> <trans-attribute>Required</trans-attribute>
> </container-transaction>
>
> The Session Bean then calls a finder method that fails
> (the reason for failing is that the finder method looks
> in the database and not in the chached data) and
> throws a find exception.
>
> The client gets the exception, but the transaction is not
> rolled back and the modified data is in the database
> (We use Oracle 7.3 as database)
>
> This did work with Jonas 1.6.1, after getting the finder
> exception, the transaction was rolled back and not modified
> in the database. Now with Jonas 2.0 the transaction seems
> not to be rolled back, the modified data is in the database.
>
> Max:
> > > We can solve the finder method problem by keeping the data we
> > > modify in our own Hashtable, but we can not solve the rollback
> > > problem, so it seems we have to switch back to Jonas 1.6.1.
>
> Philippe:
> > I think it's a bad idea because no modification will be done
> > anymore on jonas 1.6. If you want to get fixes to your problem,
>
> So I hope you can help us with Jonas 2.0
>
> Thanks, Max
> ----
> To unsubscribe, send email to [EMAIL PROTECTED] and
> include in the body of the message "unsubscribe jonas-users".
> For general help, send email to [EMAIL PROTECTED] and
> include in the body of the message "help".
>
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
