Setting Application level Transaction Timeout

Hi,
I have seen option in weblogic to set jta transaction time out. Is there a way I specify application level timeout.
Thanks,
Bhargav.

Scott,
Many thanks for the response.
We've found a way around this now, by changing the developer's usernames to the same as their NT/ Active Directory signon, which fools APEX into maintaining the session id from their builder session even though when logging into the application they get authenticated by LDAP.
Using a post authentication process would be ok but I can't see any way of passing a variable retrieved in the authentication process under the first session to the post authentication process so that it can be set in the second session. We'd either therefore have to insert the data into a table and read it back or add an extra LDAP call to retrieve the user role/ group list during the post authentication process.
Thanks again,
Matt

Similar Messages

Setting application level item during authentication

We’re having an issue with an application level item that we set during our custom authentication function to store a role list for authorization. The issue is that the application level item, which should be set using htmldb_util.set_session_state(‘ITEM_NAME’, p_item_value), is not being set.
On further investigation we realised that this issue was only affecting developers, not users of the application. This seems to be because the home page link, set in Shared Components > Edit Security Attributes, is set to “f?p=&APP_ID.:1:&SESSION.”, which means that the developers session was being passed to the application when the “Run Application” button was pressed. What then happens is that following the successful execution of the authentication function, a new session id is generated and visible on the URL and the Application Level Items are not set correctly.
Examples:
I’m developing an application on Apex that has the home page link set to “f?p=&APP_ID.:1:&SESSION.”, here’s the first part of my URL at the Application home page:
http://apex.oracle.com/pls/otn/f?p=4000:1:1065658352862710::
I hit “Run Application” and get to this URL (note the session id is the same)
http://apex.oracle.com/pls/otn/f?p=16033:1:1065658352862710:::::
I log in using any old username and password (the auth scheme on this demo app always returns true) and I get to this URL (note the session id is different):
http://apex.oracle.com/pls/otn/f?p=16033:1:1403999736046638
My application level item is not set and I start to cry. When I recover from my tearful episode I try to log in again, I hit logout and get taken to this URL:
http://apex.oracle.com/pls/otn/f?p=16033:1
I log in again (with the same username or different, it doesn’t matter) and low and behold, my application level item is set ok. This is the URL I can see (note another new session id):
http://apex.oracle.com/pls/otn/f?p=16033:1:4917752800353335
In despair, I close my browser window and go to my other application, this one has got the home page link set to “f?p=&APP_ID.:1” (no session id passed).
I log back into Apex as a developer and go to the application home page at this URL:
http://apex.oracle.com/pls/otn/f?p=4000:1:131988631742187::
I hit “Run Application” and get to this URL (note the session id is missing):
http://apex.oracle.com/pls/otn/f?p=19114:1::::::
I log in using any old username and password (same deal as before) and I get to this URL (new session id):
http://apex.oracle.com/pls/otn/f?p=19114:1:4320851658879093:::::
Amazingly, this time the application level items are set first time.
What I’d like to know (there is a purpose to this) is:
- Why is a different session allocated to the application after login, when a “developer’s” session id is passed to the application?
- If I remove the session id from the home page url what is the impact? I can’t think of anywhere within the application that this is used (other than between page 101 and the home page), but our thoughts are that this could mean that users end up generating more sessions on the server.
- Is there any other way around this, perhaps using a different method of setting the application level item? The authentication procedure which sets the item reads as follows and mimics our authentication procedure (which you can assume does a little bit more than just returning true):
function test_login
(p_username in varchar2 default null,
p_password in varchar2 default null) return boolean is
begin
htmldb_util.set_session_state('F16929_SYSDATE', to_char(sysdate, 'DAY'));
return true;
end;- Has anyone else encountered difficulties with the setting of application level items during login or has anyone come up with a more ingenious plan for passing something back from authentication that can later be used for authorisation?
Thanks
matt

Scott,
Many thanks for the response.
We've found a way around this now, by changing the developer's usernames to the same as their NT/ Active Directory signon, which fools APEX into maintaining the session id from their builder session even though when logging into the application they get authenticated by LDAP.
Using a post authentication process would be ok but I can't see any way of passing a variable retrieved in the authentication process under the first session to the post authentication process so that it can be set in the second session. We'd either therefore have to insert the data into a table and read it back or add an extra LDAP call to retrieve the user role/ group list during the post authentication process.
Thanks again,
Matt

Transaction timeout in BPEL for webservice invocation

[ERROR] [] [oracle.soa.bpel.engine.dispatch] [tid: orabpel.invoke.pool-4.thread-3] [userId: <anonymous>] [ecid: e8538d226bae7c2a:1914e8c0:148c67a5f26:-8000-00000000000031a2,1:27459] [APP: soa-infra] failed to handle message[[
weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds
BEA1-166C02569896A59BE380
                at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1788)
                at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1676)
                at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1988)
                at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1586)
                at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
                at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
                at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
                at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
                at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds
BEA1-166C02569896A59BE380
This is happening when invoking a webservices from BPEL and if it takes more than 5 minutes we are getting above Error
we have tried out SyncMaxWaitTime Property in BPEL configurations through SOA administration menu of EM. Also tried by increasing JTA timeout seconds in Service--JTA @ weblogic console.
Any suggestion or pointers..

Hi,
Could help set the following...
The timeouts should be configured based on the below condition
SyncMaxWaitTime < BPEL EJB's transaction timeout < Global Transaction Timeout
The values could be: SyncMaxWaitTime (3600) ; BPEL EJB's transaction timeout (3600); Global Transaction Timeout JTA (7200)
Setting the SyncMaxWaitTime :
This is the maximum time a synchronous BPEL process waits before it times out to get the response from another BPEL or a web service
Login to EM console
Expand SOA and right click on "soa-infra"
From context menu, select SOA Administration –> BPEL properties
Click on "More BPEL Configuration properties"
Enter the appropriate value for the SyncMaxWaitTime
Setting the global transaction timeout at Weblogic Domain Level:
This property controls the transaction timeout seconds for active transactions. If the transaction is still in the "active" state after this time, it is automatically rolled back.
Log into Oracle Weblogic Administration Console.
Click Services -> JTA.
Change the value of Timeout Seconds to the required value (the default is 30)
Click Save.
Restart Oracle Weblogic Server.
Overriding the transaction timeout setting for BPEL EJB's:
The timeout properties for the EJB's control the particular timeout setting for the SOA application, overriding the global setting specified by the JTA timeout
Log into Oracle Weblogic Administration Console.
Click Deployments.
Expand soa-infra -> EJBs.
Click on the configuration tab for the timeout setting for each of EJB’s listed below and the change the time out values as required.
Following EJBs need to be updated:
BPELActivityManagerBean
BPELDeliveryBean
BPELDispatcherBean
BPELEngineBean
BPELFinderBean
BPELInstanceManagerBean
BPELProcessManagerBean
BPELSensorValuesBean
BPELServerManagerBean
Click Save.
Restart Oracle Weblogic Server.
I hope you find it useful!
hugs!

Set Transaction timeout in Jdeveloper

hi,
I am using Jdeveloper 11.1.1.5 with JPA2.0. Is there an option where i can set the JTA Timeout for the integrated WLS server.
I know how to do it using the Web Console, however Id like to be able to do it either from a Jdeveloper setting or maybe a configuration file.
Any help is much appreciated.
Thanks

what is Transaction timeout in ATGTransaction timeout is related to application server. For more detail see below urls:
http://docs.oracle.com/cd/E36434_01/Platform.10-1-2/ATGEndecaIntegrationGuide/html/s0106increasingthetransactiontimeouta01.html
http://docs.oracle.com/cd/E24152_01/Platform.10-1/ATGInstallGuide/html/s0406settingthetransactiontimeoutonwe01.html
http://docs.oracle.com/cd/E24152_01/Platform.10-1/ATGInstallGuide/html/s0406settingthetransactiontimeoutonjb01.html
-RMishra
Edited by: RMishra on Mar 14, 2013 5:53 PM
Edited by: RMishra on Mar 14, 2013 6:10 PM

How to set a page template as an "application level default template"?

Hi,
For some reason, my default application level page template is not 'default' anymore. is there a way to set that? Thanks.

See Home>Application Builder>Application 999999>Shared Components>Themes>Create / Edit
Jeff

Acrobat or Reader: Is there a way to set the print scaling default at the application level?

Is there a way to set the Page/Print Scaling to a default at the application level? For Acrobat and Reader?
Thanks,

Often asked, but that feature retains the last used local setting.
You can however, change the default for Documents, individually, in their Properties > Advanced tab

Set item value from application level item

Hello,
I'm using Apex 2.2.1.00.04. I've modified the Page "No Tabs" template so that I can have my own Form (which is submitted to an outside website). On this form, I create some hidden items:
<form name="frmEPay" method="POST" action="some_website">
<input type="hidden" id="i1" name="userId" value=&G_ID. />
<input type="hidden" id="i11" name="timestamp" value="" />
<input type="hidden" id="i12" name="hash" value="" />
On this apex page, I have a javascript function which is called in the onload (basically, the ApEx webpage displays and then is redirected). Here's a snippet of that function:
var appProc = new htmldb_Get(null, html_GetElement('pFlowId').value,'APPLICATION_PROCESS=PrepEPay',0);
appProc.get();
appProc = null;
document.getElementById('i11').value = "&G_ECOM_TIMESTAMP.";
document.getElementById('i12').value = "&G_HASH.";
document.frm_infiNET.submit();
As you can see, the function calls an application level On Demand process (PrepEPay). That process sets the values of the application level items G_ECOM_TIMESTAMP and G_HASH. After those App level items have their values, I want to take those values and apply them to the hidden items on my custom form. Unfortunately, it doesn't work how I have things currently. I've verified that the On Demand process is running(by viewing the Session report on the page). So my problem seems to be this: 1. Retrieving the values from the Apex application level items
2. Setting those values to the values of my hidden items (on my custom form)
I think the biggest reason why I'm having difficulties is because I have to do a lot of this in the template, since that is the only way to have a separate Form. Maybe my problem is that I don't understand how to reference the Apex application level item value from a different form?
Thanks,
Marty

Marty,
You are describing this as if you expect the substitution within "&G_ECOM_TIMESTAMP." and the other one to take place in some kind of lexical order, e.g., from the top to the bottom of the HTML. The replacements happen in the engine, before anything is sent to the page. Then the browser interprets language constructs such as javascript calls which in your case includes an ajax invocation of a server-side application process.
You need to re-think the machinery here.
Scott

Change Default Application level setting for checkbox value from "On"/"Off" to 1/0

Hi,
I am creating livecycle designer forms. In that the checkboxes take a default value of "On'/"Off" and I have to change it to 1 and 0 in all the boxes on layout checkbox property.
In livecycle i have to change it in Object-Binding tab.
Is there an application level setting where I can set the default to 1 and 0 instead of "on/"off" at the app level itself? this way every new form will have 0 and 1 instead of off/on
I export the form data to XML and push it to database and it needs 1 and 0.
I need the app setting for both Adobe Acrobat 9 Extended Pro
Please help

It is 1/0 by default .....if you drag a checkbox from the object library onto the canvas and you are getting on/off as your default, then you have modified th eobject. You can set the object the way you want (anf property not just binding) and then you can drag the object back onto the Library palette. This will ask you to name it and if you choose the same name it will overwrite the one that is in the library.
Paul

OSB Customization files 2 set Retry Application Errors and Timeout props

I know it's possible to set Endpoint URI, Retry Count and Retry Iteration Interval properties using customization files, but what about other properties? I am particularly interested in setting Retry Application Errors and Timeout for a HTTP business services. If it's not possible to do with customization files is there another way of setting them without having to go though each service in the console?
Edited by: user1019490 on Sep 23, 2010 2:45 AM

Yes, I guess this can be done as there is provision in ALSBCustomizationFile.xml. Below is the snippet from ALSBCustomizationFile.xml
<cus:envValueAssignments>
<xt:envValueType>Service URI Table</xt:envValueType>
<xt:location xsi:nil="true"/>
<xt:owner>
<xt:type>BusinessService</xt:type>
<xt:path>TestProject/BusinessService/TestBS</xt:path>
</xt:owner>
<xt:value>
<tableElement xmlns="http://www.bea.com/wli/sb/transports">
<URI>http://www.test.com/testService.asmx</URI>
<weight>0</weight>
</tableElement>
</xt:value>
</cus:envValueAssignments>
<cus:envValueAssignments>
<xt:envValueType>Service Retry Count</xt:envValueType>
<xt:location xsi:nil="true"/>
<xt:owner>
<xt:type>BusinessService</xt:type>
<xt:path>TestProject/BusinessService/TestBS</xt:path>
</xt:owner>
<xt:value xsi:type="xs:string" xmlns:xs="http://www.w3.org/2001/XMLSchema">0</xt:value>
</cus:envValueAssignments>
<cus:envValueAssignments>
<xt:envValueType>Service Retry Iteration Interval</xt:envValueType>
<xt:location xsi:nil="true"/>
<xt:owner>
<xt:type>BusinessService</xt:type>
<xt:path>TestProject/BusinessService/TestBS</xt:path>
</xt:owner>
<xt:value xsi:type="xs:string" xmlns:xs="http://www.w3.org/2001/XMLSchema">0</xt:value>
</cus:envValueAssignments>
Regards,
Karthik

JTF_UM_APPROVAL_URL is set at iStore and OM application level but no URL in email

Hi,
JTF_UM_APPROVAL_URL is at iStore and OM application level as per implementation guide. But still in workflow mailer we are getting following messages:
URL: 3012: Illegal characters found in 'https://abc.com:443/<< Please define the URL for the application login in the JTF_UM_APPL_URL profile option >>'.
Thanks
Ashish

Hello Ashish,
If you had referenced to OA_HTML/ in the profile option url setting, replace this with the virtual directory mapped to the JSP file location.
Regards,
Debbie

BMT and transaction timeout

Hello,
Does anybody knows what the behavior should be for a Session EJB with BMT (using JTA) after a transaction timeout? Does the container performs a database rollback for you immediately after the time-out event? I’ve noticed that JBoss does not perform a rollback but Web does. What do the J2EE specs say what should happen?
We are experiencing database locks in an Oracle database caused by ‘hanging’ JTA-transactions which aren’t removed after a timeout. An application server restart will remove them. We are trying to find the cause, there fore I’am posting this message.
Regards,
Marteyn Heijlaerts

          "Laurel Neustadter" <[email protected]> wrote:
          >
          >Hi:
          >
          >The WLS 6.0 documentation states that for a CMT bean, one specifies the
          >transaction
          >timeout in weblogic-ejb-jar.xml, and for a BMT bean, one specifies the
          >transaction
          >timeout via UserTransaction.setTransactionTimeout().
          >
          >You also set a transaction timeout attribute at the domain level. How
          >does the
          >domain level attribute work into all of this? How is it used?
          >
          >For example, if a transaction timeout value is not specified at the bean
          >level,
          >will the domain level value be used?
          >
          >Laurel
          Yes, the domain level timeout is the default.
          It is overridden by any setting at the EJB level. This in turn
          can be overridden by the client calling the EJB, if the client
          starts a transaction and uses
          transactionManager.setTransactionTimeout()

Session time out when working in application level

Hi
We are upgraded our PROD environment from 11.5.10.2 to R12.1.3
When end user working at application level then it is throughing the session time out error, end user is not idle state he active and working on application level
I have checked the profile ICX:Session Timeout it is 30
Thanks
Shaik

Hi;
Please see:
ICX:SESSION TIME OUT
Re: Inccreasing the timeout parameter for the Oracle R12 session
Also see:
How AutoConfig sets ICX: Session Timeout [ID 307149.1]
How To Manage Timeout at Responsibility Level [ID 412224.1]
Regard
Helios

Transaction timeouts behaviour - explanation needed

Hello all,
I'm a newbie to Weblogic and would like to understand how transaction timeouts work in Weblogic. I have a EJB2 application running under Weblogic 10.3 and using Oracle 11g database via thin jdbc driver.
I noticed that if I set trans-timeout-seconds in deployment descriptor it terminates sql queries if they overflow the limit. Say I have timeout set to 10 seconds, it will stop executing sql query after that time and immediately return exception to caller of the current EJB method. This is just perfect!
What I want is to understand how that is done, does it proxy driver somehow? Will it work with other databases, Postgresql for example?
Can I port same behavior to other app servers, JBoss for example.
Thank you in advance.

Unfortunately, it seems to work different in JBoss7. I created a very simple app and it waits until end of query execution instead of interrupting it.
I'm porting application from weblogic to JBoss7 and it is critical for me to achieve identical behavior.

Transaction Timeout (BPEL v10.1.2.0.0, WebLogic 8.1 sp4)

We are attempting to process a transform on a medium sized xml doc (~4.5 MB). For the test case we are simply reading the the doc using the FileAdapter, performing a transformation, and then writing the result to a file using the FileAdapter once again. The flow works fine for smallish files (under ~4MB), however, when dropping a file greater than that size the flow fails once finished while writing entries to the BPEL audit log with a TransactionTimedOutException (see exception below).
I understand what is happening and why (it certainly takes longer than 2 mins to process the file). I have also done quite a bit of digging around for references to this issue and found several posts regarding bumping the transaction timeout value when running the OC4J container. My problem is that we are not running the OC4J container. I know how to manage the default transaction timeout value for WebLogic but it appears that the BPEL application doesn't seem to be honoring the default transaction timeout on the WL Server. I have come to this conclusion for two reasons: first, the default transaction timeout on the WL Server (before modification) is 30 seconds, not the 120 seconds that this transaction is timing out on. second, changing the transaction timeout value on the WebLogic server has no impact on this issue what so ever. I can set the transaction timeout to any value I like, the process ALWAYS times out after 120 seconds.
Is there another setting on the BPEL server that I may have missed that is overriding the default timeout, i.e. is it possible that when the BPEL server process is starting the transaction it is setting the timeout on the TransactionManager in code prior to starting the transaction?
Any pointers are greatly appreciated.
------------- START STACK TRACE ------------------
<2007-03-15 13:50:24,625> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "cube delivery": Cannot insert audit trail.
The process domain was unable to insert the current log entries for the instance "10601" to the audit trail table. The exception reported is: The transaction is no longer active - status: 'Rolled back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 120 seconds
Name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)],Xid=BEA1-0021B65431A170F9CFEF(31469464),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=120,seconds left=60,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread Group for Queue: 'default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=ended,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@154d033,re-Registered = false),SCInfo[f58_integration+orabpelServer]=(state=active),properties=({weblogic.transaction.name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)], weblogic.jdbc=t3://127.0.0.1:9700}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+, XAResources={},NonXAResources={})],CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+)]'. No further JDBC access is allowed within this transaction.
Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
sql statement: INSERT INTO audit_trail( cikey, domain_ref, count_id, block, block_csize, block_usize, log ) VALUES( ?, ?, ?, ?, ?, ?, ? )
<2007-03-15 13:50:24,643> <ERROR> <default.collaxa.cube.engine.dispatch> <BaseScheduledWorker::process> Failed to handle dispatch message ... exception ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 120 seconds
Name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)],Xid=BEA1-0021B65431A170F9CFEF(31469464),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=120,seconds left=60,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread Group for Queue: 'default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=ended,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@154d033,re-Registered = false),SCInfo[f58_integration+orabpelServer]=(state=active),properties=({weblogic.transaction.name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)], weblogic.jdbc=t3://127.0.0.1:9700}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+, XAResources={},NonXAResources={})],CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+)
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1614)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1117)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1881)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1034)
at weblogic.transaction.internal.WLSTimer.trigger(WLSTimer.java:31)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
; nested exception is: weblogic.transaction.internal.TimedOutException: Transaction timed out after 120 seconds
Name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)],Xid=BEA1-0021B65431A170F9CFEF(31469464),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=120,seconds left=60,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread Group for Queue: 'default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=ended,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@154d033,re-Registered = false),SCInfo[f58_integration+orabpelServer]=(state=active),properties=({weblogic.transaction.name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)], weblogic.jdbc=t3://127.0.0.1:9700}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+, XAResources={},NonXAResources={})],CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+)
------------- END STACK TRACE ------------------

Hi
i am facing a similar problem..did u find the solution for this problem?
Please pass the solution/workaround u performed for solving this...
Thanks & Regards
Subramanian

Tuxedo calls procedure and Application Level Service Failure

hello ,professors all!
My Tuxedo Service just call an procedure exists in oracle9i, i am sure that the procedure runs ok in oracle9i individually, when it was called by my tuxedo service , it is not ok by first time ,and runs out tp application level Service failure error .But strangely it is ok by second time！
who can explan it to me and show me a way to solve the difficult problem?
i spend a lot time wondering the answer!
Edited by: user9086437 on 2010-9-29 下午9:57

There are many possible reasons why a database procedure might fail the first time it is executed and succeed after that.
You should check the Tuxedo ULOG and Oracle database logs for any messages that may point to the problem.
If there is a LIBTUX_CAT:6205 or LIBTUX_CAT:6206 message in the userlog file then you need to add a tx_open() call to your server's tpsvrinit() or tpsvrthrinit() function.
If there is an OPENINFO string for the group where your server is running then you are using XA transaction management and should not be connecting to the database in your application code; if there is not an OPENINFO string for the group where your server is running then you need to connect to the database in your application.
If you set the environment variable
TMTRACE=*:ulog:dye
for the server where the failure is happening then Tuxedo will write a trace record of each Tuxedo call and each XA call to the ULOG file. This can be helpful in determining why the failure is happening on the first call, especially if Tuxedo is handling transaction management using XA.
I hope some of this is of help in debugging the problem.
Ed

Setting Application level Transaction Timeout

Similar Messages

Maybe you are looking for