Long running onMessage() method

I have an application in which the onMessage() method implemented within an MDB would never complete. The onMessage() method calls a bean which executes in a while(TRUE) loop.
If I were to use CMT to control my MDB, the message would not be dequeued from the JMS server till the onMessage() method completes. What is the impact of this never ending transaction on the JMS provider and container(Weblogic 7.0)? I realize this is something which should be avoided and would be better handled using a bean managed MDB. But I need the rollback facility provided by a container managed MDB to be able to automatically put the message back into the Q if for some reason the MDB or the server hosting it failed.
Thanks

You m,ust use a Startup class

Similar Messages

Long running DBAdapter partnerlink activities (transactions)

Hello,
I try to use nonBlockingInvoke = true for long running DBAdapter partnerlink activities,
but i'm not succesfull.
In BPELConsole the activity seems to be running, but there is an entry
in Manual Recovery > Activity TAB and OraBPEL~OC4J_BPEL~default_island~1
log says:
<2006-02-10 09:32:05,130> <INFO> <test.collaxa.cube.ws> <AdapterFramework::Outbound> file:/ora/app/oracle/product/bpel/integration/orabpel
/domains/test/tmp/.bpel_ZalozeniObjednavky_1.2.jar/ZapisObjednavky.wsdl [ ZapisObjednavky_ptt::ZapisObjednavky(InputParameters) ] - Using
JCA Connection Pool - max size = <unbounded>
<2006-02-10 09:32:05,390> <ERROR> <test.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "cube engine": Callback in
vocation failed.
An attempt to invoke the method "handleCallback" on the performer "bpel.p0.BPEL_BIN$$BPELC_BpInv0" failed. The reported exception is: "".
Please ensure that the signature of the method "handleCallback" is: ( IWorkItem, ICubeContext ).
<2006-02-10 09:32:05,406> <ERROR> <test.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.instance.CallbackInvokerMessage";
the exception is: Callback invocation failed.
An attempt to invoke the method "handleCallback" on the performer "bpel.p0.BPEL_BIN$$BPELC_BpInv0" failed. The reported exception is: "".
Please ensure that the signature of the method "handleCallback" is: ( IWorkItem, ICubeContext ).
Does anybody succeed with nonBlockingInvoke = true on DBAdapter partnerlink?
I use BPEL 10.1.2 patch02
Thank you
Karel

Hi Jon,
 
 
You can set the maxConnections which represents the Maximum number of connections in the pool in oc4j-ra.xml.
Please refer to the section Oracle Application Server Adapter for Databases in Oracle® BPEL Process Manager Developer's Guide
for more information.
 
 
Aruna

ORABPEL-05002 for long running process

Hi everybody,
My question is related with a long running process I have designed and which, after running for a couple of days, ends by reporting the ORABPEL-05002 error:
===============================================================
ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.PerformMessage"; the exception is: Transaction was rolled back: timed out; nested exception is: java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
 java.lang.Exception: No Exception - originate from:
 at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:152)
 at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
 at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
 at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
 at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
 at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
 at java.lang.Thread.run(Thread.java:534)
===============================================================
Looking in the Manual Recovery screen, I can see an Activity I can recover. It's about an assign Activity where I'm doing a single boolean assignation.
Of course, together with the ORABPEL-05002 error I got also the 'Transaction was rolled back: time out' message. Note that I have modified the transaction-timeout value to 180000. The error occurs during the night, with no heavy load of the server.
Recovering the assign activity brings back the process in the running state.
My process pattern:
while (1 == 1) {
do activity;
wait_timeout();
So, I have the following questions:
1. Which is cause of this error?
2. How may I automatically recover this lost activity? RecoveryAgent?
Any suggestion is appreciated.
Regards,
amo
P.S: the full stack of error messages reported in domain.log:
===============================================================
<2006-09-18 08:08:34,101> <ERROR> <SRH.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> failed to handle message
javax.ejb.EJBException: Transaction was rolled back: timed out; nested exception is: java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
 java.lang.Exception: No Exception - originate from:
java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
 java.lang.Exception: No Exception - originate from:
 at com.evermind.server.ejb.EJBUtils.makeException(EJBUtils.java:873)
 at ICubeEngineLocalBean_StatelessSessionBeanWrapper0.handleWorkItem(ICubeEngineLocalBean_StatelessSessionBeanWrapper0.java:1479)
 at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handle(PerformMessageHandler.java:45)
 at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
 at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
 at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
 at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
 at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
 at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
 at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.Exception: No Exception - originate from:
 at com.evermind.server.ejb.EJBUtils.makeException(EJBUtils.java:871)
 ... 10 more
javax.ejb.EJBException: Transaction was rolled back: timed out; nested exception is: java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
 java.lang.Exception: No Exception - originate from:
 at ICubeEngineLocalBean_StatelessSessionBeanWrapper0.handleWorkItem(ICubeEngineLocalBean_StatelessSessionBeanWrapper0.java:1479)
 at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handle(PerformMessageHandler.java:45)
 at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
 at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
 at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
 at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
 at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
 at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
 at java.lang.Thread.run(Thread.java:534)
<2006-09-18 08:08:34,129> <ERROR> <SRH.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.instance.PerformMessage"; the exception is: Transaction was rolled back: timed out; nested exception is: java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
 java.lang.Exception: No Exception - originate from:
ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.PerformMessage"; the exception is: Transaction was rolled back: timed out; nested exception is: java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
 java.lang.Exception: No Exception - originate from:
 at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:152)
 at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
 at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
 at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
 at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
 at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
 at java.lang.Thread.run(Thread.java:534)
<2006-09-18 08:09:05,236> <ERROR> <SRH.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "activity manager": Scope not found.
The scope "BpSwt2.30995" has not been defined in the current instance.
ORABPEL-02094
Scope not found.
The scope "BpSwt2.30995" has not been defined in the current instance.
 at com.collaxa.cube.engine.core.ScopeContext.getScope(ScopeContext.java:213)
 at com.collaxa.cube.engine.core.WorkItem.setCubeInstance(WorkItem.java:259)
 at com.collaxa.cube.engine.core.WorkItemFactory.init(WorkItemFactory.java:68)
 at com.collaxa.cube.engine.core.WorkItemFactory.create(WorkItemFactory.java:58)
 at com.collaxa.cube.engine.adaptors.common.BaseWorkItemPersistenceAdaptor.load(BaseWorkItemPersistenceAdaptor.java:147)
 at com.collaxa.cube.engine.data.WorkItemPersistenceMgr.load(WorkItemPersistenceMgr.java:75)
 at com.collaxa.cube.engine.CubeEngine.load(CubeEngine.java:5185)
 at com.collaxa.cube.engine.CubeEngine.load(CubeEngine.java:5173)
 at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:2136)
 at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:145)
 at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:116)
 at IActivityManagerLocalBean_StatelessSessionBeanWrapper52.expireActivity(IActivityManagerLocalBean_StatelessSessionBeanWrapper52.java:645)
 at com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessageHandler.handle(ExpirationMessageHandler.java:43)
 at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
 at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
 at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
 at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
 at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
 at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
 at java.lang.Thread.run(Thread.java:534)
<2006-09-18 08:09:05,274> <ERROR> <SRH.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> failed to handle message
ORABPEL-02094
Scope not found.
The scope "BpSwt2.30995" has not been defined in the current instance.
 at com.collaxa.cube.engine.core.ScopeContext.getScope(ScopeContext.java:213)
 at com.collaxa.cube.engine.core.WorkItem.setCubeInstance(WorkItem.java:259)
 at com.collaxa.cube.engine.core.WorkItemFactory.init(WorkItemFactory.java:68)
 at com.collaxa.cube.engine.core.WorkItemFactory.create(WorkItemFactory.java:58)
 at com.collaxa.cube.engine.adaptors.common.BaseWorkItemPersistenceAdaptor.load(BaseWorkItemPersistenceAdaptor.java:147)
 at com.collaxa.cube.engine.data.WorkItemPersistenceMgr.load(WorkItemPersistenceMgr.java:75)
 at com.collaxa.cube.engine.CubeEngine.load(CubeEngine.java:5185)
 at com.collaxa.cube.engine.CubeEngine.load(CubeEngine.java:5173)
 at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:2136)
 at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:145)
 at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:116)
 at IActivityManagerLocalBean_StatelessSessionBeanWrapper52.expireActivity(IActivityManagerLocalBean_StatelessSessionBeanWrapper52.java:645)
 at com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessageHandler.handle(ExpirationMessageHandler.java:43)
 at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
 at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
 at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
 at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
 at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
 at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
 at java.lang.Thread.run(Thread.java:534)
<2006-09-18 08:09:05,275> <ERROR> <SRH.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.instance.ExpirationMessage"; the exception is: Scope not found.
The scope "BpSwt2.30995" has not been defined in the current instance.
ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessage"; the exception is: Scope not found.
The scope "BpSwt2.30995" has not been defined in the current instance.
 at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:152)
 at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
 at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
 at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
 at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
 at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
 at java.lang.Thread.run(Thread.java:534)
===============================================================

These are the possible cause to the problem and their solutions:
Poor performance of the dehydration database If you are using Oracle Lite as dehydration store, please switch to use Oracle 9i or 10g. If Oracle 9i/10g is already in use, check the database parameter 'process' and 'session' to make sure it can handle the expected throughput.
OC4J has too few available connections to the dehydration database. Increase the maxConnection number of the BPELServerDataSource at the BPEL_HOME/integration/orabpel/system/appserver/oc4j/j2ee/home/config/data-sources.xml (for developer edition) or IAS_HOME/j2ee/OC4J_BPEL/config/data-sources.xml (mid-tier installation).
Size of message is too big Two ways to deal with this problem:
Increase the transaction timeout at PEL_HOME/integration/orabpel/system/appserver/oc4j/j2ee/home/config/server.xml (developer edition) or IAS_HOME/j2ee/OC4J_BPEL/config/server.xml (mid-tier installation)
Decrease the auditLevel from BPELConsole -> Manage BPEL Domain -> Configurations tab. Doing so will reduce the amount of data saved to the dehydration store.
Cheers
Anirudh Pucha

No display due to long running Actions

Hi,
I have a small issue in my application.
Please help providing the solution for the following problematic scenario faced in my application.
My project is generally a report generation project,
arch used: our-own architecture(similar to struts)
Server: deployed in tomcat server..
On clicking a button from X.jsp, it triggers the action with the request = REQ1
so in my configuration Xml file it checks for it and executes the corresponding Action classes and it should display the Presentation(Jsp)
What happens is , the action class execution is taking more than 10 min, becaz of which i am getting blank screen.
From the action to jsp , it is executing without any error, which i could see in the log files..
Actions taken:
improved the performance of the query, but cudnt reduce much time..
session time is 180min, and connection timeout set to an hr. - No change- It seems this doesnt have to do anything with this.
my Observance:
I guess, as per arch, it is executing till jsp, but it seems that HttpRequest is getting timedout becaz of long running actions.
Please help to find the cause and approach method to resolve this issue.
Note: no issues to wait till 10min.. but need to get the values (reports) in the screeen..
Thanks in advance.....

Design is inappropriate.
Long running processes, and specifically reports, shouldn't rely on session connections.
Instead the following should be done.
- Process initiation (user request), post a task request to a task request queue. Return a unique identifier to requestor.
- Separate process processes tasks in the task queue.
- Requestor (such as a gui) periodically polls using the indentifier to see if the task is complete.
- When the task is complete the requestor asks for the results (GUI displays them.)
The problem with extending timeouts is that there are valid error scenarios where long timeouts will mean resources not returned to the system for long periods of time when they should have been.
Per your current solution there is probably some other timeout somewhere. Could be several. The JSP forum might be a better place to ask where all of the possible timeouts could be.

No response due to long running Action classes

Hi,
I have a small issue in my application.
Please help providing the solution for the following problematic scenario faced in my application.
My project is generally a report generation project,
arch used: our-own architecture(similar to struts)
Server: deployed in tomcat server..
On clicking a button from X.jsp, it triggers the action with the request = REQ1
so in my configuration Xml file it checks for it and executes the corresponding Action classes and it should display the Presentation(Jsp)
What happens is , the action class execution is taking more than 10 min, becaz of which i am getting blank screen.
From the action to jsp , it is executing without any error, which i could see in the log files..
Actions taken:
improved the performance of the query, but cudnt reduce much time..
session time is 180min, and connection timeout set to an hr. - No change- It seems this doesnt have to do anything with this.
my Observance:
I guess, as per arch, it is executing till jsp, but it seems that HttpRequest is getting timedout becaz of long running actions.
Please help to find the cause and approach method to resolve this issue.
Note: no issues to wait till 10min.. but need to get the values (reports) in the screeen..
Thanks in advance.....

It sounds like either the server or perhaps a firewall is timing out after 5 minutes or so. If you can examine the log files for each such machine in the network, you might find that one is reporting a timeout. If this is the case, you can change the timeout to something greater than 5 minutes, but this is not advisable. Other applications should rightfully timeout if they 'hang' for more than 5 minutes or so and you don't want to interfere with that. One possible solution is to look up something like 'jsp keepalive' to see how to get the JSP page to periodically send a message to the server to keep the session alive using something like AJAX. I tried this and I couldn't find anything that worked. Another thing you can do is do performance tuning to speed things up, or only fetch a small subset of data for the user at a time by filtering (example: instead of returning the entire telephone book, have the user select A to Z for last name and only return the last name that begins with that letter. Another possibility is to cache the data and read from the cache. Then, periodically, refresh the cache from the database at say, midnight every night. Those are the only ideas I have.

Issue in Visual Notification During Long Running Transactions

Hi,
I am using Jdev 11.1.1.5.0 for developement.
In my application i am having af:table. in that table i am having a column as af:selectBooleanCheckbox. My Need is avoid clicking a selectBooleanCheckbox twice or changing data input while waiting for a long running process to complete. I follows Frank Nimphius have written articles in the past http://www.oracle.com/technetwork/developer-tools/adf/learnmore/27-long-running-queries-169166.pdf but my appliaction i use af:clientListener component for af:selectBooleanCheckbox. when i click the checbox in table, popup(progress popup) is not opening and it also allow user to enter some other data in my page.
Pls help...
- Vinoth

In Jsff
<af:resource type="javascript">
 function enforcePreventUserInput(evt) {
 var popup = AdfPage.PAGE.findComponentByAbsoluteId('progressId');
 if (popup != null) {
 AdfPage.PAGE.addBusyStateListener(popup, handleBusyState);
 evt.preventUserInput();
 function handleBusyState(evt) {
 var popup = AdfPage.PAGE.findComponentByAbsoluteId('progressId');
 if (popup != null) {
 if (evt.isBusy()) {
 popup.show();
 else if (popup.isPopupVisible()) {
 popup.hide();
 AdfPage.PAGE.removeBusyStateListener(popup, handleBusyState);
</af:resource>
<af:popup id="progressId" contentDelivery="immediate">
 <af:dialog id="dcx2" type="none" title="Long Running Process ..."
 closeIconVisible="false">
 <af:panelGroupLayout id="pgl1dd" layout="vertical">
 <af:image source="/images/left" id="isdfs1"/>
 <af:image source="/images/animbar.gif" id="idf2"
 inlineStyle="width:197px;"/>
 <af:outputText value="... please wait" id="odfg11"/>
 </af:panelGroupLayout>
 </af:dialog>
</af:popup>
{noformat}within af:table{noformat}
<af:column sortProperty="SeriesID" align="center" width="54px"
 headerText=" " id="c22">
 <af:selectBooleanCheckbox autoSubmit="true" label="select" id="sbc2"
 binding="#{pageFlowScope.MyBean.applicableValue}"
 valueChangeListener="#{pageFlowScope.MyBean.onValChngofChkBox}">
 <af:clientListener method="enforcePreventUserInput" type="click"/>
 </af:selectBooleanCheckbox>
 </af:column>

Query on long running client import process

Hi Gurus,
I have few queries regarding the parameter PHYS_MEMSIZE. Let me brief about the SAP server configuration before I get into the actual problem.
We are running on ECC 6.0 on windows 2003, SP2 - 64 bit and DB is SQL 2005 with 16GB RAM and page file configured 22 GB.
As per the Zero Administration Memory management I have learnt as a rule of thumb, use SAP/DB = 70/30 and set the parameter PHYS_MEMSIZE to approximately 70% of the installed main memory. Please suggest should I change the parameter as described in zero administration memory guide? If so what are the precautions we should take care for changing memory parameters. Are there any major dependencies and known issues associated to this parameter?
Current PHYS_MEMSIZE parameter set to 512 MB.
Few days ago we had to perform the client copy using EXPORT / IMPORT method. Export process was normal and went well However the import process took almost 15 HRs to complete. Any clues what could be the possible reasons for long running client copy activity in SQL environment. I am suspecting the parameter PHY_MEMSIZE was configured to 512 MB which appears to be very low.
Please share your ideas and suggestions on this incase if anyone have ever experienced this sort of issue because we are going to perform a client copy again in next 10 days so i really need your inputs on this.
Thanks & Regards,
Vinod
Edited by: vinod kumar on Dec 5, 2009 9:24 AM

Hi Nagendra,
Thanks for your quick response.
Our production environment is running on ACtive/Active clustering like One central Instance and Dialog Instance. Database size is 116 GB with 1 data file and log file is 4.5 Gb which are shared in cluster.
As suggested by you if I need to modify the PHYS_MEMSIZE to 11 or 12 GB(70% of physical RAM). What are the precautions should I consider and I see there are many dependencies associated with this parameter as per the documentation of this parameter.
The standard values of the following parameters are calculated
According to PHYS_MEMSIZE
em/initial_size_MB = PHYS_MEMSIZE (extension by PHYS_MEMSIZE / 2)
rdisp/ROLL_SHM
rdisp/ROLL_MAXFS
rdisp/PG_SHM
rdisp/PG_MAXFS
Should I make the changes to both Central and dialog instance as well. Please clarify me,. Also are there any other parameters should i enhance or adjust to speedup the client copy process.
Many Thanks...
Thanks & Regards,
Vinod

Cancel long running statement in Oracle Lite (OLITE_10.3.0.3.0 olite40.jar)

On JDBC statement, there is the method 'cancel' to instruct the database to cancel an executing statement. This works fine on Oracle server database, but not on Oracle lite database. The method call 'cancel' just blocks and the running statement is never interrupted.
The example I tried is very simple. There is a thread started which executes a long running statement. I noticed, that when moving the cursor forward by calling rs.next(), it just blocks. That would be ok, if the statement could be canceled from within the main thread by stmt.cancel. But this call blocks as well with no implact on the running statement. Why is that? Do I miss something or is it not possible to cancel a long running statements in Oracle Lite?
In the following my code snipped:
public class CancelStatement {
     private static final String PATH_DB = "XX";
     private static final String PATH_LIB = "XX";
     private static final String CON_STRING = "jdbc:polite:whatever;DataDirectory=" + PATH_DB + ";Database=XX;IsolationLevel=Read Committed;Autocommit=Off;CursorType=Forward Only";
     private static final String USER = "XX";
     private static final String PASSWORD = "XX";
     public static void main(String args[]) throws Exception {
          System.setProperty("java.library.path", PATH_LIB);
          Class.forName("oracle.lite.poljdbc.POLJDBCDriver");
          Connection con = DriverManager.getConnection(CON_STRING, USER, PASSWORD);
          Statement stmt = con.createStatement();
          Thread thread = new Thread(new LongStatementRunnable(con, stmt));
          thread.start();
          Thread.sleep(3000);
          // stop long running statement
          System.out.println("cancel long running statement");
          stmt.cancel(); // XXX does not work, as call is blocked until out of memory
          System.out.println("statement canceled");
     private static class LongStatementRunnable implements Runnable {
          private Connection con;
          private Statement stmt;
          public LongStatementRunnable(Connection con, Statement stmt) {
               this.con = con;
               this.stmt = stmt;
          @Override
          public void run() {
               try {
                    System.out.println("start long running statement...");
                    // execute long running statement
                    ResultSet rs = stmt.executeQuery("SELECT * FROM PERSON P1, PERSON P2");
                    while (rs.next()) { // here the execution gets blocked
                         System.out.println("row"); // is never entered
                    rs.close();
                    stmt.close();
                    con.close();
                    System.out.println("long running statement finished...");
               } catch (Exception e) {
                    e.printStackTrace();
}I would be very glad if you could help me.
Thanks a lot
Daniel
Edited by: 861793 on 26.05.2011 14:29

Unfortunately Oracle Lite doesn't have this option. You can call your statement from a second thread as you have done, but you won't be able to kill or cancel this operation. The only way to get fix this is by rebooting. You can use process explorer to find the dll process that is executing the SQL, but the tables will be locked and sync would be locked as well until the process is finished running in shared memory.

Using MDBs for long running transactions

Although MDBs are not the best vehicles for running long transactions, I am
 forced to use them for one such scenario (let's say for lack of a better
 pattern). In order to let my long running MDB (with Container Managed Tx)
 do it's chores I increased the time-out value to a higher number rather than
 using the default of 30 secs. Strangely, I was seeing
 IllegalStateExceptions in stdout. So I created a brand new test MDB with a
 Thread.sleep for 60 seconds, increased my MDBs timeout value to 120 secs,
 made sure there was only one MDB in the pool and ran the test again. I
 still see the below error after 30 seconds.
 I guess I should probably open a support case, but I thought I'll post here
 as well in case there's something I am missing.
 <May 27, 2003 5:26:31 PM PDT> <Notice> <EJB> <Error marking transaction for
 rollback: java.lang.IllegalStateException: Cannot m
 ark the transaction for rollback. xid=64:bea55f200db2c786, status=Rolled
 back. [Reason=weblogic.transaction.internal.TimedOutEx
 ception: Transaction timed out after 34 seconds
 Xid=64:bea55f200db2c786(-33600248),Status=Active,numRepliesOwedMe=0,numRepli
 esOwedOthers=0,seconds since begin=34,seconds left=
 30,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread
 Group for Queue: 'default'],ServerResourceInfo[JMS_hmJD
 BCStore]=(state=started,assigned=none),SCInfo[wlcsDomain+wlcsServer]=(state=
 active),OwnerTransactionManager=ServerTM[ServerCoor
 dinatorDescriptor=(CoordinatorURL=wlcsServer+155.14.3.140:7501+wlcsDomain+,
 Resources={})],CoordinatorURL=wlcsServer+155.14.3.1
 40:7501+wlcsDomain+)]
 java.lang.IllegalStateException: Cannot mark the transaction for rollback.
 xid=64:bea55f200db2c786, status=Rolled back. [Reason
 =weblogic.transaction.internal.TimedOutException: Transaction timed out
 after 34 seconds
 Xid=64:bea55f200db2c786(-33600248),Status=Active,numRepliesOwedMe=0,numRepli
 esOwedOthers=0,seconds since begin=34,seconds left=
 30,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread
 Group for Queue: 'default'],ServerResourceInfo[JMS_hmJD
 BCStore]=(state=started,assigned=none),SCInfo[wlcsDomain+wlcsServer]=(state=
 active),OwnerTransactionManager=ServerTM[ServerCoor
 dinatorDescriptor=(CoordinatorURL=wlcsServer+155.14.3.140:7501+wlcsDomain+,
 Resources={})],CoordinatorURL=wlcsServer+155.14.3.1
 40:7501+wlcsDomain+)]
 at
 weblogic.transaction.internal.TransactionImpl.throwIllegalStateException(Tra
 nsactionImpl.java:1486)
 at
 weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImp
 l.java:466)
 at
 weblogic.ejb20.manager.BaseEJBManager.handleSystemException(BaseEJBManager.j
 ava:255)
 at
 weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:21
 5)
 at
 weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:153)
 at
 weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:117)
 at
 weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java
 :63)
 at
 com.xoriant.hm.ejb.session.HierarchyManagerBean_fzysig_EOImpl.getHierarchyId
 (HierarchyManagerBean_fzysig_EOImpl.java
 :1477)
 at
 com.ebiz.application.customerprofile.hm.CPXHMController.SynchronizeMHTH(Unkn
 own Source)
 at
 com.ebiz.application.customerprofile.hm.CPHMOrgGroupMsgBean.onMessage(Unknow
 n Source)
 at weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)


Hi Adarsh,
 It may be that the transaction time-out setting in the descriptor
 is not taking effect. The tx is still timing out after
 the default 30 seconds, so the later attempt to call
 "setRollbackOnly" fails as the transaction has already
 rolled back The ignored descriptor setting is a known issue
 in some earlier SPs, but I'm not sure when and where it
 was fixed - so yes, contact customer support. The work-around
 is to set the default transaction time-out for the entire server to a
 higher value. (I'm not sure where to set this on the console,
 but the relevant JTA MBean field is "TimeoutSeconds".)
 Tom
 Adarsh Dattani wrote:
 > Although MDBs are not the best vehicles for running long transactions, I am
 > forced to use them for one such scenario (let's say for lack of a better
 > pattern). In order to let my long running MDB (with Container Managed Tx)
 > do it's chores I increased the time-out value to a higher number rather than
 > using the default of 30 secs. Strangely, I was seeing
 > IllegalStateExceptions in stdout. So I created a brand new test MDB with a
 > Thread.sleep for 60 seconds, increased my MDBs timeout value to 120 secs,
 > made sure there was only one MDB in the pool and ran the test again. I
 > still see the below error after 30 seconds.
 > I guess I should probably open a support case, but I thought I'll post here
 > as well in case there's something I am missing.
 >
 > <May 27, 2003 5:26:31 PM PDT> <Notice> <EJB> <Error marking transaction for
 > rollback: java.lang.IllegalStateException: Cannot m
 >
 > ark the transaction for rollback. xid=64:bea55f200db2c786, status=Rolled
 > back. [Reason=weblogic.transaction.internal.TimedOutEx
 >
 > ception: Transaction timed out after 34 seconds
 >
 > Xid=64:bea55f200db2c786(-33600248),Status=Active,numRepliesOwedMe=0,numRepli
 > esOwedOthers=0,seconds since begin=34,seconds left=
 >
 > 30,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread
 > Group for Queue: 'default'],ServerResourceInfo[JMS_hmJD
 >
 > BCStore]=(state=started,assigned=none),SCInfo[wlcsDomain+wlcsServer]=(state=
 > active),OwnerTransactionManager=ServerTM[ServerCoor
 >
 > dinatorDescriptor=(CoordinatorURL=wlcsServer+155.14.3.140:7501+wlcsDomain+,
 > Resources={})],CoordinatorURL=wlcsServer+155.14.3.1
 >
 > 40:7501+wlcsDomain+)]
 >
 > java.lang.IllegalStateException: Cannot mark the transaction for rollback.
 > xid=64:bea55f200db2c786, status=Rolled back. [Reason
 >
 > =weblogic.transaction.internal.TimedOutException: Transaction timed out
 > after 34 seconds
 >
 > Xid=64:bea55f200db2c786(-33600248),Status=Active,numRepliesOwedMe=0,numRepli
 > esOwedOthers=0,seconds since begin=34,seconds left=
 >
 > 30,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread
 > Group for Queue: 'default'],ServerResourceInfo[JMS_hmJD
 >
 > BCStore]=(state=started,assigned=none),SCInfo[wlcsDomain+wlcsServer]=(state=
 > active),OwnerTransactionManager=ServerTM[ServerCoor
 >
 > dinatorDescriptor=(CoordinatorURL=wlcsServer+155.14.3.140:7501+wlcsDomain+,
 > Resources={})],CoordinatorURL=wlcsServer+155.14.3.1
 >
 > 40:7501+wlcsDomain+)]
 >
 > at
 > weblogic.transaction.internal.TransactionImpl.throwIllegalStateException(Tra
 > nsactionImpl.java:1486)
 >
 > at
 > weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImp
 > l.java:466)
 >
 > at
 > weblogic.ejb20.manager.BaseEJBManager.handleSystemException(BaseEJBManager.j
 > ava:255)
 >
 > at
 > weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:21
 > 5)
 >
 > at
 > weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:153)
 >
 > at
 > weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:117)
 >
 > at
 > weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java
 > :63)
 >
 > at
 > com.xoriant.hm.ejb.session.HierarchyManagerBean_fzysig_EOImpl.getHierarchyId
 > (HierarchyManagerBean_fzysig_EOImpl.java
 >
 > :1477)
 >
 > at
 > com.ebiz.application.customerprofile.hm.CPXHMController.SynchronizeMHTH(Unkn
 > own Source)
 >
 > at
 > com.ebiz.application.customerprofile.hm.CPHMOrgGroupMsgBean.onMessage(Unknow
 > n Source)
 >
 > at weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
 >
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 >
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 >
 >
 >
 >

Long running statement

Hi,
Is there any way to find out the long running statement from the previous night batch program?
Thanks

Another method is by using OEM.
1) Click on the performance tab, switch to historical selection from the drop down View Data on top right corner.
2) Scroll down to Additional Monitoring Links and select Period SQL. Use the selector at bottom of top graph to the spike in activity. Again the heavy SQL will show.
3) Click the SQL in question by examining CPU and elapsed times. Use the plan hash value to select from v$sql or v$sqltext if required. Check the SQL plan and tuning information if available.
4) From 2 above you an also schedule SQL Tuning or SQL Access advisor.

Should EntryProcessors be used for long-running operations?

Hi Gene and All,
     a couple of other questions come from the seemingly unexhaustible list :-)
     - what happens if the caller of an InvocableMap.invokeAll or invoke method dies?
     - all entryProcessors complete regardless of the client being there or not
     - all already started process method calls complete, the unprocessed entries will not get processed
     - something else happens
     - what happens if the caller of an InvocableMap.aggregate method with a parallel-aggregator dies
     - all aggregate methods in the parallel-aggregator complete
     - the aggregate methods in the parallel-aggregator stop during processing
     - something else happens
     - should an entryprocessor or a parallel-aware entryaggregator implement a comparably long-running operation (e.g. jdbc access), or does that seriously affect performance of other concurrent operations within the cluster node or the entire cluster (e.g. becuase of blocking other events/requests)?
     - should the work manager be used instead for these kinds of things (e.g. jdbc access)?
     Thanks and best regards,
     Robert

Robert,
     As soon as an EntryProcessor or EntryAggregator get delivered to the server nodes, it will get executed regardless of the requestor's state.
     In regard to long-running operations the only thing you have to be conscious about is a number of worker threads allocated for such a processing. Since there is a single client thread issuing a request, it would suggests allocation as many worker threads (across the cache server tier) as there are client thread (across the presentation/application tier).
     Regards,
     Gene

Long running servlet in a single node of a cluster

Good evening,
I am developing a J2EE application that consists of a number of web services that perform background processing of relatively long-running jobs. Status of the jobs actually need to be reported back to the SAP ABAP system, which we do via JCo. All communication back to ABAP occurs in a single long-running, JMS driven servlet. This callback servlet uses both a timestamp (last time status was sent back) or a count of status events to determine when to send data to the ABAP system.
All of this works great in a single Java instance J2EE configuration. However, when we introduce clustering into the configuration, we get one instance of the callback servlet per J2EE server process. Is there an easy way to configure the servlet so that it only runs on a single J2EE server process in one instance?
TIA,
- Bill

Hi Bill,
Launching manually threads even from a web container is also not recommended as good J2EE practice.
If each applications launches its own set of threads that may easily crash the server. Another drawback of such long running servlet is that you are blocking application thread from the server. One last point - it seems that you are storing the data in the servlet at some intermediate variables without any persistance. What will happen if the server crashes ? Can you afford to loose the data ?
I am not implying that you launch threads from the MDB. I am just saying that you could define that single MDB and send messages directly to it. You do the job there inside the onMessage, no new thread. You will be guaranteed that no other call will be executed. You are guaranteed nothing will be lost in case server crashes, you will not use resources even if there is no traffic.
Btw, please feel free to give me a phone call or write an email to further discuss the issue. You can take the details from your CSN I am currently processing
Best Regards
Peter

ProgressIndicator and hourglass for long running processes

Hi all,
Iam using Oracle ADF 10g with EJBs.
I have a long running process for which I want to give the user an indication of its progress. The process is run upon clicking a submit button.
I have tested the use of the combination of progressIndicator + poll according to the example of Gerger consulting( http://gergerconsulting.blogspot.com/2007/04/adf-faces-progressindicator-example-for.html) but it did not work. The problem is that my long running process hangs the page and the progress bar does not work until the process has finished.
I have seen a similar post in this foum (Re: How to run long background jobs in ADF applications where a user complains that there is not an Oracle method for running asynchronous processes from Oracle ADF.
I've tested to isolate my asynchronous process with the progressIndicator + poll in a single ADF page. The process is being activated from an invokeAction from the executables of the pagedef file. But again the process hangs the page and the progressIndicator does not display at all.
So I have abandoned the idea of the progress indicator and Iam thinking of using an hourglass.
Is there an example or guidelines of how I can do it?

Thanks John for your reply,
Iam still working on the progressIndicator. I have read the discussion thoroughly quite many times.
One thing I have not yet figured out from your discussion is how you manage to create the long-running-process thread within an action method within the managed bean and make the thread still be active, while the parent action method has finished.
Usually the managed beans attached to a .jspx pages has request scope. So a commandButton's action method (that will spawn the long running thread) will finish much earlier than the thread and it will kill the thread.
Thanks,
Dimitris

How can i cancel long running queries (red x doesnt work)

hi there
i am trying to work with some long running queries - it would be very nice to be able to cancel them (like toads cancel button)
I have tried the red X in the circle but it doesnt seem to work - it appears to have cancelled it (the cylon-eye style comfort bar stops ocillating) but if i try to use the connection again, or disconnect or open another connection it says:
"connection currently busy. Try again?"
i have tried this in the latest release vanilla & the latest release plus patch 2
thanks
Martin

Good news that this will be improved. Can't resist to post this Link: [plsql forum thread about start/stop.. | http://forums.oracle.com/forums/thread.jspa?forumID=75&threadID=927697]
I have experienced the same and also noted that it feels better to execute stored procedures in sqldeveloper
- by editing
- compiling (might hang if already busy)
- run from the same dialog just to get the the cylon's eye for emergency stops (which waits .... ) meanwhile jump to apex to fiddle with small table triggering exception to stop the procedure.
If stored procedure is executed from the list via 'right mouse click'-style then you see in the log-region "connecting to databse ... ." but no method to stop nor cancel or cylon's eye is well hidden.
When such "busy" is running I also noted that the database-connection right mouse click has greyed/inactivated the selections "connect/disconnect" so the next logical step for stopping via "disconnect" is out of the question.
I think this also boils down also to question whether the user has rights to see gv$session and be able to drop/stop busy/jamming sessions. E.g. public synonyms listing has small icons with mystic red :)
/paavo
Java(TM) Platform 1.6.0_14
Oracle IDE 1.5.4.59.40

Cancel long running queries

Hi Folks,
Is it possible to submit a SELECT statment using OraSqlStmt object and retrieve the data so generated?
I want to submit a long-running SELECT query against Oracle, and have the option to cancel the query.
I can submit the query asynchronously NONBLK option of OraSqlStmt and then be able to cancel it. However, I also want to display the dataset returned by the query. But I think it is not possible to create a dataset / recordset or dynaset using OraSqlStmt.
THe question is:
How can I submit a long running Select query, be able to cancel it and if the query is not cancelled then be able to display the records in a grid? I am using VB6.
Thanks

Good news that this will be improved. Can't resist to post this Link: [plsql forum thread about start/stop.. | http://forums.oracle.com/forums/thread.jspa?forumID=75&threadID=927697]
I have experienced the same and also noted that it feels better to execute stored procedures in sqldeveloper
- by editing
- compiling (might hang if already busy)
- run from the same dialog just to get the the cylon's eye for emergency stops (which waits .... ) meanwhile jump to apex to fiddle with small table triggering exception to stop the procedure.
If stored procedure is executed from the list via 'right mouse click'-style then you see in the log-region "connecting to databse ... ." but no method to stop nor cancel or cylon's eye is well hidden.
When such "busy" is running I also noted that the database-connection right mouse click has greyed/inactivated the selections "connect/disconnect" so the next logical step for stopping via "disconnect" is out of the question.
I think this also boils down also to question whether the user has rights to see gv$session and be able to drop/stop busy/jamming sessions. E.g. public synonyms listing has small icons with mystic red :)
/paavo
Java(TM) Platform 1.6.0_14
Oracle IDE 1.5.4.59.40

Long running onMessage() method

Similar Messages

Maybe you are looking for