Ejb Transaction Attribute

We are using Ejbs2.1
Our system uses Database but we are not writing IT System so we do not need To use trasactions at all.
We are using RequiresNew as the Transaction Attribute so every
ejb starts in a new transaction and each method only invoke one database access
We are now considering to change the Transaction Attribute to NotSupported So each database access will do a commit (the database connection is set to autoCommit)
We thought that this approach will be more efficient since no transaction will be created.
I will be happy to hear what you think about this approach, is our assumption is correct?

it means that the method must operate outside of an active transaction - in other words there will be no active transaction during its runtime. If there is an active transaction when the method is called, that transaction is "put on hold" until the "notsupported" EJB call finishes.

Similar Messages

EJB + "transaction attributes" + "best practice"

hi
For EJBs, when you specify multiple transaction attributes for a single
method, is the latest attribute taken or the first?
for e.g. In Jbuilder8 in the container transaction section for an EJB,
if i were to put
Method Transaction attribute
* Required
getSomeThing() Supported
As you can see all the methods were initially given the required attribute,
and then the method getSomeThing() was given Supported. will the
getSomething() method use Required or else Supported. Secondly, will this
cause an extra overload (Transaction attributes are set and the again
reset), is it a recommended best practice?
suren

getSomeThing() Supported
As you can see all the methods were initially given
the required attribute,
and then the method getSomeThing() was given
Supported. will the
getSomething() method use Required or else Supported.It will use supported.
Secondly, will this
cause an extra overload (Transaction attributes are
set and the againIt won't cause extra overload.
reset), is it a recommended best practice?It really depends on your needs - what you're trying to achieve. There is no best practice for that it depends on the application you're building.
Regards,
Dimitar

Regarding EJB transaction attributes

Hi,
I am having a method in a stateless session bean. This bean's transaction
attribute is "Required'. This method in turn is calling a create method using another entity bean whose transaction attribute is "Required".
After calling the create method we are using another stateless session bean
having transaction attribute "NotSupported" to retrieve the previously created record(We have our own business requirement, that's the reason we are using here another session bean to retrieve immediatly the created record, instead of using the same entity bean). All the above transactions are done in the same method.
while calling the retrive method to retrieve the immediatly created record, we are getting an exception saying the below.
SQL0911N The current transaction has been rolled back because of
a deadlock or timeout. Reason code "68".
What could be the problem? Can anyone help me out?
Note : if we use a different method for the retrieval alone then it's working fine.
Thanks.

The container might have suspended the current transaction, and called the retrieve method whose tx attribute is NotSupported. The duration of this invocation may have exceeded the transaction timeout limit. After the transaction has been left idle for such a long period, it times out.

Is it posible that transaction attribute required & isolation any after no

Dear freind
I want to share this question which i face in a company Rose It Solution Delhi India
que:-- There is a Account EJB transaction attribute is required which isolation level select that there will be no changes in database a) TX_readOnly b) TX_raed_commited c)TX_unreapitable_read d)TX_Serializable After all i think TX_readOnly is not a isolation level second things that is transaction attribute is required then why not changes in database
Regards
Rajesh Pandey freelance Developer e-mail:-- [email protected]
Please use html tags to format code blocks.

Dear freind
I want to share this question which i face in a company Rose It Solution Delhi India
que:-- There is a Account EJB transaction attribute is required which isolation level select that there will be no changes in database a) TX_readOnly b) TX_raed_commited c)TX_unreapitable_read d)TX_Serializable After all i think TX_readOnly is not a isolation level second things that is transaction attribute is required then why not changes in database
Regards
Rajesh Pandey freelance Developer e-mail:-- [email protected]
Please use html tags to format code blocks.

Can i call Bean managed EJB with transaction attribute Required New

          I am calling a BeanManaged EJB which has a transaction attribute
          set to Required New from a container managed bean. Does it create a new transaction
          other than the Bean managed transaction. Do i really need a required new field
          transaction attribute.All i need is user controlled transaction.Do i need to set
          the transaction aatibute.
          Thanks
          Krish.


Hi Krish,
          The question does not make much sense.
          I would suggest that you set all your tx settings to "Required" unless you
          have a specific reason to do otherwise, and in those few instances that you
          have a specific reason to do otherwise, then change it in just those places.
          Peace,
          Cameron Purdy
          Tangosol Inc.
          << Tangosol Server: How Weblogic applications are customized >>
          << Download now from http://www.tangosol.com/download.jsp >>
          "KRISH" <[email protected]> wrote in message
          news:[email protected]..
          >
          > I am calling a BeanManaged EJB which has a transaction attribute
          > set to Required New from a container managed bean. Does it create a new
          transaction
          > other than the Bean managed transaction. Do i really need a required new
          field
          > transaction attribute.All i need is user controlled transaction.Do i need
          to set
          > the transaction aatibute.
          >
          > Thanks
          >
          > Krish.
          >

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

Error deploying EJB on weblogic: Unable to set the transaction attribute

Hi,
I'm trying to deploy an application in WL10.3.2 and an error occurred during activation of changes.
Here is the error message from the log file:
<Jun 6, 2011 1:28:27 PM MDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'serverEAR-2' due to error weblogic.application.ModuleException: Exception preparing module: EJBModule(serverEJB-2.8.0.jar)
Unable to deploy EJB: C:\oracle\Middleware\user_projects\domains\base_domain\servers\Server_3\tmp\_WL_user\serverEAR-2\1zw7ao\serverEJB-2.8.0.jar from serverEJB-2.8.0.jar:
Unable to set the transaction attribute for method 'saveActionGroup(EditableActionGroup)' on EJB 'ViewBean'. No matching method could be found. Please verify the method signature specified in the ejb-jar.xml file matches that of your Remote interface for this EJB.
weblogic.application.ModuleException: Exception preparing module: EJBModule(serverEJB-2.8.0.jar)
Unable to deploy EJB: C:\oracle\Middleware\user_projects\domains\base_domain\servers\Server_3\tmp\_WL_user\serverEAR-2\1zw7ao\serverEJB-2.8.0.jar from serverEJB-2.8.0.jar:
Unable to set the transaction attribute for method 'saveActionGroup(EditableActionGroup)' on EJB 'ViewBean'. No matching method could be found. Please verify the method signature specified in the ejb-jar.xml file matches that of your Remote interface for this EJB.
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:454)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:59)
     Truncated. see log file for complete stacktrace
Caused By: weblogic.ejb.container.deployer.DeploymentDescriptorException: Unable to set the transaction attribute for method 'saveActionGroup(EditableActionGroup)' on EJB 'ViewBean'. No matching method could be found. Please verify the method signature specified in the ejb-jar.xml file matches that of your Remote interface for this EJB.
     at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.processCTs(MBeanDeploymentInfoImpl.java:1502)
     at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.processSpecificMethodCTs(MBeanDeploymentInfoImpl.java:1472)
     at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.initializeTransactionAttribute(MBeanDeploymentInfoImpl.java:773)
     at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:259)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1190)
     Truncated. see log file for complete stacktrace
Please help me...Thanks.

In your ejb-jar.xml you are referring to a method saveActionGroup(EditableActionGroup) which is not defined in your remote interface.
Maybe you have made some typo in the configuration. Check your transaction section, i.e.,
<container-transaction>
            <method>
                <ejb-name>ViewBean</ejb-name>
                <method-name>saveActionGroup</method-name>
                <method-params>
                    <method-param>package.EditableActionGroup</method-param>
                </method-params>
            </method>
            <trans-attribute>Required</trans-attribute>
</container-transaction>or something similar. See if the defined methods are corresponding to the methods defined in the remote interface.

EJB 2 : Query in understanding Transaction Attribute NotSupported

NotSupported
The Container invokes an enterprise Bean method whose transaction attribute is set to NotSupported with an unspecified transaction context.
I am having a query in understanding the above thing .Please let me know what does above mean and also what transaction context mean in the below :
If a client calls with a transaction context, the container SUSPENDS the association of the transaction context with the current thread before invoking the enterprise bean's business method.
Thanks in advance .
Waiting for your replies .

it means that the method must operate outside of an active transaction - in other words there will be no active transaction during its runtime. If there is an active transaction when the method is called, that transaction is "put on hold" until the "notsupported" EJB call finishes.

Help-Problem in calling JMS inside an EJB having transaction attribute Required New

          Hi,
          Version wl 5.1 service pack 8
          OS - unix
          I am using a Container managed bean say Bean1(transaction attribute Required)
          which in one of its method is trying to call another EJB say Bean2 which has the
          transaction attribute set to "RequiredNew".Inside the method in Bean2 i have my
          JMS funtions coded to persist to database.JMS uses Queue connection factory and
          is an non transaction JMS session.The JMS server is running in a separate weblogic
          server and not in the server where EJB is deployed.I use the url of the JMS server
          and get the context of that server and connect my JMS.
          The problem that i am facing is
          I do the transaction in bean1 and the i make the call to bean2 to do the JMS work
          and i can see the JMS doing the insert in the table and everthing works fine.But
          after few seconds i can see the exception/message seen on the console of the weblogic
          server where my JMS server is running as below
          Tue Sep 04 15:57:09 CDT 2001:<I> <TX> Transaction (TxC (30486015, xid = 99963563
          2756_5, timeout = 30, txState = Marked Rollback, root = 829817264280676325S10.51
          .110.237:[7001,7001,7002,7002,7001,-1]/326) rolled back after 30 sec.
          After this happen i dont see any roll back in either bean1 or bean2 or the JMS
          insert is rolled back.
          I don't know why this exception is thrown and no effects on the rollback and it
          works the way i wanted.But the only thing that keeps bothering me is the rollback
          and why does this happen.
          Thanks
          Krish.


The exception your seeing is troubling - if the tran is rolled
          back than whatever work is associated should also roll back. I suggest
          instrumenting your code to see if the tran rolling back is the same tran
          that is being used for the transactional application work that appears to succeed.
          Also, try forcing a rollback, you may see that the EJB work truly rolls back
          while the JMS work does not.
          I'm not really familiar with 5.1, but I know there is a fundamental limitation to one
          phase commits, this means that the JDBC connection pool used by JMS as well
          as that used by the EJB must be one and the same - I'm not exactly sure how
          it works, but I'm pretty sure multiple servers can share the same connection pool.
          This post seems unrelated to clustering, if you need further help, I
          suggest posting in the ejb or transaction newsgroups.
          Krish wrote:
          > Hi,
          >
          > Version wl 5.1 service pack 8
          > OS - unix
          >
          > I am using a Container managed bean say Bean1(transaction attribute Required)
          > which in one of its method is trying to call another EJB say Bean2 which has the
          > transaction attribute set to "RequiredNew".Inside the method in Bean2 i have my
          > JMS funtions coded to persist to database.JMS uses Queue connection factory and
          > is an non transaction JMS session.The JMS server is running in a separate weblogic
          > server and not in the server where EJB is deployed.I use the url of the JMS server
          > and get the context of that server and connect my JMS.
          >
          > The problem that i am facing is
          >
          > I do the transaction in bean1 and the i make the call to bean2 to do the JMS work
          > and i can see the JMS doing the insert in the table and everthing works fine.But
          > after few seconds i can see the exception/message seen on the console of the weblogic
          > server where my JMS server is running as below
          >
          > Tue Sep 04 15:57:09 CDT 2001:<I> <TX> Transaction (TxC (30486015, xid = 99963563
          > 2756_5, timeout = 30, txState = Marked Rollback, root = 829817264280676325S10.51
          > 110.237:[7001,7001,7002,7002,7001,-1]/326) rolled back after 30 sec.
          >
          >
          > After this happen i dont see any roll back in either bean1 or bean2 or the JMS
          > insert is rolled back.
          >
          > I don't know why this exception is thrown and no effects on the rollback and it
          > works the way i wanted.But the only thing that keeps bothering me is the rollback
          > and why does this happen.
          >
          > Thanks
          >
          > Krish.

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

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

MDB transaction attributes

Is there a special reason why NotSupported and Required are the only two supported transaction attributes? I understand that MDBs cannot have a client-initiated transaction, but there are other transaction attributes that indicate the same thing.
If an MDB wants to indicate that it should not execute in a transaction, why can't it indicate Never or Supports in addition to NotSupported? In the case of no client-initiated transaction, all three result in the annotated method occuring under no transaction.
If an MDB wants to indicate that it should execute in a transaction, why can't it indicate RequiresNew in addition to Required? Again, in the case of no client-initiated transaction, both result in the annotated method occuring under a transaction.
The Mandatory attribute throws an exception if there is no client-initiated transaction, so clearly that is never appropriate for MDBs. But I am confused as to why the other transaction attributes cannot be used as indicated above.
Please clarify why the specification indicates this about MDB transaction attributes...
Thanks.

When ejb webservice endpoints were introduced in J2EE 1.4 there was no support for
propagation of transaction context over a webservice invocation. Both the JSR 109
spec and the EJB 2.1 spec prohibited the use of MANDATORY on an ejb web
service endpoint since using it was likely a developer error.
In Java EE 5 the restriction against MANDATORY for ejb web service endpoints was removed in the
EJB 3.0 spec. There's still no requirement that transactions be able to flow with web service
invocations but there are some products that support it so the ejb container is no longer
required to throw an exception in that case.
--ken

JDBC, JMS and EJB transactions - possible problem?

Hello,
          I am using Oracle 9, Weblogic 8.1 SP 4, MyEclipse and
          XDoclet.
          In my current project I have the following piece of code
          in one of my message driven beans (code cited as pseudocode
          without unnecessary details):
          * @ejb.bean name="MyMessageProcessor"
          * display-name="Display name for a MyMessageProcessor"
          * jndi-name="ejb/MyMessageProcessor"
          * description="Bean MyMessageProcessor"
          * destination-type="javax.jms.Queue"
          * transaction-type="Container"
          * acknowledge-mode="Auto-acknowledge"
          * subscription-durability="Durable"
          * generate="false"
          * @ejb.transaction type="Required"
          public class MyMessageProcessor implements MessageDrivenBean, MessageListener {
          public void onMessage(Message msg) {
               try {
                    //obtaining connections to two different databases via JNDi
                    java.sql.Connection connOne =
                    ((DataSource)ctx.lookup("DataSourceOne")).getConnection();
                    java.sql.Connection connTwo =
                         ((DataSource)ctx.lookup("DataSourceTwo")).getConnection();
                    // performing some UPDATEs and INSERTs on connOne and connTwo
                    // calling some other methods of this bean
                    //creating the reply JMS message and sending it to another JMS queue
                    Message msgTwo = this.createReplyMessage(msg)
                    this.queueSender.send(msgTwo);
                    //commiting everything
                    this.queueSession.commit();
               } catch (Exception ex) {
               try {
                    if (this.queueSession!=null) this.queueSession.rollback();
               } catch (JMSException JMSEx) {};
               this.context.setRollbackOnly();
          Some days ago (before the final remarks from my client) there used to be only one DataSource configurated on the basis of the
          connection pool with non-XA jdbc driver. Everything worked fine
          including the transactions (if anything wrong happend not only wasn't the replymessage sent, but also no changes were written
          to database and the incomming message was thrown back to the my bean's
          queue).
          When I deployed the second DataSource I was informed by an error message, that only one non-transactional resource may
          participate in a global transaction. When I changed both datasources
          to depend on underlying datasources with transatcional (XA) jdbc drivers, everything stopped working. Even if
          EJB transaction was theoretically successfully rolledbacked, the changed were written to the database
          and the JMS message wasn't resent to the JMS queue.
          So here are my questions:
               1. How to configure connection pools to work in such situations? What JDBC drivers should I choose?
               Are there any global server configurations, which may influence this situation?
               2. Which jdbc drivers should I choose so that the container was able to rollback the database transactions
               (of course, if necessary)?
               3. Are there any JMS Queue settings, which would disable the container to send message back to the
               queue in case of setRollbackOnly()? How should be the Queue configurated?
          As I am new to the topic and the deadline for the project seems to be too close I would be grateful
          for any help.
          This message was sent to EJB list and JDBC list.
          Sincerely yours,
          Marcin Zakidalski

Hi,
          I found these information extremely useful and helpful.
          The seperate transaction for sending messages was, of course, unintentional. Thanks a lot.
          Anyway, I still have some problems. I have made some changes to the
          code cited in my previous mail. These changes included changing QueueSessions
          to non-transactional. I also set the "Honorate global transactions" to true.
          I am using XA JDBC driver. After setting "Enable local transactions" to false
          (I did it, because I assume that JDBC transactions should be part on the global
          EJB transaction) I got the following error:
          java.sql.SQLException: SQL operations are not allowed with no global transaction by default for XA drivers. If the XA
          driver supports performing SQL operations with no global transaction, explicitly allow it by setting
          "SupportsLocalTransaction" JDBC connection pool property to true. In this case, also remember to complete the local
          transaction before using the connection again for global transaction, else a XAER_OUTSIDE XAException may result. To
          complete a local transaction, you can either set auto commit to true or call Connection.commit() or Connection.rollback().
          I have also inspected the calls of methods of bean inside of onMessage() method just to check, whether
          the transactions are correctly initialized (using the weblogic.transaction.Transaction class).
          My questions are as follows:
          1. Any suggestions how to solve it? I have gone through the google answers on that problem and only
          thing I managed to realize that JDBC must start its own transaction. Is there any way to prohibit it
          from doing that? Can using setAutocommit(true/false) change the situation for better?
          2. How to encourage the JDBC driver to be a part of EJB transaction?
          3. As I have noticed each of ejb method has its own transactions (transactions have different
          Xid). Each method of the bean has "required" transaction attribute. Shouldn't it work in such
          way that if already started transaction exists it is used by the called method?
          4. The DataSources are obtained in my application via JNDI and in the destination environment I will have slight
          impact on the configuration of WebLogic. What is least problematic and most common WebLogic configuration which would
          enable JDBC driver to participate in the EJB transaction? Is it the WebLogic configuration problem or can it be
          solved programmically?
          Currently my module works quite fine when "enable local transactions" for DataSources is set to true, but this way
          I am loosing the ability to perform all actions in one transaction.
          Any suggestions / hints are more than welcomed. This message was posted to jdbc list and ejb list.
          Marcin

Transaction attributes

why transaction attributes are not present in JDBC ?
EJB 2.0 Specification includes six defined transaction attributes but JDBC does not carry these . Even the latest JDBC spec does not carry these attributes . Why ?

gimbal2 wrote:
YoungWinston wrote:
user575089 wrote:
EJB 2.0 Specification includes six defined transaction attributes but JDBC does not carry these . Even the latest JDBC spec does not carry these attributes . Why ?I don't know, but I suspect that the transaction attributes are only relevant to EJB. JDBC can be used to execute any piece of SQL on a database, and therefore doesn't have any "model" associated with it (although it does allow you to disable auto-commit). I'm no EJB expert, but I''d suspect that it probably does have a transaction model.
WinstonYes, with exactly six transaction attributes. That is because those attributes are not related to JDBC but to container managed transactions; in other words EJB tech.correct. These are available in EJB tech. However,my point was these are evolved because of necessity ... is not it ?

Can I modify WLI system Bean's transaction attribute --turn on archiver resulting endless exception in log file

hi,erveryone,
one difficult question need help.
Environment: WLS8.1sp2 + WLI8.1sp2 + ORACLE9i + solaris9
when I started archiver manually,just for a while, wli system generated about 40,000 JMS messages in
wli.internal.worklist.timer.queue,and consume the great mass of system resource of Database server,I had to stop these
archive processes immediately to keep other applicaitons which using the same database running normal. I did so by
following steps:
(1) in WLI console, delete wli.internal.worklist.timer.queue;
(2) in WLI console, reconstruct wli.internal.worklist.timer.queue;
(3) restart wli server.
after server was restarted, wli server output endless and repeatly exception to log file ,the typical exception was:
####<May 8, 2005 3:08:26 PM CST> <Info> <EJB> <app01> <jcwliserver> <ExecuteThread: '54' for queue:
'weblogic.kernel.Default'> <<anonymous>> <BEA1-54B26B551CC1A8856F80> <BEA-010049> <EJB Exception in method: remove:
java.sql.SQLException: Transaction rolled back: Unknown reason.
java.sql.SQLException: Transaction rolled back: Unknown reason
     at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1299)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
     at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
     at
com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_loadGroup0(ListenerBean_1nsp14__WebLogic_CMP_R
DBMS.java:1055)
     at
com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
Logic_CMP_RDBMS.java:596)
     at
com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
Logic_CMP_RDBMS.java:584)
     at
com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.ejbRemove(ListenerBean_1nsp14__WebLogic_CMP_RDBMS.j
ava:2423)
     at weblogic.ejb20.manager.DBManager.remove(DBManager.java:1318)
     at weblogic.ejb20.internal.EntityEJBLocalHome.remove(EntityEJBLocalHome.java:214)
     at
com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14_LocalHomeImpl.remove(ListenerBean_1nsp14_LocalHomeImpl.java:131)
     at
com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean.removeTaskListeners(RemoteWorklistManagerBean.java:3001)
     at
com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean_us8t1c_EOImpl.removeTaskListeners(RemoteWorklistManagerBean_us8t
1c_EOImpl.java:698)
     at com.bea.wli.worklist.timer.WorklistTimerMDB.processListenerToRemove(WorklistTimerMDB.java:102)
     at com.bea.wli.worklist.timer.WorklistTimerMDB.onMessage(WorklistTimerMDB.java:61)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
####<May 8, 2005 3:08:26 PM CST> <Info> <EJB> <app01> <jcwliserver> <ExecuteThread: '96' for queue:
'weblogic.kernel.Default'> <<anonymous>> <BEA1-54B96B551CC1A8856F80> <BEA-010049> <EJB Exception in method: remove:
javax.ejb.NoSuchEntityException: [EJB:010140]Bean with primary key: '153.22.52.28-17343c7.10243c3c6ec.a51' not found..
javax.ejb.NoSuchEntityException: [EJB:010140]Bean with primary key: '153.22.52.28-17343c7.10243c3c6ec.a51' not found.
     at
com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_loadGroup0(ListenerBean_1nsp14__WebLogic_CMP_R
DBMS.java:1165)
     at
com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
Logic_CMP_RDBMS.java:596)
     at
com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
Logic_CMP_RDBMS.java:584)
     at
com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.ejbRemove(ListenerBean_1nsp14__WebLogic_CMP_RDBMS.j
ava:2423)
     at weblogic.ejb20.manager.DBManager.remove(DBManager.java:1318)
     at weblogic.ejb20.internal.EntityEJBLocalHome.remove(EntityEJBLocalHome.java:214)
     at
com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14_LocalHomeImpl.remove(ListenerBean_1nsp14_LocalHomeImpl.java:131)
     at
com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean.removeTaskListeners(RemoteWorklistManagerBean.java:3001)
     at
com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean_us8t1c_EOImpl.removeTaskListeners(RemoteWorklistManagerBean_us8t
1c_EOImpl.java:698)
     at com.bea.wli.worklist.timer.WorklistTimerMDB.processListenerToRemove(WorklistTimerMDB.java:102)
     at com.bea.wli.worklist.timer.WorklistTimerMDB.onMessage(WorklistTimerMDB.java:61)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
The wli server generated log file very quickly ,:it can output 1M bytes log file per second,all logged information
is similar to the <BEA-010049> excetpion metioned above. BEA support engineer suggested me to totally stop the
archive ,I did so,but the server was still ouput the log file like crazy as before and the normal log information are
completely override by <BEA-010049> excetpion.
I checked the EntityEJBs in WLI console :Mywlidomain> Applications> WLI System EJBs> WLI Worklist Persistence$)A#,and
found that in statistics table :
ListenerBean : Pool miss ratio = 99.67%, transaction rollback ration = 99.90%,Destory Bean Ratio = 99.48%(see
attachment)
WorklistTimerMDB: transaction rollback ratio = 99.97%
It seems ListenerBean worked incorrectly.I searched in support.bea.com and found one example which also about server
output endless log file,the author solved this problem by changing Bean's transaction-attribute from 'Required'
to 'RequiresNew' thought he didn't know why it works. I try this method by changing ListenerBean's
transaction-attribute from 'Required' to 'RequiresNew'.
$weblogic_home/integration/lib/wli-ejbs.ear/ejb-jar-generic.xml:
<ejb-name>CommentBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>ListenerBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>RequiresNew</trans-attribute> -----------the default value is Required,I modified it to
RequiresNew.
</container-transaction>
<container-transaction>
really it works, the log file output resume normal. But there are still some problems:
(1) this exception is still exist:
javax.ejb.NoSuchEntityException: [EJB:010140]Bean with primary key: '153.22.52.28-17343c7.10243c3c6ec.a51' not found.
(2) is this method safe ?(Does "Modify ListenBean's transaction-attribute" impat other parts of wli system?)
(3) after changed the transaction attribute, if turn on archive again, the server output endless exception:
####<Jun 1, 2005 5:14:58 PM CST> <Info> <EJB> <app01> <jcwliserver> <ExecuteThread: '63' for queue:
'weblogic.kernel.Default'> <<anonymous>> <BEA1-2F43890B86B0A8856F80> <BEA-010036> <Exception from ejbStore:
java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start()
failed on resource 'weblogic.jdbc.jta.DataSource': XAER_RMERR : A resource manager error has occured in the transaction
branch
oracle.jdbc.xa.OracleXAException
     at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1160)
     at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:311)
     at weblogic.jdbc.wrapper.VendorXAResource.start(VendorXAResource.java:50)
     at weblogic.jdbc.jta.DataSource.start(DataSource.java:617)
     at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1075)
     at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1007)
     at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:218)
     at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:419)
     at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1287)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
     at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
     at
com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.__WL_store(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:363
6)
     at
com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.ejbStore(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:3548)
     at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:927)
     at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:745)
     at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010)
     at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
     at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1142)
     at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1868)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:250)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start()
failed on resource 'weblogic.jdbc.jta.DataSource': XAER_RMERR : A resource manager error has occured in the transaction
branch
oracle.jdbc.xa.OracleXAException
     at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1160)
     at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:311)
     at weblogic.jdbc.wrapper.VendorXAResource.start(VendorXAResource.java:50)
     at weblogic.jdbc.jta.DataSource.start(DataSource.java:617)
     at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1075)
     at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1007)
     at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:218)
     at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:419)
     at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1287)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
     at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
     at
com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.__WL_store(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:363
6)
     at
com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.ejbStore(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:3548)
     at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:927)
     at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:745)
     at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010)
     at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
     at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1142)
     at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1868)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:250)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
     at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1292)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
     at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
     at
com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.__WL_store(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:363
6)
     at
com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.ejbStore(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:3548)
     at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:927)
     at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:745)
     at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010)
     at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
     at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1142)
     at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1868)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:250)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
How can I solve these problem ? any suggestion is warm welcome.
Thanks in advance.
Great Lou

Back up all data to at least two different storage devices, if you haven't already done so. The backups can be made with Time Machine or with a mirroring tool such as Carbon Copy Cloner. Preferably both.
Boot into Recovery (command-R at startup), launch Disk Utility, and erase the startup volume with the default options.This operation will destroy all data on the volume, so you had be better be sure of your backups. Quit Disk Utility and install OS X. When you reboot, you'll be prompted to go through the initial setup process. That’s when you transfer the data from one of your backups. For details of how this works, see here:
Using Setup Assistant
Transfer only "Users" and "Settings" – not "Applications" or "Other files." Don't transfer the Guest account, if it was enabled on the old system. Test. If the problem is still there, you have a hardware fault. Take the machine to an Apple Store for diagnosis.
If the problem is resolved, reinstall your third-party software cautiously. Self-contained applications that install into the Applications folder by drag-and-drop or download from the App Store are safe. Anything that comes packaged as an installer or that prompts for an administrator password is suspect, and you must test thoroughly after reinstalling each such item to make sure you haven't restored the problem.
Note: You need an always-on Ethernet or Wi-Fi connection to the Internet to use Recovery. It won’t work with USB or PPPoE modems, or with proxy servers, or with networks that require a certificate for authentication.

Ejb Transaction Attribute

Similar Messages

Maybe you are looking for