Hi All,

I am working on Websphere 5.0 Version, Windows 2000 Professional. I
have been able to deploy an EAR on the server. I have two stateless
session
beans and an Entity Bean. I am invoking the first stateless bean and
this bean invokes the second stateless bean and the second inturn
invokes the Entity Bean. I have given the transaction attribute as
"SUPPORTS" for all the beans. I am able to invoke the methods on each
of the bean and the data is also being retrieved from the DB, but
while the data is returned back I get the
"org.omg.CORBA.TRANSACTION_ROLLEDBACK" Exception.

I also came to know with some forum of increasing the transaction
timeout value in the server, I could increase the value, but still in
vain.

I see the following error in the SystemErr.log:
================================================
SystemErr R java.lang.reflect.InvocationTargetException:
javax.transaction.TransactionRolle dbackException: CORBA
TRANSACTION_ROLLEDBACK 0x0 No; nested exception is:
org.omg.CORBA.TRANSACTION_ROLLEDBACK:
javax.transaction.TransactionRolledba ckException: minor code: 0
completed: No

SystemErr R org.omg.CORBA.TRANSACTION_ROLLEDBACK:
javax.transaction.TransactionRolledbackEx ception: minor code: 0
completed: No
SystemErr R at java.lang.reflect.Constructor.newInstance(Native
Method)
SystemErr R at com.ibm.CORBA.iiop.UtilDelegateImpl.copyObjectByPr oxy(UtilDelegateImpl.java:119 7)
SystemErr R at com.ibm.CORBA.iiop.UtilDelegateImpl.copyObject(Uti lDelegateImpl.java:797)
Syste mErr R at javax.rmi.CORBA.Util.copyObject(Util.java:327)


Can any one please let me know what could be the problem.


Regards,

Balaji

Hi, Balaji

Can you tell me if you got an answer to that problem.

I have quite the same :

A session bean, called by a servlet that does a lot of work,
When it returns to the servlet, I get the same message as you.

It looks like a timeout issue to me, since when the amount of work
is low, and the return is quick, everything works fine. It fails
only when there is a lot of work to do, and it takes a long
time to do it.
In all the cases, the session bean finishes its work successfully.

Best regards

Jean-Marc

Hi Jean-Marc,

Could you please let me know what is the exact type of job is done in your session bean. I mean to say, are you doing any work with the DB or just doing some stuff.

I can propose some solutions:

1) If your session bean is doing some DB handling, you might have to put something called a 'Resource Reference' to the DataSource name your are using. This you will have to put to the session bean.

2) If your session bean is not handling DB work, in the servlet, just try calling the session bean within a transaction.

Hope this might solve your problem. But, if possible let me know what is the exact type of job you are handling in the session bean, so that I could solve your problem precisely.


Regards,

Balaji

Hi, Balaji,

thank you for your answer.
Let me introduce my bean a bit more in details.

This is a bean that has to update possibly a lot of
data in the database.
This is done this way :

A first session bean (bean1) collects the list of data to update and
calls a second session bean's method (method2-1) with this list as a
parameter and on the local interface.

The second bean's (bean2) method2-1 has transaction "not supported".
The method2-1 calls bean2's update method (method2-2) for each
update on the local interface.
method2-2 has transaction Required.

The idea is that each update has to be commited separately.

The problem comes when bean2 ends, but from the messages I issue,
I know that even if the servlet gets an exception, method2-1
has finished successfully and so that all the method2-2 have
committed. By the way, the updates in the database have been
controlled and everything is ok.

Thank you for your time.

Best regards

Jean-Marc

Hi Jean-Marc,

So, as per your reply I think I can confirm that while you are updating the data in the DB using the method2, you are invoking the method within a transaction.

If this is not there, please try the same within the transaction.

Also, I can infer that when the method1 is called for getting the data, you have give the transaction attribute as "not-supported". Try invoking this method too within a transaction.

Also, as I had said before, check adding the 'Resource Reference' for you bean.

Regards,

Balaji