Bean-managed stateless session bean can't roll back using JTA

I use weblogic6.1sp2 + jdk131
a stateless session bean must do 2 things:
insert a record to A table and delete another record in A table
this bean has the same structure as the example in
j2eetutorial/examples/src/ejb/teller
I use TxDataSource in weblogic
if delete fail, the roll back is run,but in database,
the insert record is STILL in A table.
any idea?

make sure that your deployment descriptor says "transaction required".
Also, If the insert and delete are two different methods, the client must call these two methods in the same transaction scope.

Similar Messages

Call stateless session bean EJB 2.0 from Webdynpro Java UI

Hello,
Can someone please tell me asto how to call a stateless session bean EJB 2.0 from Webdynpro Java UI?
The NWDS version is 7.0.
Thanks and Regards,
Arya

Hi Aryadipta
Please check this pdfs
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b00917dc-ead4-2910-3ebb-b0a63e49ef10&overridelayout=true
Steps for calling stateless session bean in Webdynpro java
Go to NWDS -> open perspective ->j2ee
select EJB Module Project ->create a project with name
Open the Project -->RC on ejb-jar.xml -> Select new --> EJB
Give name to EJB Bean (First letter should be in capital letters)
select the type of bean as Stateless session bean and give the package name to store that EJB bean.
After that Expand ejb-jar.xml and then select the <projectEJB>
Double click on this on method tab double click you will get business method where we will create the methods for business logic
Double click on projectEJB and then RC on bean tab and write required business logic in bean window as follows(based on requirement we will design a business logic).
After writing the business logic go to project -> rebuild
Till now we have created one EJB jar file
then go to File-->Enterprise Application Project -->create a project (projectEAR)
After creating a project click on next-> here we will have ear projects and then we select specific project required for our application.(here select projectEJB)
After that Calculate EAR project will be available on j2ee explorer.
Right click on <Bean> here
select New->Web Service->give a name to webservice and select Default configuration type as simple SOAP
-->click next -> Finish.
That webservice and related are created in ejb-jar.xml .
Expand the ejb-jar.xml.and double click on < webservice>
RC ProjectEJB -> Build EJB Archive RC on CalculateEAR ->Build applicationarchive.
Expand the projectEAR->RC on CalculateEAR.ear->Deploy to J2EE Engine
Double click on calculateEAR.ear ->Webservice navigator tab ->we eill servers expand the node
select the specific WebService
Here we test the webservice by click on Test and test it.
After that go to Web dynpro perspective ->create one webdynpro Project and one component
RC on model> Select import Web Service model(last)>give model name and package
and select radio button as local file system or URL
Go to WSnavigator->copy the WSDL path and paste it in model WSDL path and click on finish.
from here onwards steps are same as that adaptive RFC model
Hope it helps
Thanks
Tulasi Palnati
Edited by: Tulasi Palnati on Aug 26, 2009 12:15 PM
Edited by: Tulasi Palnati on Aug 26, 2009 12:43 PM

Transaction management in stateless session beans.

Hi all,
I am using EJB 1.1.
I have a statless session bean that has two methods- A and B.
which does not involve any database interaction
like inserting/updating/deleting the data in the database.
The process flow is such the client always calls A first followed by the call to B.
I have the Transaction attribute set as TX_REQUIRED at the whole bean level.
Now my question is as follows:
Since it is a stateless bean, ejbCreate() is called for every method's invocation.
So does it mean that a new transaction is started for every method invocation?
Also since a transaction ends by commit/rollback.
The transation associated with the method A/B will never get completed as there is no commit/rollback involved in method implementation.
So how is this transaction ended?
Any more details about the transaction management in stateless session beans is highly appreciated.
Any input at the earliest is highly appreciated.
Thanks in advance.

Since it is a stateless bean, ejbCreate() is called for every method's invocation.For stateless session bean , Create() is not delegated to the instance.
So does it mean that a new transaction is started for every method invocation?This depends opon the Tx attribute and sequence of calls. Since you have given Tx_required then if you call any method and there is no Tx context associated with client,then a new TX will be started by container othere wise it will execute in the same TX context as the calling client. Note that client can be jsp or other ejb method.
Also since a transaction ends by commit/rollback.
The transation associated with the method A/B will never get completed >as there is no commit/rollback involved in method implementation.
So how is this transaction ended?If you are using COntainer managed TX then Transaction handling like starting , ending etc is handled by the container. You need not worry about that.
Any more details about the transaction management in stateless session >beans is highly appreciated.
Any input at the earliest is highly appreciated.Some time back I had read the article on how the Transaction management done by container on IBM Site. I dont have URL , but you can search the site.
HTH
-Ashwani

Transaction is not Rolling Back in Stateless Session Bean

          Hi,
          I am using UserTransaction in Stateless Session bean .
          Transaction is not rolling back.
          The following code is writen in stateless session bean. In UserTransaction i am
          calling Two methods of another stateless session bean.
          The problem is if doJob2() method fails, doJob1() method is rolling back. These
          two methods consist of SQL statement with different Connection Object from TXDataSource.And
          session bean(TestSession) is set to CMT, attribute as "Required".
          try{
          Context ictx=new InitialContext();
          TestHome home=(TestHome)ictx.lookup("TestSession");
               utx = sessionCtx.getUserTransaction();
               utx.begin();
          TestRemote remote=home.create();
               remote.doJob1();
               remote.doJob2();
               utx.commit();
          }catch(Exception e)
               try{
               utx.rollback();
          }catch(Exception ex)
               System.out.println("unable to rollback"+ex);
          if any SQL Exception as occured in doJob2(), its calling method utx.rollback()
          in catch block. but SQL statements executed thru. doJob1() are not rolling back.
          what might be the reason?
          thanks
          Ranganath


          Thanx Priscilla ,
          Transaction is working.
          ranganath
          "Priscilla Fung" <[email protected]> wrote:
          >
          >In your ejb-jar.xml, you should specify <transaction-type> element to
          >be "Container"
          >for container-managed transaction. If you specified it to be "Bean" for
          >bean-managed
          >transaction, EJB ontainer will suspend the caller's transaction before
          >starting
          >a new transaction for your doJobX() methods. Thus, doJob1()nd doJob2()
          >will be
          >executing in different transactions, and thus rolling back doJob2()'s
          >transaction
          >will have no effect on work done and committed in doJob1()'s transaction.
          >
          >Regards,
          >
          >Priscilla
          >
          >
          >"Ranganath" <[email protected]> wrote:
          >>
          >>
          >>
          >>I am sending config.xml,deployment descriptors, code snippet for TestSession.
          >>i
          >>am using weblogic6.0sp2.
          >>if you need any aditional info. please let me know.
          >>
          >>thanks
          >>ranganath
          >>
          >>EJB-JAR.xml
          >>
          >><?xml version="1.0"?>
          >>
          >><!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
          >JavaBeans
          >>1.1//EN' 'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
          >>
          >><ejb-jar>
          >>     <enterprise-beans>
          >>     <session>
          >>          <ejb-name>TestSession</ejb-name>
          >>          <home>com.apar.sslbridge.test.TestHome</home>
          >>          <remote>com.apar.sslbridge.test.TestRemote</remote>
          >>          <ejb-class>com.apar.sslbridge.test.TestBean</ejb-class>
          >>          <session-type>Stateless</session-type>
          >>          <transaction-type>Bean</transaction-type>
          >>          <resource-ref>
          >>     <res-ref-name>jdbc/oraclePool</res-ref-name>
          >>     <res-type>javax.sql.DataSource</res-type>
          >>     <res-auth>Container</res-auth>
          >>          </resource-ref>
          >>     </session>
          >>     </enterprise-beans>
          >>     <assembly-descriptor>
          >>     <container-transaction>
          >>          <method>
          >>          <ejb-name>TestSession</ejb-name>
          >>          <method-intf>Remote</method-intf>
          >>          <method-name>*</method-name>
          >>          </method>
          >>          <trans-attribute>Required</trans-attribute>
          >>     </container-transaction>
          >> </assembly-descriptor>
          >></ejb-jar>
          >>
          >>
          >>TestSession CODE:
          >>
          >>
          >>     public void doJob1() throws RemoteException
          >>     {
          >>     Statement st = null;
          >>     String query=null;
          >>     try{
          >>     con=getConnection();
          >>     st=con.createStatement();
          >>     query="insert into x values("+x+++")";
          >>     System.out.println(query);
          >>     int rec=st.executeUpdate(query);
          >>     }catch(SQLException sqle)
          >>     {
          >>     System.out.println("SQL Exception "+sqle);
          >> throw new RemoteException("RemoteException*****SQLError");
          >>     } catch (Exception e) {
          >>     System.out.println("Exception "+e);
          >> throw new RemoteException("RemoteException*****GenralError");
          >> }
          >>}
          >>
          >>
          >> public void doJob2()throws RemoteException
          >> {
          >> Connection con=null;
          >> Statement st = null;
          >> String query=null;
          >> try{
          >> con=getConnection();
          >> st=con.createStatement();
          >> query="insert into y values("+x+++")";
          >> System.out.println(query);
          >> int rec=st.executeUpdate(query);
          >> }catch(SQLException sqle)
          >> {
          >> System.out.println("SQL Exception "+sqle);
          >> throw new RemoteException("RemoteException*****SQLError");
          >> } catch (Exception e) {
          >> System.out.println("Exception "+e);
          >> throw new RemoteException("RemoteException*****GenralError");
          >>}
          >>}
          >>private Connection getConnection(){
          >>try {
          >>Connection con = StaticParams.POOL_DATASOURCE.getConnection();
          >>return con;
          >>     } catch(Exception e) {
          >>     System.out.println("TestBean.getConnection() Unable to get get pool
          >>connection
          >>" + e);
          >>     }
          >>}
          >>
          >>
          >>
          >>
          >>"Priscilla Fung" <[email protected]> wrote:
          >>>
          >>>It should work if you are using TxDataSource. Could you post your
          >config.xml,
          >>>deployment descriptors, code snippet for TestSession?
          >>>
          >>>Regards,
          >>>
          >>>Priscilla
          >>>
          >>>"Ranganath" <[email protected]> wrote:
          >>>>
          >>>>Hi,
          >>>>
          >>>> I am using UserTransaction in Stateless Session bean .
          >>>> Transaction is not rolling back.
          >>>>
          >>>>The following code is writen in stateless session bean. In UserTransaction
          >>>>i am
          >>>>calling Two methods of another stateless session bean.
          >>>> The problem is if doJob2() method fails, doJob1() method is rolling
          >>>> back. These
          >>>>two methods consist of SQL statement with different Connection Object
          >>>>from TXDataSource.And
          >>>>session bean(TestSession) is set to CMT, attribute as "Required".
          >>>>
          >>>> try{
          >>>> Context ictx=new InitialContext();
          >>>> TestHome home=(TestHome)ictx.lookup("TestSession");
          >>>>     utx = sessionCtx.getUserTransaction();
          >>>>     utx.begin();
          >>>> TestRemote remote=home.create();
          >>>>     remote.doJob1();
          >>>>     remote.doJob2();
          >>>>     utx.commit();
          >>>> }catch(Exception e)
          >>>> {
          >>>>     try{
          >>>>      utx.rollback();
          >>>> }catch(Exception ex)
          >>>> {
          >>>>     System.out.println("unable to rollback"+ex);
          >>>>     }
          >>>> }
          >>>>if any SQL Exception as occured in doJob2(), its calling method utx.rollback()
          >>>>in catch block. but SQL statements executed thru. doJob1() are not
          >>rolling
          >>>>back.
          >>>>what might be the reason?
          >>>>
          >>>>thanks
          >>>>Ranganath
          >>>
          >>
          >

A question about entity manager in stateless session bean.

JSR 220 ejbcore, page 47 : stateless session bean: All business object references of the same interface type for the same stateless session bean have the "same object identity", which is assigned by the container.
So, if we have two session beans in client code...
@EJB Cart cart1;
@EJB Cart cart2;
then cart1.equals(cart2)==true
If we declare entity manager in stateless session bean:
@PersistenceContext( unitName="ds" ,type=PersistenceContextType.TRANSACTION)
private EntityManager em;If cart1 and cart2 are the same reference, do we have any problem when using the same reference(maybe the same em? ) to get data from db?

If cart1 and cart2 are the same reference, do we have
any problem when using the same reference(maybe the
same em? ) to get data from db?No. In EJB, there is a distinction between the EJB reference and the bean instance.
Each time you make an invocation on an EJB reference for a stateless session bean,
the container can choose any instance of that bean's bean class to process the
invocation. That's true whether you invoke the same reference multiple times or
two difference references to the same bean.
Each bean instance is guaranteed to be single-threaded.

Transaction Management - App Module in Stateless Session Bean

Hi All,
We are using Application Module in local mode in a Stateless Session Bean. The application module gets the database connection from the datasource of the application server(Oracle 9iAS).
The problem that we are facing is as follows
- When a database update/insert is made using the Application Module and the ViewObject (and the underlying Entity Object), the changes are not being commited.
Please note that we are not using the ApplicationModule.getTransaction.commit() as it does not give us commit/rollback control from another Session Bean/UseCase. We instead are relying on the Container to manager the transaction and commit the database changes. But the container does not seem to refresh the changes to the database.
Q1 - Is there a contract between the container and the application module that needs to be created so that the container managed-transaction and the application module work together ?
Any help in this matter would be greatly appreciated.
-Ankur Sinha

Q1 - Is there a contract between the container and the application module that needs to be created so that the container managed-transaction and the application module work together ?For stateless beans you have to call postChanges in the business method for the changes to be applied to the db. For stateful beans bc4j we do that automatically just before the transaction ends.
Take a look at the following howto
http://otn.oracle.com/products/jdev/howtos/bc4j/ejbstateless_with_bc4j.html
In 9.0.3 you'll be able to create a stateless service bean declaritively.
dhiraj Hi dhiraj,
- I looked at the example but was not able to find the ContainerManagedTxnHandlerImpl class in the BC4J jars. Can you point me to the latest version of BC4J on technet ?. I already have JDeveloper 9.0.2
- Regarding your response, what do you mean by creating stateless service bean declaritively ?
Thanks,
Ankur

Transaction can be applied to stateless session bean

is transaction can be applied to stateless session beanif yes/no why?

Just because a stateless session bean is stateless doesn't mean it doens't hold state. The stateless means it shouldn't hold any client state.
It can hold onto for example the dao objects.
The idea is that you pass all the client state to the sessionbean when calling it.
Eg.
public void doBulkOperation( User user ,string param1, String param2){
operation1( user, param1 );
operation2( user, param2 );
public void operation1( User user ,String param1){
//do some work involving user
public void operation2( User user ,String param2){
//do some work involving user
now suppose that doBulkOperation, operation1, operation2 are declared as transaction required. doBulkOperation starts the transaction if there isn't one running and joins the transaction. Then operation1 and operation2 join in the transaction.
Perfectly safe!
What you're not allowed to do is the following:
privata User user
public void doBulkOperation( User user ,string param1, String param2){
this.user = user;
operation1( param1 );
operation2( param2 );
public void operation1( String param1){
//do some work involving user
public void operation2( String param2){
//do some work involving user
This would be unsafe because concurrent calls will change the user and produce unpredictable results and possibly corrupting data.
It will work perfectly thougn if there is only one user or you're using a statefull session bean providing you don't share that bean with several clients.

Can we call a method in stateless session bean ?

Can we call a method in stateless session bean in onMessage method?

Hi,
The purpose of service locator is to abstract the lookup of the server side services like ejb and DSNs. It should be a normal java class but as such there is no such restriction. You can have a look at the service locator patter at the j2ee blue prints.
/Ashwani

Can we implement "Service Locator" in Stateless Session Bean??

Hi,
My enterprise application is using Stateless Session Bean. To increase the performace , I think of implementing "service Locator" pattern so as to cache the EJBHome objects in order to avoid looking up Home object every time. I want to know whether this will work out in case of stateless session bean??
Thanks for ur help.

Hi,
The purpose of service locator is to abstract the lookup of the server side services like ejb and DSNs. It should be a normal java class but as such there is no such restriction. You can have a look at the service locator patter at the j2ee blue prints.
/Ashwani

Transaction not rolling back in stateless session bean

          Hi,
          I am facing a problem...
          I have one stateless session bean which does multiple updates in SYBASE database.I
          am using non-transactional datasource. Bean calls a method of data access obejct
          whcih internally calls more than one one mehtod to update different tables.If
          any of update fails then I am explicitly thorwing EJBException. Still it is not
          rolling back.
          I have one more application where similar situation is there but only difference
          is that there we have Entity bean and updates are being done through store method.
          In that case with same datasource it is rolling back perfectly.
          I have tried with transactional datasource as well but it didn't work.Then I tried
          to put setAutoCommit(false) in my connection class which gives me connection.But
          then it is not allowing me to enter into my application.
          In deployment descriptor for both the beans transaction attribute is required
          for all methods.
          Regards.
          Rahul.


          Hi,
          I am facing a problem...
          I have one stateless session bean which does multiple updates in SYBASE database.I
          am using non-transactional datasource. Bean calls a method of data access obejct
          whcih internally calls more than one one mehtod to update different tables.If
          any of update fails then I am explicitly thorwing EJBException. Still it is not
          rolling back.
          I have one more application where similar situation is there but only difference
          is that there we have Entity bean and updates are being done through store method.
          In that case with same datasource it is rolling back perfectly.
          I have tried with transactional datasource as well but it didn't work.Then I tried
          to put setAutoCommit(false) in my connection class which gives me connection.But
          then it is not allowing me to enter into my application.
          In deployment descriptor for both the beans transaction attribute is required
          for all methods.
          Regards.
          Rahul.

Can Entity Bean with Home Business Method replace Stateless Session Bean?

Since Entity Bean can have business methods in the Home Interface, can we use Entity Bean with Home Business Methods to replace Stateless Session Bean?
I am assuming we can get better performance by doing this since the overhead of creating Component Object can be avoided as compared to stateless session beans.

Requires-new makes the container start a new transaction. Only use that flag
          at the point that you are certain that a NEW transaction should BEGIN. I
          suggest you use Required as your default for all methods in the application,
          and only change that to anything else when you are certain that you should.
          Peace,
          Cameron Purdy
          Tangosol Inc.
          << Tangosol Server: How Weblogic applications are customized >>
          << Download now from http://www.tangosol.com/download.jsp >>
          "A.J,LEE" <[email protected]> wrote in message
          news:3ba5adb2$[email protected]..
          >
          > I find it result in "dead lock"
          > when I call RequiresNew attributed CMP method in session Bean.
          > Then, Is it possible to use CMP which is set with "RequiresNew"
          transaction attribute?
          >
          > I Wonder why.
          >
          > Thanx in advance.

Calling EJB 3.0 Stateless Session Bean

Dear all,
I created a stateless session bean with a hello world method on it. Now i want to call the method from a BeanDecorator class, through a getter metod. When i use the jndi lookup in my getter, i can call the helloWorld method without a problem. However, when i dont use the jndi lookup, and only use the @EJB annotation, i always get a nullpointer.
This is working:
InitialContext ic = new InitialContext();
test = (TestLocal)ic.lookup("test.be/ear~bd/LOCAL/TestBean/"+TestLocal.class.getName());
test.helloWorld()
This gives nullpointer:
@EJB
private TestLocal test;
test.helloWorld();
What is the correct way to consume session beans without having to explicitly code the jndi lookup?
Kind regards.

Hi,
any annotation like this can be used only in "managed classes" like Session Beans, Servlets etc. Managed classes are those classes managed by the J2EE server. Managed here means, lifetime controlled by server.
You can find this in J2EE specification.
Frank

How to use jta in toplink and stateless session bean EJB 3.0?

I have an application with techologies jsf,stateless session bean, adf, toplink
generated by toplink workbench.
In web side ı want to use two methods in stateless session bean which are updated
different tables. I call these methods in my page backing bean.
I also want to JTA in web side. My first methods is done correctly, but second method has an error. I wanto to rollback all transaction.
How can ı do that? with using JTA in Toplink...

Yuichi
Did you manage to solve this? I'm doing something similar and seeing the same problem, although they're up to 7.3 SP7.
Any help greatly appreciated.
Lewis

How to integrate hibernate with Stateless Session bean in weblogic10.0

Hi,
I need to invoke hibernate(3.x) DAO from EJB Stateless Session bean(EJB2.x). I am using mysql database. Can somebody please post the configuration.
Thanks in advance,
Rushi.

Hi Deepak,
Thanks for your reply.
Actually, our stand alone java application already using spring-hibernate feature. Now we are planning divide our application into modules and deploy each module as ejb beans. As it is already integrated with spring-hibernate we are not using entity beans as of now. My understanding is container uses some default transcation management .so, my question is what are all the configurations needs to be done to let weblogic 10.0 server uses org.springframework.orm.hibernate3.HibernateTransactionManager. I mean, is there are any .xml file in weblogic to configure all these? please reply deepak I am struck here..
Regards,
Rushi.

EJB Stateless Session Bean Transactions

I have a stateless session bean.
Its deployment descripter references a JDBC DataSource.
It uses container managed transactions.
If I make JDBC calls, within a business method
of this stateless session bean, with the referred datasource, is it attached
to a container managed transaction?

If I make JDBC calls, within a business method
of this stateless session bean, with the referred
datasource, is it attached
to a container managed transaction?IIRC, yes. For CMT, the container will roll back any JDBC actions carried out by a method if it fails.

Bean-managed stateless session bean can't roll back using JTA

Similar Messages

Maybe you are looking for