Transaction Attibutes in EJB

How can we set the Isolation levels for Transaction in Session Beans. and as well as Entity Beans i.e. CMP

Configure the underlying datasource and connection pools in appserver.
-cheng

Similar Messages

Assignment of transaction attributes in ejb-jar.xml

Hi all,
I'm going through the employee example from the book "Java programming in SAP web application server". I have followed the instrucstions to the letter and have triple checked that i did not miss anything.
During the part "Defining Transaction Control", when i go to the "Assembly" tab, choose "Container-transaction" and click add; i get the following error message.
You have to create and reference EJBs first. Afterwards you can choose them here.
Newly created EJBs are referenced automatically in the ejb-jar.xml, in special cases you might have to reference them manually.
Below is a copy of the ejb-jar. Both beans are referenced in the file so i don't really understand the error message!
Thanks for your help.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
     <description>EJB JAR description</description>
     <display-name>EJB JAR</display-name>
     <enterprise-beans>
          <session>
               <ejb-name>EmployeeServicesBean</ejb-name>
               <home>com.sap.demo.EmployeeServicesHome</home>
               <remote>com.sap.demo.EmployeeServices</remote>
               <local-home>com.sap.demo.EmployeeServicesLocalHome</local-home>
               <local>com.sap.demo.EmployeeServicesLocal</local>
               <ejb-class>com.sap.demo.EmployeeServicesBean</ejb-class>
               <session-type>Stateless</session-type>
               <transaction-type>Container</transaction-type>
               <ejb-local-ref>
                    <ejb-ref-name>ejb/Employee</ejb-ref-name>
                    <ejb-ref-type>Entity</ejb-ref-type>
                    <local-home>com.sap.demo.EmployeeLocalHome</local-home>
                    <local>com.sap.demo.EmployeeLocal</local>
                    <ejb-link>EmployeeEjb.jar#EmployeeBean</ejb-link>
               </ejb-local-ref>
          </session>
          <entity>
               <ejb-name>EmployeeBean</ejb-name>
               <home>com.sap.demo.EmployeeHome</home>
               <remote>com.sap.demo.Employee</remote>
               <local-home>com.sap.demo.EmployeeLocalHome</local-home>
               <local>com.sap.demo.EmployeeLocal</local>
               <ejb-class>com.sap.demo.EmployeeBean</ejb-class>
               <persistence-type>Container</persistence-type>
               <prim-key-class>java.lang.Long</prim-key-class>
               <reentrant>False</reentrant>
               <cmp-version>2.x</cmp-version>
               <abstract-schema-name>EmployeeBean</abstract-schema-name>
               <cmp-field>
                    <field-name>lastname</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>firstname</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>id</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>department</field-name>
               </cmp-field>
               <primkey-field>id</primkey-field>
               <query>
                    <description>Query for getting all employee objects.</description>
                    <query-method>
                         <method-name>findAllEmployees</method-name>
                         <method-params/>
                    </query-method>
                    <ejb-ql>Select object (p) from EmployeeBean p</ejb-ql>
               </query>
          </entity>
     </enterprise-beans>
     <assembly-descriptor/>
</ejb-jar>

I was able to add the transaction attributes manually to the ejb-jar.xml file. below is what the file looks like now for those interested.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
     <description>EJB JAR description</description>
     <display-name>EJB JAR</display-name>
     <enterprise-beans>
          <session>
               <ejb-name>EmployeeServicesBean</ejb-name>
               <home>com.sap.demo.EmployeeServicesHome</home>
               <remote>com.sap.demo.EmployeeServices</remote>
               <local-home>com.sap.demo.EmployeeServicesLocalHome</local-home>
               <local>com.sap.demo.EmployeeServicesLocal</local>
               <ejb-class>com.sap.demo.EmployeeServicesBean</ejb-class>
               <session-type>Stateless</session-type>
               <transaction-type>Container</transaction-type>
               <ejb-local-ref>
                    <ejb-ref-name>ejb/Employee</ejb-ref-name>
                    <ejb-ref-type>Entity</ejb-ref-type>
                    <local-home>com.sap.demo.EmployeeLocalHome</local-home>
                    <local>com.sap.demo.EmployeeLocal</local>
                    <ejb-link>EmployeeEjb.jar#EmployeeBean</ejb-link>
               </ejb-local-ref>
          </session>
          <entity>
               <ejb-name>EmployeeBean</ejb-name>
               <home>com.sap.demo.EmployeeHome</home>
               <remote>com.sap.demo.Employee</remote>
               <local-home>com.sap.demo.EmployeeLocalHome</local-home>
               <local>com.sap.demo.EmployeeLocal</local>
               <ejb-class>com.sap.demo.EmployeeBean</ejb-class>
               <persistence-type>Container</persistence-type>
               <prim-key-class>java.lang.Long</prim-key-class>
               <reentrant>False</reentrant>
               <cmp-version>2.x</cmp-version>
               <abstract-schema-name>EmployeeBean</abstract-schema-name>
               <cmp-field>
                    <description>
                    </description>
                    <field-name>lastname</field-name>
               </cmp-field>
               <cmp-field>
                    <description>
                    </description>
                    <field-name>firstname</field-name>
               </cmp-field>
               <cmp-field>
                    <description>
                    </description>
                    <field-name>id</field-name>
               </cmp-field>
               <cmp-field>
                    <description>
                    </description>
                    <field-name>department</field-name>
               </cmp-field>
               <primkey-field>id</primkey-field>
               <query>
                    <description>Query to get all employee objects.</description>
                    <query-method>
                         <method-name>findAllEmployees</method-name>
                         <method-params/>
                    </query-method>
                    <ejb-ql>Select object (p) from EmployeeBean p</ejb-ql>
               </query>
          </entity>
     </enterprise-beans>
     <assembly-descriptor>
          <container-transaction>
               <description>container-transaction</description>
               <method>
                    <ejb-name>EmployeeBean</ejb-name>
                    <method-name>*</method-name>
               </method>
               <method>
                    <ejb-name>EmployeeServicesBean</ejb-name>
                    <method-name>*</method-name>
               </method>
               <trans-attribute>Required</trans-attribute>
          </container-transaction>
     </assembly-descriptor>
</ejb-jar>
Thanks

Transaction problem in ejb

Hi
I have a problem related to CMP entity beans.
I am using Oracle 9i and weblogic 6.1
Here is the description of the problem.
The transaction attribute of all the beans is set to 'Required'.
I have a PersonBean (CMP) in Person.jar mapping to Person table along with other
beans.
I have a MemberBean(CMP) in Member.jar file mapping to Member table along with
many other beans.
There is a one to many relation ship between person and member tables in Oracle
9i database :
Id in the person table is the P_Key and Person_Id in Member table is the related
foreign key.
No relationship was made between Person and Member beans as there were in two
different jar files with different deployment descriptors.
I have a stateless session bean PersonService bean.
There is a method in PersonService bean called createPerson(String name);
This method creates Person in the database using Person p = PersonHome.create(),
long personId = p.getId()..returns the primary key of the person.
PersonService calls createMember(long personId) now.
which will try to create a Member record in the database using the personId.
Now the Member bean fails to create and the transaction is rolled back with a
foreign_key violation exception.
because it cannot locate the Person EJB Primary key entry in the underlying table.
But the EJB cache is still inserted properly with Person EJB (findByPrimaryKey
works).
I feel that Member bean is not able to participate in the same transaction of
the Person bean inspite of keeping the transaction attribute to 'Required'.
When I keep the transaction of Person bean to 'RequiresNew', then the transation
of createPerson is getting committed and Member is starting a New transaction
and it gets created.
But I donot want like this.
I want all the beans to be participating in the same transaction.
According to Oracle / Weblogic documentation the default database isolation mode
Read_Committed should allow participants in transaction to see uncommitted data
while participants outside the transaction see only committed data. I have tried
other dataabase isolation modes (such as Read_Uncommitted, "Serializable") these
appear to either create other problems or not have an affect.
Any solution to this problem is highly appreciated.
Thanks
Lavanya

Previously our code was running on Weblogic where
methodA() -> Transaction Attribute -> Supports
methodB() -> Transaction Attribute -> Required
But in JBOSS in order to run the same thing we have to do
methodA() -> Transaction Attribute -> Required
methodB() -> Transaction Attribute -> Required
Any Pointers??

Can I use JTA transactions in a EJB that calls a webservice

Hi,
I created a EJB Client that calls two web services with JTA transactions. I would like to undo the first web services when the second one fails. Is this possible at all? If yes, is JTA the right way to do this?
Thank you
Julia

You may be able to but it all depends on the RAM and the system. Some work, Some Don't.
But if you haven't already bought the RAM just buy what is right for the system.
Even if the faster RAM works it will not run at the faster speed. It would be Clocked down to the speed of the system it is installed in.

Transaction handling between EJBs

hi,
I am having a delegate kind of Stateless Session Bean(SSB which calls three other SSBs and perform database operations. My delegate bean does not have any database activities associated with it.
I am using container managed transaction and setting transaction attribute for the business function calling the 3 SSBs as RequiresNew. I have set the transaction attribute for the other 3 beans as Required. But when there is a update error, the transaction is not rolling back. Have someone come across similar problem?
Thanks in advance.
Regards,
Karthik

An user exception (in the EJB spec. called application exception) must not be extend RunTimeException.
Hi crackers, here are some sentences from the EJB specification:
Code that you develop should not throw EJBException - that's "reserved" for the container vendor to signal a container failure.EJB Spec. 2.0 (page373):
If the bean method performs an operation that results in a checked exception[32] that the bean
method cannot recover, the bean method should throw the javax.ejb.EJBException
that wraps the original exception.
Not entirely accurate. If a user-defined Exception extends the Exception class, yes, you must explicitly rollback the transaction. However, if the user-defined Exception extends RuntimeException, the container will roll back the exception for you.EJB Spec. 2.0 (page372):
An application exception class must be a subclass (direct or indirect) of java.lang.Exception.
An application exception class must not be defined as a subclass of the java.lang.RuntimeException
or of the java.rmi.RemoteException.

Transaction handling in EJBs

i dont know ejb�s handle transaction.
any sugesstions??????
sorry my english, ciao

http://www.google.com/search?hl=en&q=EJB+transaction+handling
Especially look at this one:
http://www.kevinboone.com/ejb-transactions.html

How to commit/rollback a transaction encompasing multiple EJBs

I have 2 Stateless Session Beans 'RulesManager' and 'BankManager'. Each EJB method in them gets a connection, perform the task, close the connection and return the results.
Now in RulesManager I have an EJB method processRules(). And in BankManager I have an EJB method updateTransactions().
I have a requirement that means I first have to call BankManager's updateTransactions() method; if successful then call RulesManager's processRules() method. IF its successfull as well then commit else rollback.
I dont know how to do this. Can anybody help me in this regard?
Thanks

Thanks kdgregory. This is how the things work out in our application.
I have a class BankDelegate which has each public method in BankManager SSB without the throws clause. Inside each method I get remote interface of BankManager SSB and then calls the corresponding EJB method.
Similarly I have a RulesDelegate class which has each public method in RulesManager SSB without the throws clause. Inside each method I get remote interface of RulesManager SSB and then calls the corresponding EJB method.
User press Update button on JSP which submits the form to another JSP. That JSP creates an instance of BankDelegate and call its updateTransactions() method.
Each EJB method is using container managed transactions. Inside each EJB method, if anything failed then i issued a rollback using this._sessionContext.setRollbackOnly();
I am using MS SQL Server 2000.
Thanks

Transaction settings in ejbs.

Hi all,
I have three questions:
1) I have several EJBs related to different business entities being called within one single transaction by the client;
I would like to know if it is better to have bean lvel transaction setting or method level transaction setting.
2) If TX_REQUIRED is put at the method level that involve create/save/delete SQL statements.Can TX_NOT_SUPPORTED transaction attribute be set to the methods that involve DML statement(Select statements).
3) Also is there any restriction that the calling method within a single large transaction must hvae more restrictive transaction attribute
(with TX_REQUIRED) than the method that is being called
(with TX_NOT_SUPPORTS/TX_SUPPORTS) or vice versa.
thanks in advance.

1) EJBs server handle concurrency automatically, a bean's methods do not have to be made a thread-safe.The EJB specification prohibits use of the synchronized keyword.
The EJB container has to maintain complete control over the concurrency, transaction and persistence.

Transaction management in EJB

Suppose, a method in session bean is called that deals with some entity beans. I want to maintain transaction over some block of codes separately (e.g. History table has to be updated synchronously with the master table) not over the whole things in the method. How it can be done?

Hi Kuntal,
BMP/CMP and BMT/CMT are completely different. BMP/CMP (Bean-managed persistence/ Container-managed persistence) describes the way in which entity bean persistence is handled.
BMT/CMT (Bean-managed transactions / Container-managed transactions) controls whether bean developer or the container is in charge of demarcating transactions.
Entity beans can be either BMP or CMP. However, they always have CMT. It's not possible to use UserTransaction wtihin an entity bean.
For session beans, you can use BMT and use the session bean as a facade to access your entity beans. That would give you the control you're looking for.

Default Transaction Attribute for EJBs

Guys,
Can you tell me the default transaction attributes if any in Weblogic 7.0 i.e.
the attributes used
if not explicitly specified for a bean method when using in CMT ?
For CMP entity beans,
MDBs,
Other beans (?) :
thanks for your help
regards
Ved

Hello Mr. Woollen,
As always, thank you for your excellent insight into the internals of BEA WebLogic.
I now have a better understanding of what happens "by default" in WLS. I do agree
that changing this now would definitely break existing applications. It's always
difficult to decide when to officially deprecate a "feature" or to leave it in
forever.
Best regards,
Ryan LeCompte
[email protected]
http://www.louisiana.edu/~rml7669
Rob Woollen <[email protected]> wrote:
For better or worse, MDBs default to NotSupported and everything else
defaults to Supports.
I say for better or worse because I would have liked to change it to
always require the user to set a default transaction attribute.
Unfortunately we have many customer's applications who depend on this
behavior, and I believe if we change it we will break all of them.
Regardless, I would not recommend depending on our default tx attribute
and instead always set one for '*'.
In general, entity beans should run as Required or Mandatory. Session
beans are usually required or notsupported. MDBs are required or
notsupported.
-- Rob
Ved Gangaputra wrote:
Guys,
Can you tell me the default transaction attributes if any in Weblogic7.0 i.e.
the attributes used
if not explicitly specified for a bean method when using in CMT ?
For CMP entity beans,
MDBs,
Other beans (?) :
thanks for your help
regards
Ved

Manage a transaction without an EJB container !

Hi all,
i have a problem, i have to write into 5 tables of a DBMS launching 5 queries.
My application is a standalone program, about your opinion how can i manage the 5 queries inside a transaction ?
I have heard that i could use a property of the Connection class called AutoCommit.
Any suggestion ?
Cheers.
Stefano

I'd say that if the OP hasn't heard of autoCommit that
Spring might be over his/her head. Yeah, your probably right.
Better to learn
how to do it with JDBC first, IMO.Definitely
Not only will they learn about units of work, they'll
appreciate all that a good framework is doing for them
once they realize how much work it is to do by hand.
%Just want to point out other solutions when they are potential fits, up to the poster to decide if its overkill for their scenario.
Cheers,
-Scott

Setting transaction attributes for EJB Create methods

Dear developers
How do I set transaction attributes at the method level. I am able to set this only at the bean level.
I am trying to use container managed transactions.
Thanks
Naveen

if you specify * in the <method-name> element, then it is the bean
otherwise, you can specify a particular method name in the <method-name> element.
Best regards...
Dear developers
How do I set transaction attributes at the method
level. I am able to set this only at the bean level.
I am trying to use container managed transactions.
Thanks
Naveen

JDBC Connections in WLS 7.0.SP2

Hello All,
We are using both entity beans and JDBC calls inside our Stateless Session Beans.
Our tests show that
1. we need more database connections (in pool) than number of concurrent users
(say twice)
2. getting and releasing connections become a bottleneck as we need to do this
for every method invocation for making JDBC calls
3. Methods using only entity beans run faster
Can somebody explain this behaviour. Thanks in advance for the time and help.
Best Regards
MS

Hi Manoj,
"MS" <[email protected]> wrote in message news:3eeac5af$[email protected]..
Hello All,
We are using both entity beans and JDBC calls inside our Stateless SessionBeans.
Our tests show that
1. we need more database connections (in pool) than number of concurrentusers
(say twice)It all depends how transaction processing is arragend in your application.
In the worst case you both get connections from the pool using the pool
driver
and use TxDatasource for entity beans. Than you will have number of needed
pool connections doubled. The same story is when you actively use
RequiresNew transaction attribute for SLSB.
Normally when you use the Required transaction attibute for
EJBs and TxDatasource to get connections, the max number of
consumed connections will be around a number of the execution
threads.
2. getting and releasing connections become a bottleneck as we need to dothis
for every method invocation for making JDBC callsCan you provide more information on the approach used to
indentify fact of bottleneck? Also, could you please post the connection
pool and datasource definitions? That will help to identify if the pool
is possible misconfigured.
3. Methods using only entity beans run fasterIt's hard to tell why it happens to you withouth knowing more about the
application. But here are a couple of suggestions: first, weblogic makes
extensive use of caching when database is accessed via EJBs. second,
those direct JDBC calls are not written well ot use inappropriate
transaction
model.
Can somebody explain this behaviour. Thanks in advance for the time andhelp.
Let me know if you have more questions.
Regards,
Slava Imeshev

ORABPEL-08033: EJB Transaction Error

Hi
I have a usecase in which procA(sync Service) calling procB (Async Service) and on completion of execution, ProcB gives a non blocking invoke back to procA. Condition: The either of one should be in running state always.
However there are fault situation in ProcB hence to not to break the sequence we have put a catchAll block which handles/logs and then gives the non blocking invoke back to procA.
But when ProcB fails somewhere because of some other partner links, it is safely going into catchAll and handling it well and when it tries to do a non blocking invoke it is resulting in following:
ORABPEL-08033
EJB Transaction Error.
EJB exception happened while invoking the partner. Please verify partner service.
Can somebody give me some leads in this?
TIA
regards
Joy

I have setup catch statements, both an catch all in the outermost scope and a catch for remote fault at the scope surrounding the call to the AQ. But that's not the issue. The problem is that BPEL don't get the error. The error stay's at the adapter and the BPEL don't come to a failed state.

EJB Entity transaction rollback problem

          Hello,
          I have created 2 beans one is a Stateless Session and the other a Bean Managed Entity Bean. The SS Bean has methods to retrieve an Oracle Connection from a DataSource defined connection pool, and to close a connection. The entity bean I have created is responsible for insterting a new record into one of the tables in my database.
          I have a client app that calls the ejbCreate method on the entity bean at which point the Entity EJB takes control, gets a valid connection from the SS EJB, runs a simple working SQL SELECT statement (obtaining correct values), and then attempts to perform an insert into a table using a prepared statement. My problem is that the application runs fine without any errors and all calls are made and all calls seem to be working fine. I have checked to make sure that the Datasource I am using is AutoCommit= false and it is and there are no exceptions being thrown in my EJB's but yet it appears as though the SQL statements executeUpdate() command is not being committed as their is no rows created in the database. Does anyone know what I may be doing wrong. I have all ACL parameters set up correctly and as I stated before the entire app runs without errors and I do have a SELECT statment that is working properly within the same method as the INSERT statement which is not!!! Please send any suggestions!!
          Justin


          I am using CMT, it is activated by default on Entity Beans I believe. The bean itself is marked as TX_REQUIRED so I believe all the methods automatically are all TX_REQUIRED.
          Here is my Bean ejbCreate Method, My PK class, and my ejb-jar.xml file-- I've pasted them below for convenience.
          ejbCreate:
               public CustomerPK ejbCreate(String aUserName, String aPassword, String aFirstName,
                    String aMiddleInit, String aLastName, String aEmailAddr)
                    throws javax.ejb.CreateException {
               Connection conn=null;
               long nextPrsnID;
               long nextCustID;
               if (verifyParams(aUserName, aPassword, aFirstName, aMiddleInit,
                    aLastName, aEmailAddr)) {
               if (isUniqueUserName(aUserName)) {
               try {
                    conn=getConnection();
                    conn.setAutoCommit(false);
                    nextPrsnID=addPerson(conn,aFirstName,aMiddleInit,aLastName); // adds a person to the person table consists of just simple SQL
                    nextCustID=addCustomer(conn,nextPrsnID, aUserName,aPassword, aEmailAddr); //adds a customer to the customer table
                    // SET THE BEAN MANAGED PUBLIC VARIABLES
                    this.userName=aUserName;
                    this.password=aPassword;
                    this.firstName=aFirstName;
                    this.middleInit=aMiddleInit;
                    this.lastName=aLastName;
                    this.emailAddr=aEmailAddr;
                    this.personID=nextPrsnID;
                    this.custID=nextCustID;
                    conn.commit(); // with this statement here the transaction goes through otherwise the DB will not be updated
               catch (Exception e){
                    throw new javax.ejb.CreateException("Experiencing Database Problems-- Unrecoverable Error"); // rollback transaction
               finally{
                    cleanup(conn,null); // close the connection
               else {           // UserName already exists
               throw new javax.ejb.CreateException("Sorry username already exists please choose another one");
               else {          // Registration parameters were not verifiable
               throw new javax.ejb.CreateException("Registration paramater rules were violated");
               CustomerPK custPK=new CustomerPK(nextCustID);
               return custPK;
          EJB CUSTOMER PRIMARY KEY CLASS:
          public class CustomerPK implements java.io.Serializable {
          // PRIMARY KEY VARIABLES
          public long CustomerID;
          public CustomerPK(long aCustomerID) {
          this.CustomerID=aCustomerID;
          public CustomerPK() {
          public String toString(){
          return ((new Long(CustomerID)).toString());
          public boolean equals(Object aComparePK){
          if (this.CustomerID==((CustomerPK)aComparePK).CustomerID){
               return true;
          return false;
          public int hashCode(){
          return ((new Long(CustomerID).toString()).hashCode());
          } // END-CLASS
          CUSTOMER 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>
          <entity>
               <ejb-name>Customer</ejb-name>
               <home>CustomerHome</home>
               <remote>Customer</remote>
               <ejb-class>CustomerBean</ejb-class>
               <persistence-type>Bean</persistence-type>
               <prim-key-class>CustomerPK</prim-key-class>
               <reentrant>False</reentrant>
               <resource-ref>
          <res-ref-name>jdbc/DeveloperPool</res-ref-name>
          <res-type>javax.sql.DataSource</res-type>
          <res-auth>Container</res-auth>
          </resource-ref>
          </entity>
          </enterprise-beans>
          <assembly-descriptor>
          <container-transaction>
               <method>
               <ejb-name>Customer</ejb-name>
               <method-intf>Remote</method-intf>
               <method-name>*</method-name>
               </method>
               <trans-attribute>Required</trans-attribute>
          </container-transaction>
          </assembly-descriptor>
          </ejb-jar>
          "Cameron Purdy" <[email protected]> wrote:
          >Are you using CMT? Have you marked the methods as REQUIRED?
          >
          >Peace,
          >
          >--
          >Cameron Purdy
          >Tangosol, Inc.
          >http://www.tangosol.com
          >+1.617.623.5782
          >WebLogic Consulting Available
          >
          >
          >"Justin Jose" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> Hello,
          >>
          >> I have created 2 beans one is a Stateless Session and the other a Bean
          >Managed Entity Bean. The SS Bean has methods to retrieve an Oracle
          >Connection from a DataSource defined connection pool, and to close a
          >connection. The entity bean I have created is responsible for insterting a
          >new record into one of the tables in my database.
          >> I have a client app that calls the ejbCreate method on the entity bean at
          >which point the Entity EJB takes control, gets a valid connection from the
          >SS EJB, runs a simple working SQL SELECT statement (obtaining correct
          >values), and then attempts to perform an insert into a table using a
          >prepared statement. My problem is that the application runs fine without
          >any errors and all calls are made and all calls seem to be working fine. I
          >have checked to make sure that the Datasource I am using is AutoCommit=
          >false and it is and there are no exceptions being thrown in my EJB's but yet
          >it appears as though the SQL statements executeUpdate() command is not being
          >committed as their is no rows created in the database. Does anyone know
          >what I may be doing wrong. I have all ACL parameters set up correctly and
          >as I stated before the entire app runs without errors and I do have a SELECT
          >statment that is working properly within the same method as the INSERT
          >statement which is not!!! Please send any suggestions!!
          >>
          >> Justin
          >
          >

Transaction Attibutes in EJB

Similar Messages

Maybe you are looking for