CMR and Transaction Attribute

I got two ReadOnly CMP entity beans with a 1:N relationship, and one session facade,
all with the TX attribute of NotSupported. When I tried to get the CMR collection
in the session bean, WebLogic 6.1 SP3 threw an EJBException saying the CMR collection
could not be accessed outside a TX context. Only by changing the TX attribute
of the SLSB to Required (left the CMP bean TX attribute unchanged) could I get
the collection. What is the reason behind this behavior? I want the caching
feature of the ReadOnly beans but do not want ot pay any price for transactions.
Is this possible?

I do one more test and found
UPDATE exception raised when I have foreign key in table. If I use only plain fild evething is ok. If add to entity foreign key field container raise exception when it try to update record.

Similar Messages

Compound attribute and transactional attribute

hi experts,
what is compound attribute and transactional attribute, in what case we will use this attributes, can anybody explain with business scenario, pl help to understand this.
thanks & regards
venkat

Coumpounding attributes is an attribute which is compounded with another infoobject. This brings unique data relationship. Suppose u have company codes like CC1, CC2, CC3 and you have employees E1, E2, E3...The employees codes will be same in each company code. To make them unique across we compound the employeee code with company code. The it will result as below.
CC1 - E1, E2, E3
CC2 - E1, E2, E3
CC3 - E1, E2, E3
Again the other one must be a transitive attribute and not transactional attribute. When an navigational acts as another attribute as navigational attribute then the other is called transitive attribute.

CMP and Transaction Attribute

Hi All!
I try to play with cmp entity beans. All I try to do is find instance and call one from the methods.
When I use transaction attribute another than "Required", I get exception 25222. Application module creation exception.
If I change attribute to "Required New" then I get error while bean try to UPDATE record.
I can't understand why this update appear on findByPrimaryKey!
Can any body give some information on JBO behavior?
Mike
null

I do one more test and found
UPDATE exception raised when I have foreign key in table. If I use only plain fild evething is ok. If add to entity foreign key field container raise exception when it try to update record.

Diff B/W master data and transaction data

Hi all,
What is the main Diff B/W master data and transaction data. give me some example ?
Thanks in Advance
Krish...

hi krish,
MASTER Data is the data that exists in the organization like employee details, material master, customer master, vendor master etc. These are generally created once.
Master data are distributed throughout the company, they are often not standardised and often redundant. As a result it is very costly to offer efficient customer service, keep track of supply chains and make strategic decisions. With SAP Master Data Management (SAP MDM) these important business data from across the company can be brought together, harmonised and made accessible to all staff and business partners. As a key component of SAP NetWeaver, SAP MDM ensures data integrity via all IT systems.
Regardless of the industry, companies often work with different ERP and Legacy systems. The result: the business processes are based on information about customers, partners and products which is displayed in different ways in the systems. If the data are recorded manually, there are more inconsistencies: some data sets are entered several times, others cannot be retrieved by all divisions of the company.
As corporate applications are becoming increasingly complex and produce ever greater amounts of data, the problem is intensified further. Nevertheless, your employees must work with the inconsistent data and make decisions on this basis. The lack of standardised master data easily leads to wrong decisions, which restrict efficiency and threaten customer satisfaction and profitability.
In a word: in order to save costs and ensure your companys success it is necessary to consolidate master data about customers, partners and products, make them available to all employees beyond system boundaries and use attributes valid company-wide for the purpose of description.
TRASNACTION Data - These are the business documents that you create using the master data - Purchase orders, sales orders etc
http://help.sap.com/saphelp_nw2004s/helpdata/en/9d/193e4045796913e10000000a1550b0/content.htm
Regards,
GNK.

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

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 ?

What happens internally while loading master data and transaction?

hello,
What happens internally and which tables are used while loading master data and transaction?
I have loaded the data in DSO, but i am not getting value of particular InfoObject after loading the data.
I have executed Attribute change run also.
Kindly explain ...
Thanks,
Sonu

Hi,
Master data,
Material Indipendent data can be sent without any dependency.
Material Dependent data sequence is as follow.
Plant,
MRP areas,
Supply area,
Material,
MRP area material,
planning material,
ATP check,
Purchase info recards,
schedule agg,
PPM or PDS (But before PPM or PDS work center should send to apo) If PDS is sending then BOM should send before PDS.
Transaction data.
As per the business requirement what is planning in apo.
Regards,
Kishore Reddy.

Transaction Attribute issue in weblogic 8.1

Hi,
I have problem with the transaction attribute of my session bean in Weblogic8.1 and SQLServer. Following is the description.
I have two beans, say SampleBeanOne and SampleBeanTwo. The transaction attribute of SampleBeanOne is "Required" and that of the SampleBeanTwo is "RequiresNew".
In SampleBeanOne i am trying the execute the a batch of insert quires using PreparedStatement.addBach() and PreparedStatement.executBatch() in a loop that runs of 5 times.
Inside the loop i am calling a method in SampleBeanTwo to get the next sequence. In that method i am updating the squence and selecting the new value.
Now the problem i am facing is that when i call the executeBatch() in the PreparedStatement only the final insert statement added to the batch is called and the insert statement added gets vanished.
If i change the transaction attribute of the SampleBeanTwo to "Required" the code is working fine. But i can't do that since the SampleBeanTwo is accessed throught out my application.
The same peace of code is working properly with Websphere5 and SQL server combination.
Kindly help me out in this issue.
Regards

Hi
ThanX for your reply. I raised the issue to the BEA support, they said that the issue is the driver that i am using. It got resolved when i tried with the BEA provided driver. They call it the BEA branded driver for SQL Server.
Regards
Muthu

Develop a report to migrate territories and its attributes

Hi All,
My requirement -> create territories, assign BP and attributes to it through a custom report. Using BAPI BAPI_TERRITORY_CREATE I manage to create territories but assign BP and Attributes i did not find any FM and BAPI. kindly guide me how i can assign BP and Attributes to a territories.
By debugging transaction crmm_terrman i found some FMs but not working for me.
regards,
Noor Gani

Hello Noor,
I'm not sure but if you are talking about the marketing attributes, you can definitely use FM - CRM_MKTBP_ASSIGN_ATTRIBUT_TAB
You need to pass the profile id, partner id and marketing attributes data. Thats it.
I think the FM you ar eusing for terrritory is fine. It should work.
I hope this helps.
Thanks
Vishal

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.

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.
          >

Line Item Dimension and Navigational attribute

Hi Gurus,
Can somebody tell me how line item Dimensions and navigational attributes works technically?
What are the pros and cons for them?
Regards
Alex

Hi Alex,
You will use navigational attributes based on how you want to track and report history. Let me explain with an example.
Customer Bubba is assigned Sales Group XYZ in Jan 2007. In July the Sales Group on the Customer Master record is changed to ABC. Your are looking at the sales report.
1). If you want to see all the sales made to Customer Bubba at the time of reporting (current) then you will use navigational attributes You will create 0SALESGRP as the navigational attribute of 0CUSTOMER . Then all sales to the customer will show up under Sales Group ABC.
2). If you want to see all the sales made to the customer at the time the actual transaction occured then you will add Sales Group as a characteristic of the InfoCube. Then sales from Jan - June 2007 will show under Sales Group XYZ and from July - Present will show under Sales Group ABC.
Performance issue occurs because navigational attribute is stored outside of the dimension table of the cube and is stored in separate master data tables. So query has to perform additional table read. So essentially there are advantages and disadvantages of usng navigational attributes. It is business requirement that will drive the use of navigational attribute.
Hope this helps!!!. Please assign points.

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

JBDC transaction attribute problem.

Hi All,
We have some methods which will make a call to database to bring some data
using SELECT statement. Have set transaction attribute for those methods as NOT SUPPORTED not to open a transaction and lock the table. But, now it is opening a transaction & locking table & rows.
Any idea why it is doing so ?

normally a select statement will not lock the table
unless you are using a PreparedStatement or
CallableStatement class to perform the query. I don't believe this is correct. I don't think either PreparedStatement or CallableStatement automatically lock tables.
If you
are then it should be an expected behavior. if you
are not using any of this classes make sure to check
that you have not lock the table with the statement
connection.setAutoCommit(false);
this
statement usually locks the table whether you are
using a select statement or not. I don't think this is true, either. This tells the Connection where a transaction starts.
But if these are not
the cause then make sure that you close all
connections when the query has finished executing.
that is connection.close();I think the correct way to tell the database manager to lock data is to use "SELECT FOR UPDATE" notation.
%

Transaction attribute in XML deployment descriptor

Hi,
I just want to know the use of transaction attributes like (Required, notSuuport etc..) are in the EJB.
What is Bean managed and container managed transaction.
How we use the transaction attributes in BMP and CMP.
and in similar fashion, the use of the same in Session beans.
..Aman

modification to the above quesion::
There are 5 different beans named as
CMP, BMP, Stateless, Stateful and MDB.
I want to know that which all transactions (CMT or BMT) can be applied for which bean?
I just got some feedback from some ppl that i cant apply BMT for CMP and BMP. if that is true then why???
if i can apply CMT for CMP and BMP then how i will modify the EJB-jar for the
method definitiion for CMP and BMP. I mean to say the method name and parameter definition. as there are only call back methods.
..Aman

CMR and Transaction Attribute

Similar Messages

Maybe you are looking for