Re: Transaction time
Dear All,
My clients has raised a quesry that his user are facing problems while executing a transaction MB5B. This transaction is being required by 10 users at same time with different reporting variants.
The system takes huge time & in many case it even gives dump.
Please advice how to resolve this situation.
I understand there is something in BASIS called performance tuning or Indexing.Can this solve my issue.
Please advice.
Regards,
Vivek
Hi,
This is a standard SAP Transaction.
Basis only can improve the performance.
Check the SAP Early watch Report with Basis (They are the custodians of this report).
Regards,
Siva
Similar Messages
-
Transaction Time out error in EJB while using Websphere Application Server.
Hi All,
I am using Websphere Application server and getting the transaction time out error. By default the transaction time out is 120 second. I am using session bean for doing a set of transaction. These set are dynamically generated. Is there any way to set the transaction time out for only this session bean to infinite ?
Thanks in advance
VivekHi,
According to WAS 6 , every opened connection has to be commited (or rolledback) explicitly (didnt try autocommit) before closing. Even if all you have done with that connection is a SELECT Query.
This has apparently solved the same problem I was getting. implement it and see whether it helps you. -
Hi All,
About my issue ,
A legacy system written in PL/SQL procedures written to process huge chunk of data ( kind of adapter which processes more than 2000 files each invoke updates some tables , which takes around 6 hrs to complete ). and we are trying to invoke those pl/sql procedures to integrate the system with SOA(11G).
We have developed a BPEL communicating to DB through DBadapter ( invokes the required PL/SQL procedures ).
All BPELs used are asynchronous processes . wanted to know how the DB Adapter works . is it a good practice to make the BPEL wait for the pl/sql procedure to return (Though BPEL process is a Asynchronous one) .
Please advice me on this .
Cheers
VamsiVamsi,
I believe configuring Pick activity will not help in this case. If you are configuring a DB adapter in a BPEL process then between the invoke and DB adapter it is a sync call. So try increasing transaction time out period through admin console and let me know the results.
Another option is, remove all activities and services from main BPEL after invoke activity (of DB adapter) and create another BPEL and create the removed activities. Create a concurrent program to invoke the PLSQL procedure and at the end of the procedure call the end point url of the second bpel and send the out variables to this bpel.
Hope this helps
Thanks -
Transaction time out for an single ejb
Hi,
I have one ejb which need to run for long time.
Did a quick search on the forum and find out that you can modify data-source.xml and server.xml to increase the time out period.
But this is a "global" setting which will affect all the ejbs in the application.
Is there a setting where only one ejb's transaction time-out can be specified?
Thanks in advance!
YoungWhat is the exact error code? I.e. the ORA-nnnn error code.
It is not possible to diagnose a problem if the actual problem is not known. Responders are guessing at what the problem is and offering solutions.. and these could be very far of the mark. -
How to extend transaction time on EJBSessionBean method?
Hi,
I am importing some data from XML files, and for that I have several methods in a SessionBean. The import may take several minutes, so with larger sets of data I get "Transaction time out" error. I know I can set transactions to bean-managed (haven't tried it yet, though), but is there a way to set a single method's transaction (in a container-managed-transaction bean) to take all the time it needs?
Thanks,
PedjaOk now it is even worse ir seems to have stopped ringing totally my phone is updated using the latest version of IOS and the ringer is on full I am missing all of my calls!!!! Is there anyone that can help??
-
Transaction aborted (possibly due to transaction time out) - Question
This one is driving me insane!
Bellow you will find the code, the descriptor stuff and the exception. The code belongs to a CMP EJB using CMT (transactions). This gets called from a session bean. Please help.
Here is the code:
public Object ejbCreate( String id )
throws CreateException {
s_logger.debug( "ejbCreate()" ); // this prits
//setId( id );
return null;
public void ejbPostCreate( String id )
throws CreateException {
s_logger.debug( "ejbPostCreate()" ); // this also prints
here is descriptor stuff:
<container-transaction>
<method>
<ejb-name>AgentBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
here is the !@#$ exception (sorry been tracing this one for hours):
RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: Transaction aborted (possibly due to transaction time out).; nested exception is: javax.transaction.RollbackException: Transaction marked for rollback; nested exception is:
javax.transaction.RollbackException: Transaction marked for rollback
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: Transaction aborted (possibly due to transaction time out).; nested exception is: javax.transaction.RollbackException: Transaction marked for rollback; nested exception is:
javax.transaction.RollbackException: Transaction marked for rollback
java.rmi.RemoteException: Transaction aborted (possibly due to transaction time out).; nested exception is: javax.transaction.RollbackException: Transaction marked for rollback; nested exception is:
javax.transaction.RollbackException: Transaction marked for rollback
javax.transaction.RollbackException: Transaction marked for rollback
<<no stack trace available>>It usually means that you're doing something which creates a loop in your locking. Something like setting a value in each instance from an update method of one of the instances. Your posted code doesn't seem to be the trouble, but I could be missing something.
Success,
S. -
Hi,
I have a stateless session bean invoking methods on an entity bean reference.
When 2 methods are invoked using the home reference, I get the following error
Start server side stack trace:
javax.transaction.TransactionRolledbackException: Transaction timed out after
64 seconds
Name=[EJB com.aol.quack.usabilityTools.recTuningBeans.UsabilityReportBean.createFreqReport(java.lang.Str
e=active),properties=({weblogic.transaction.name=[EJB com.aol.quack.usabilityTools.recTuningBeans.Usabil
at weblogic.transaction.internal.TransactionManagerImpl.receiveRequest(TransactionManagerImpl.ja
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:153)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:253)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:220)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy79.findRecognitions(Unknown Source)
at com.aol.quack.usabilityTools.util.FuncLib.processForEachMode(FuncLib.java:190)
at com.aol.quack.usabilityTools.util.FrequencyReport.generate(FrequencyReport.java:128)
at com.aol.quack.usabilityTools.recTuningBeans.UsabilityReportBean.createFreqReport(UsabilityRep
at com.aol.quack.usabilityTools.recTuningBeans.UsabilityReportBean_earfgg_EOImpl.createFreqRepor
at com.aol.quack.usabilityTools.recTuningBeans.UsabilityReportBean_earfgg_EOImpl_WLSkel.invoke(U
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:257)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
Does anyone have idea whats wrong? Is it the code?
The same code works for small tables though.
Thanks,
Priya
I don't think you can call a stored procedure from a CMP. What i meant was you might try calling a stored
procedure from a BMP or a Stateless bean if it is only required to get records from the table.
Shiva.
Priya wrote:
Hi,
How do I get stored procedures to work for container managed bean?
Priya
Shiva Paranandi <[email protected]> wrote:
If it is failing for large data means you need to have an alternate solution
like getting a stored procedure to
pass the results or doing some caching. Or maybe you might even try splitting
the obtained data so your
transactions might spawn for less than 60 seconds. Worst case increase
the time. Also check out what is the
time it takes to get the same data through a sql plus. Check if there
is a huge amount of time difference and
then you might want to see where this time difference is coming from.
Shiva.
Priya wrote:
Hi,
I am using CMP for the entity beans and have already set the timeoutvalue to
60 secs.
Also, this works for small tables but fails for big ones while calling2 finder/home
methods consecutively.
Priya
Shiva Paranandi <[email protected]> wrote:
Does the transaction only involve getting records from the table?
You
can change the transaction time out
value in your ejb's or in the console of WLS. Hope you are using PreparedStatements
in your SQL code. You
might also want to turn on your JDBC log to check out what might behappening.
Shiva.
Priya wrote:
Hi,
I have a stateless session bean invoking methods on an entity
bean
reference.
When 2 methods are invoked using the home reference, I get the followingerror
Start server side stack trace:
javax.transaction.TransactionRolledbackException: Transaction timedout after
64 seconds
Name=[EJB com.aol.quack.usabilityTools.recTuningBeans.UsabilityReportBean.createFreqReport(java.lang.Str
e=active),properties=({weblogic.transaction.name=[EJB com.aol.quack.usabilityTools.recTuningBeans.Usabil
at weblogic.transaction.internal.TransactionManagerImpl.receiveRequest(TransactionManagerImpl.ja
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:153)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:253)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:220)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy79.findRecognitions(Unknown Source)
at com.aol.quack.usabilityTools.util.FuncLib.processForEachMode(FuncLib.java:190)
at com.aol.quack.usabilityTools.util.FrequencyReport.generate(FrequencyReport.java:128)
at com.aol.quack.usabilityTools.recTuningBeans.UsabilityReportBean.createFreqReport(UsabilityRep
at com.aol.quack.usabilityTools.recTuningBeans.UsabilityReportBean_earfgg_EOImpl.createFreqRepor
at com.aol.quack.usabilityTools.recTuningBeans.UsabilityReportBean_earfgg_EOImpl_WLSkel.invoke(U
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:257)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
Does anyone have idea whats wrong? Is it the code?
The same code works for small tables though.
Thanks,
Priya
> > -
Transaction time out after 300 seconds..
Hi guys,
I have very intersting problem. I get transaction time out exception after 300 seconds. I use WLP8.1 SP3. I get this when I try to add a new portlet using admin tool
to home page (which is customized by many users)
Here is the error msg:
<weblogic> <> <BEA-415037> <PortalAdminInstanceManager.addPlaceableToPageInstance() -- java.rmi.RemoteException: EJB Exception: ; nested exception is:
javax.ejb.EJBException: SQL Error while trying to getLayoutDefinition on 2004: SQL [select LAY.MARKUP_DEFINITION_ID, LAY.INTERSECTION_ID, PL.PLACEHOLDER_DEFINITION_ID, PL.MARKUP_DEFINITION_ID, PL.LAYOUT_LOCATION, PL.INTERSECTION_ID, LAY.ICON_URI, LAY.HTML_LAYOUT_URI, LAY.WEBAPP_NAME, LAY.LAYOUT_FILE, LAY.IS_LAYOUT_FILE_DELETED from PF_LAYOUT_DEFINITION LAY, PF_PLACEHOLDER_DEFINITION PL where LAY.LAYOUT_DEFINITION_ID = ? and PL.LAYOUT_DEFINITION_ID = LAY.LAYOUT_DEFINITION_ID] database error code [0] SQL state [null] 040.; nested exception is: java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds
Name=[EJBHi guys,
I have very intersting problem. I get transaction time out exception after 300 seconds. I use WLP8.1 SP3. I get this when I try to add a new portlet using admin tool
to home page (which is customized by many users)
Here is the error msg:
<weblogic> <> <BEA-415037> <PortalAdminInstanceManager.addPlaceableToPageInstance() -- java.rmi.RemoteException: EJB Exception: ; nested exception is:
javax.ejb.EJBException: SQL Error while trying to getLayoutDefinition on 2004: SQL [select LAY.MARKUP_DEFINITION_ID, LAY.INTERSECTION_ID, PL.PLACEHOLDER_DEFINITION_ID, PL.MARKUP_DEFINITION_ID, PL.LAYOUT_LOCATION, PL.INTERSECTION_ID, LAY.ICON_URI, LAY.HTML_LAYOUT_URI, LAY.WEBAPP_NAME, LAY.LAYOUT_FILE, LAY.IS_LAYOUT_FILE_DELETED from PF_LAYOUT_DEFINITION LAY, PF_PLACEHOLDER_DEFINITION PL where LAY.LAYOUT_DEFINITION_ID = ? and PL.LAYOUT_DEFINITION_ID = LAY.LAYOUT_DEFINITION_ID] database error code [0] SQL state [null] 040.; nested exception is: java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds
Name=[EJB -
SMTP Connection Time SMTP Transaction Time warning and mails slow receiving
Hi,
i am getting a warning while testing email server over Mxtoolbox
Waring
SMTP Connection Time 6.661 seconds
SMTP Transaction Time 9.532 seconds - Not good! on Transaction Time
How do i resolve the same
RatheeshHi,
Please refer to the article below about the parameters for the Receive connector. The interesting parameter for the delay seemed to be the tar pit interval.
http://technet.microsoft.com/en-us/library/bb125140.aspx
Then try to run this command below to find out what your tarpitting settings:
get-ReceiveConnector | select name,tarpitinterval
Refer to this thread:
http://social.technet.microsoft.com/Forums/en-US/5680ad62-a7c8-4279-89d5-addab465680d/7925-seconds-warning-on-transaction-time-is-this-a-problem?forum=exchangesvradmin
To know more about SMTP tar pit feature:
http://support.microsoft.com/kb/842851/en-us
Regards. -
In Business One, is the transaction time stored anywhere?
Working with SAP Business One 2005 SP1 PL:29
The accounting team would like to know what time each transaction happened. So far all I can see is the created date and update date on the transactions(OJDT) and in the Change Log (ADJT).
Primarily this is focused around the Journal Entries but it may be needed to AP Transactions.
Thanks
DalenThe Document Posting time is stored in the table but it is not in a directly interpretable format
This is just one ref thread from the SDK forum
Date & Time on Documents
There are many posts. please use search term DocTime / Doc Time and you should find most of them
Suda -
Transaction time out for a simple query
I have a table with 39 million records in the table. When I try to fetch data from teh table with one single where clause. it is raising Transaction timed Out.
What is the best way to fetch full data with out Time Out.
Can we use the first_rows hint to fetch data batch by batch ?
Thanks,
CDWhat is the exact error code? I.e. the ORA-nnnn error code.
It is not possible to diagnose a problem if the actual problem is not known. Responders are guessing at what the problem is and offering solutions.. and these could be very far of the mark. -
How to caluculate total transaction time for a particular service in OSB?
Hi All,
We are using osb 11g in our project.As a part of performance testing we need to caluculate the total time taken for one transaction i.e at the time of invocation of that particular service till completion of that service.Also We need to caluculate the total time taken in intermediatory service callout if at all it is been used.Is there any out of box functionality provided by osb for caluculating the total time taken for each transaction?
Since we are using routing and service callouts in our message,log action will not help us.
Any pointers on the same would be of great help.
Regards,
Roopa MarellaYou can turn on monitoring for OSB proxy services. This out of the box gives you average execution time for the proxy service.
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/operations/monitoring.html -
WebLogic Server 6.1 Transaction Time out Transaction
Hi all,
I got the following time out exception when executing a session bean. However, the exception does not happen every time when being executed.
Original Exception Stack Trace:
javax.transaction.TransactionRolledbackException: EJB Exception: : javax.transaction.TransactionRolledbackException: EJB Exception: : weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1139)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:500)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1629)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:463)
at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1595)
at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1526)
at weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(ServerTransactionImpl.java:450)
at weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:158)
at weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:218)
at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:155)
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:63)
at com.finessealliance.clarity.cts.bfs.TxLogServicesBean_xlsia_EOImpl.execute(TxLogServicesBean_xlsia_EOImpl.java:25)
at com.finessealliance.clarity.cts.tpf.BOEvent.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRule.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl.execute(TransactionRuleBean_fptf06_EOImpl.java:37)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:178)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:268)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:235)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy80.execute(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.executeTransactionRule(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.processMessage(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.run(Unknown Source)
; nested exception is:
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1139)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:500)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1629)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:463)
at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1595)
at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1526)
at weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(ServerTransactionImpl.java:450)
at weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:158)
at weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:218)
at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:155)
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:63)
at com.finessealliance.clarity.cts.bfs.TxLogServicesBean_xlsia_EOImpl.execute(TxLogServicesBean_xlsia_EOImpl.java:25)
at com.finessealliance.clarity.cts.tpf.BOEvent.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRule.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl.execute(TransactionRuleBean_fptf06_EOImpl.java:37)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:178)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:268)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:235)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy80.execute(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.executeTransactionRule(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.processMessage(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.run(Unknown Source)
; nested exception is:
javax.transaction.TransactionRolledbackException: EJB Exception: : weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1139)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:500)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1629)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:463)
at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1595)
at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1526)
at weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(ServerTransactionImpl.java:450)
at weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:158)
at weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:218)
at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:155)
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:63)
at com.finessealliance.clarity.cts.bfs.TxLogServicesBean_xlsia_EOImpl.execute(TxLogServicesBean_xlsia_EOImpl.java:25)
at com.finessealliance.clarity.cts.tpf.BOEvent.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRule.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl.execute(TransactionRuleBean_fptf06_EOImpl.java:37)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:178)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:268)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:235)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy80.execute(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.executeTransactionRule(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.processMessage(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.run(Unknown Source)
; nested exception is:
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
javax.transaction.TransactionRolledbackException: EJB Exception: : weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1139)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:500)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1629)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:463)
at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1595)
at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1526)
at weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(ServerTransactionImpl.java:450)
at weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:158)
at weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:218)
at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:155)
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:63)
at com.finessealliance.clarity.cts.bfs.TxLogServicesBean_xlsia_EOImpl.execute(TxLogServicesBean_xlsia_EOImpl.java:25)
at com.finessealliance.clarity.cts.tpf.BOEvent.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRule.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl.execute(TransactionRuleBean_fptf06_EOImpl.java:37)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:178)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:268)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:235)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy80.execute(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.executeTransactionRule(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.processMessage(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.run(Unknown Source)
; nested exception is:
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1139)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:500)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1629)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:463)
at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1595)
at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+) - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
Xid=15045:f8ea97550ccb4ff4(6456899),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[Thread-25,5,main],SCInfo[******+******]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=******+***.***.***.***:*****+******+, Resources={})],CoordinatorURL=*********.***.***.***:***********+)]
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1526)
at weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(ServerTransactionImpl.java:450)
at weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:158)
at weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:218)
at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:155)
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:63)
at com.finessealliance.clarity.cts.bfs.TxLogServicesBean_xlsia_EOImpl.execute(TxLogServicesBean_xlsia_EOImpl.java:25)
at com.finessealliance.clarity.cts.tpf.BOEvent.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRule.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl.execute(TransactionRuleBean_fptf06_EOImpl.java:37)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:178)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:268)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:235)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy80.execute(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.executeTransactionRule(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.processMessage(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.run(Unknown Source)
at com.finessealliance.clarity.cts.tpf.BOEvent.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRule.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean.execute(Unknown Source)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl.execute(TransactionRuleBean_fptf06_EOImpl.java:37)
at com.finessealliance.clarity.cts.tpf.TransactionRuleBean_fptf06_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:329)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:178)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:268)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:235)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy80.execute(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.executeTransactionRule(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.processMessage(Unknown Source)
at com.finessealliance.clarity.cts.bos.BOServerThread.run(Unknown Source)
Thanks,
KaoruNo, I haven't set the attribute in the weblogic-ejb-jar.xml.
The transaction type of the stateless session bean is container. So, I suppose it uses the JTA time-out value which is now set to 30 secs.
Thanks,
Kaoru -
Materialized view long transaction time
I am using Oracle DB 11g R2 and created a materialized view log WITH SEQUENCE. I need to find out the exact date/time the transaction was made. I see that my MV log has the 'XID$$' column (NUMBER 22), but not sure how to determine the date/time from that. Is there another view/table I can join to get me that info? I see some have 'XID' column but they are RAW(8).
Thanks
Edited by: bobmagan on Feb 27, 2013 11:57 AM- CDC is at least as performant as materialized view logs. If you do asynchronous CDC, it performs better since you're not burdening the source transactions with the overhead of synchronously maintaining the materialized view logs.
- CDC is at least as effective as materialized view logs. Since CDC is designed to publish changes to custom consumers where materialized view logs are designed to be used by Oracle to refresh a materialized view, it strikes me as a much safer solution. If someone comes along and creates a materialized view that starts using your materialized view log, for example, a solution that involves custom code to manipulate the materialized view is almost certainly going to fail.
- CDC isn't an extra cost option so there shouldn't be a cost difference
That leaves the question of simplicity. I'll certainly grant you that a materialized view log solution may appear simpler. But a lot of that simplicity advantage disappears over time. The fact that we're talking about doing things like querying relatively obscure data dictionary tables like all_summap, for example, is added complexity that a CDC-based solution doesn't need. But over time, I'd much rather maintain a CDC-based solution rather than hooking in to materialized view logs. If someone wants to build a materialized view and Oracle happens to be able to use the materialized view log you've created for your own CDC, the custom solution will stop working. Over time, Oracle introduces more and more functionality that allows the ROWID of a row to change (shrinking a table, flashback, etc.). If you're using CDC, Oracle will take care of making sure that all those things are presented to you correctly. If you're rolling your own solution, you have to test and ensure that your code handles all those cases correctly. When Oracle makes a change in some future release that you hadn't considered, you've got to notice the potential problem, code the fix, and test it. Most places are probably going to miss something and only discover that there is a problem when they do something like shrink a table and then find that their custom solution doesn't handle that gracefully.
Justin -
Css11501 - SSl - Speeding up transaction time
HI
We are currently using a css 11501, terminating ssl to a web oracle system.
During the transaction the user may click on a link which is a link to the forms server. Various jar files are then uploaded including Jinitiator plug in.
The users are finding this rather slow ( uploading jinitiator plug-in / jar files), testing has revealed it is taking double the time, than if the user was connecting to the server directly ( Here it would be in HTTP only).
Is caching the way forward?
Which products would be best.
Can anything be done with the css 11501.
Would there be any difference in using a css11503?
Bear in mind the user transaction is ssl.
Any thoughts would be appreciated.11503 and 11501 would have the same performance.
Using a cache would help if the problem was the server.
Apparently this is not the case here.
Did you capture a sniffer trace to see if ther was anything abnormal during the file transfer.
Very low packet size ?
Long delay between packets ?
Regards,
Gilles.
Maybe you are looking for
-
How to include header files from different directories?
Hi, Sorry for the newb question, but I can't figure this out. I'm trying to compile a simple piece of code (C++) that uses header files in a directory different from the Project directory; header files are in /opt/csw/postgresql/include/pqxx. I've tr
-
Very Poor, Poor performance in GarageBand 11
My wife and I are podcasters. We do 3 and I'm a co-host on a 4th. We've used GarageBand since the beginning for recording ('09) and never had an issue. When iLife 11 came out, I saw there was a new version of GarageBand and got pretty exited and geek
-
i don't feel Ant is a good tool to use. i can wrote the batch processing script in a text file and then save it as file with the suffix .bat,such as javac myclass.java java myclass del aDirectory copy aFile bFile while tool Ant can also accomplish su
-
HR sync to LDAP - specify destination OU?
Hi all, <b>Note</b>: We are not using NetWeaver IdM on my project, so the following refers only to tools available in NetWeaver ABAP+Java 7.0. The HR - LDAP sync I talk about has been around since R/3 4.7. I am configuring a scenario to synchronise e
-
Just installed this card, and when I run the installer to install the drivers, it says there is no card detected. Any ideas? Thanks very much..