Dialog process time out !!!

Hi experts,
I am trying to execute a function Module(with RFC) that triggers a dialog process. Now the system time out limit for a dialog process is 10 mins and my process is taking longer than that, hence its giving a "Time Out" dump. Is there a way to that can avoid this system time limit for a dialog process?
Please suggest!!!
Thanks.
Note : I tried running in background but didn't work.

>
ankit harjai wrote:
> Note : I tried running in background but didn't work.
Hello Ankit,
Can you elaborate what do you mean by "running in background"? Did you use IN BACKGROUND TASK / IN BACKGROUND UNIT
addition while calling the RFC?
BR,
Suhas

Similar Messages

Parallel processing time out error

Hi All,
I am working on a scenario where in I am spawning two different parallel processe in a background job to calculate some entitlements.
My problem is even when running the main program in background mode the parallel processes are always spawned in a new dialog work process as a result of which if the dialog processes run for more than 15 minutes I get a time out error for the parallel jobs.
I understand that we cannot use the addition IN BACKGROUND TASK while doing the function call as we need the result from the function calls in the main program.
Is there any way where I can call parallel jobs in a background workprocess or override the time out issue without changing the system parameter value.
Any suggestions would be greatly appreciated.
Regards,
Narsingh.

Hi Narsingh,
By any chance did you got the solution, it would be great if you could share the solution for the issue you faced.
Regards,
Neerup

BPEL process times out after 5 minutes

Hi,
I have created a BPEL Asynchronous process that is invoking a view which takes time to give all the records; while the process is invoking this database adapter, my process abruptly ends with the following fault after 5 minutes
Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'CAMPAIGN_BATCH_COUPONS_VSelect' failed due to: DBReadInteractionSpec Execute Failed Exception. Query name: [CAMPAIGN_BATCH_COUPONS_VSelect], Descriptor name: [CAMPAIGN_BATCH_COUPONS_V.WcCampaignBatchCouponsV]. Caused by java.sql.SQLTimeoutException: ORA-01013: user requested cancel of current operation . See root exception for the specific exception. This exception is considered retriable, likely due to a communication failure. Because the global transaction is rolling back the invoke must be retried in a new transaction, restarting from the place of the last transaction commit. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "1013" to your deployment descriptor (i.e. weblogic-ra.xml). ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
It looks like my process is timed out. Is there anything that I can do for it to not time out like this?
Can anybody please help me on this?
Thanks in advance.
Edited by: user1165407 on Sep 6, 2011 4:19 PM

Hi Naresh,
Before the transaction was rollback issue it got failed while invoking the DBAdapter and it is showing the below issue:
Can you please look into this and let me know if any thing required and we pass the payload by standalonely through EM Console it is working fine.But normal order processing it is showing the below error.
Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'update' failed due to: DBWriteInteractionSpec Execute Failed Exception. update failed. Descriptor name: [insertSiebelOrder.OeSblOrders]. Caused by java.sql.BatchUpdateException: ORA-01013: user requested cancel of current operation . Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered retriable, likely due to a communication failure. Because the global transaction is rolling back the invoke must be retried in a new transaction, restarting from the place of the last transaction commit. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "1013" to your deployment descriptor (i.e. weblogic-ra.xml). ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
Let me know if any thing required.
Regards,
Raj.

Connection Process times out in Conntrans

Hi guys,
On the laptops when conntrans happens, we see an error as follows:
Connection process timed out. Contact system admin to change timeout value and synchronize again.
everything worked out well in Q, but not in Production.
are there any suggestions?
thanks

Hi,
Please update the field STR_VALUE of the table SMO5TSVVAL to FFFF.
This should make sure that it never times out.
Best Regards,
Shourav

BPEL process times out when SOAP-ENV:Fault is received from service.

Hi - I have a BPEL process identical to one in 10.1.2.0.2. If I execute the same test, the BPEL console displays the following on the console for version 10.1.2.0.2.
<Response>Clientwhen invoking endpointAddress 'http://galileo.wlgore.com:5555/soap/default', [ISS.0088.9134] Exception occurred while processing the body of the messageAxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client faultSubcode: faultString: [ISS.0088.9134] Exception occurred while processing the body of the message faultActor: http://galileo.wlgore.com:5555/soap/default faultNode: faultDetail: {http://www.webMethods.com/2001/10/soap/encoding}exception: <className>com.wm.pkg.art.error.DetailedServiceException</className>
 <message lang="">[ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service GORE_DSI_Services.AdaptorService:WorkOrderCompletion. BSFN error code: 2 Number of error: 1 Error item 1 ErrorLevel : 1 ErrorID : 0 DDItem : 0115 lineNumber : 5371 fileName : nd3n1114.c subText : alphaDescription : Error: Work Order Number Invalid glossaryText : CAUSE . . . . The Work Order Number entered does not exist in the Work Order Master file (F4801). RESOLUTION. . Either enter the correct Work Order Number or create a new Work Order for the number on the display. javax.resource.ResourceException: BSFN error code: 2 Number of error: 1 Error item 1 ErrorLevel : 1 ErrorID : 0 DDItem : 0115 lineNumber : 5371 fileName : nd3n1114.c subText : alphaDescription : Error: Work Order Number Invalid glossaryText : CAUSE . . . . The Work Order Number entered does not exist in the Work Order Master file (F4801). RESOLUTION. . Either enter the correct Work Order Number or create a new Work Order for the number on the display. at com.psft.xpi.adapter.erp.service.BSFNExecuteTemplateImpl.execute(BSFNExecuteTemplateImpl.java:306) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.psft.xpi.adapter.erp.service.BSFNExecuteTemplate.execute(BSFNExecuteTemplate.java:134) at com.wm.adk.cci.interaction.WmInteraction.execute(WmInteraction.java:70) at com.wm.pkg.art.ns.AdapterServiceNode.invokeService(AdapterServiceNode.java:596) at com.wm.pkg.art.ns.ARTNSService.baseInvoke(ARTNSService.java:47) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:155) at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:324) at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:580) at com.wm.lang.flow.FlowState.step(FlowState.java:438) at com.wm.lang.flow.FlowState.invoke(FlowState.java:403) at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1749) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:113) at com.wm.app.b2b.server.Service.doInvoke(Service.java:607) at com.wm.app.b2b.server.Service.doInvoke(Service.java:556) at wm.server.soap.envelope(soap.java:98) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:287) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:128) at com.wm.app.b2b.server.HTTPSOAPHandler._process(HTTPSOAPHandler.java:457) at com.wm.app.b2b.server.HTTPSOAPHandler.process(HTTPSOAPHandler.java:111) at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:298) at com.wm.util.pool.PooledThread.run(PooledThread.java:105) at java.lang.Thread.run(Thread.java:534) </message>
</Response>
With this version, however, we either receive "java.lang.IllegalStateException: "Cannot call setRollbackOnly() current thread is NOT associated with a transaction" or a timeout error.
I captured the return message from both servers and it is identical (shown below):
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema">
 <SOAP-ENV:Body>
 <SOAP-ENV:Fault>
 <faultcode>SOAP-ENV:Client</faultcode>
 <faultstring>[ISS.0088.9134] Exception occurred while processing the body of the message</faultstring>
 <faultactor>http://galileo.wlgore.com:5555/soap/default </faultactor>
 <detail xmlns:webM="http://www.webMethods.com/2001/10/soap/encoding">
 <webM:exception>
 <webM:className>com.wm.pkg.art.error.DetailedServiceException</webM:className>
 <webM:message xml:lang="">="">[ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service GORE_DSI_Services.AdaptorService:WorkOrderCompletion. BSFN error code: 2 Number of error: 1 Error item 1 ErrorLevel : 1 ErrorID : 0 DDItem : 0115 lineNumber : 5371 fileName : nd3n1114.c subText : alphaDescription : Error: Work Order Number Invalid glossaryText : CAUSE . . . . The Work Order Number entered does not exist in the Work Order Master file (F4801). RESOLUTION. . Either enter the correct Work Order Number or create a new Work Order for the number on the display. javax.resource.ResourceException: BSFN error code: 2 Number of error: 1 Error item 1 ErrorLevel : 1 ErrorID : 0 DDItem : 0115 lineNumber : 5371 fileName : nd3n1114.c subText : alphaDescription : Error: Work Order Number Invalid glossaryText : CAUSE . . . . The Work Order Number entered does not exist in the Work Order Master file (F4801). RESOLUTION. . Either enter the correct Work Order Number or create a new Work Order for the number on the display. at com.psft.xpi.adapter.erp.service.BSFNExecuteTemplateImpl.execute(BSFNExecuteTemplateImpl.java:306) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.psft.xpi.adapter.erp.service.BSFNExecuteTemplate.execute(BSFNExecuteTemplate.java:134) at com.wm.adk.cci.interaction.WmInteraction.execute(WmInteraction.java:70) at com.wm.pkg.art.ns.AdapterServiceNode.invokeService(AdapterServiceNode.java:596) at com.wm.pkg.art.ns.ARTNSService.baseInvoke(ARTNSService.java:47) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:155) at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:324) at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:580) at com.wm.lang.flow.FlowState.step(FlowState.java:438) at com.wm.lang.flow.FlowState.invoke(FlowState.java:403) at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1749) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:113) at com.wm.app.b2b.server.Service.doInvoke(Service.java:607) at com.wm.app.b2b.server.Service.doInvoke(Service.java:556) at wm.server.soap.envelope(soap.java:98) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:287) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:128) at com.wm.app.b2b.server.HTTPSOAPHandler._process(HTTPSOAPHandler.java:457) at com.wm.app.b2b.server.HTTPSOAPHandler.process(HTTPSOAPHandler.java:111) at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:298) at com.wm.util.pool.PooledThread.run(PooledThread.java:105) at java.lang.Thread.run(Thread.java:534)</webM:message>
 </webM:exception>
 </detail>
 </SOAP-ENV:Fault>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Thanks,
RM

We have tested this same scenario for several services and are experiencing the same result... timing out instead of returning the fault. This is a critical issue for us and would prevent us from implementing this software.

RFC Processing time out

hello everybody,
is there a way to configure the timeout limit for processing RFC's receivers???? cause I'm getting a timeout error for some interfaces where the time processing is really long and is business requirement to do this synchronously, thanks in advance.
Regards,
Julio Cesar

Julio,
I had a similar issue some time back and used the following three parameters
1. Visual Administrator
SAP XI Adapter: RFC parameter syncMessageDeliveryTimeoutMsec
This parameter is explained in SAP Note 730870 Q14 and SAP Note 791379
2. Alert Configuration
SA_COMM parameter CHECK_FOR_ASYNC_RESPONSE_TIMEOUT
This parameter specifies the maximum time in seconds that can pass between the arrival of the synchronous request message on the Integration Server and the asynchronous response message. If this time period is exceeded, a system error is returned to the caller.
3. Integration Process TimeoutControlStep
My design is such that timeout parameter 3 which is set in the Integration Process will be triggered first. This will give me control to handle the timeout via an SMTP email prior to either of the other timeouts taking effect
Regards,
Mike

Broadcaster times-out due to dialog process

Hi !
I'm trying to set up a broadcasting for a report with a large amount of records, and since when I execute it in dialog it times out, broadcasting it in the background seemed a great idea.
The thing is that, despite I schedule it to run in a background process, it still creates a dialog process to fetch data wich times out and therefore the background process (the document creation and email sendig) ends correctly sending a 'No Data Available' report or with an error: com.sap.ip.bi.base.exception.BIBase.RuntimeException.
The parameters for the report are being set in the General Precalculation tab, while there is a Filter Navigation tab which allows you to filer specific characteristics. Which is the difference here ?
Regards,
Santiago

Sonal, thanks for the quick answer.
Let me see if I get this right.
The Precalculation tab allows to filter before precalculation, in order to fetch de query from precalc. cache instead of direct db access. The data excluded from filters in precalc. tab will not be available in the query.
On the other hand, Filter tab sets filter values for characteristics contained in the query. Is this like the right column of the filter tab of Query Designer ?
Let me know if this is right.
Regards,
Santiago

Queue getting time out error

Hello ,
We have a problem with q's getting error time out.
Oue Scenerio is SAP AR - PI--SAP FCSM
The messages are reaching PI. However when PI sends the message back to SAP, the queues were set to run as dialog (D/A) mode, hence the messages were timing out after the dialog process time limit was reached. So we changed the PI queues to run in background. After that the job completes in 0 seconds and nothing gets transferred through PI to FSCM.
Can anyone help me in this problem or provide some pointers how to solve this.
Regards,
Vikrant

are you able to see the successful status in PI (message monitor/CC monitor)...
there must be some exception fired ,you put a break point in the receiver prog. at start and check where is the problem.
give details for further assitance

Accessing Source times out

When I try to access my primary library from the Sources menu, the process times out, and my AppleTV restarts after just hanging for many many minutes. I have a large library of both photos and music, so I'm guessing that this poses a problem. Has anyone else experienced this?
AppleTV Mac OS X (10.4.9)

Gene,
Mine is functioning, or disfunctioning the exact same way. I did a re-install of the Apple TV and let it sync to my library using it's defaults. It copied over about 7,000 songs. But then when I went to stream, I get the exact sme error as you.
If I had enough time I would use a smaller set of my music, say 10,000 songs, and do the same set-up to see if it would then stream properly.
As an aside, It would be nice to save the iTunes library streaming file over to the Apple TV so it would not have to "load" it each time. In our situation, it would be a better use of the drive space.

Process chains time outs and hangs with no error msg - in SP13

Hi all,
We are having all kind of weird problems after we patched our system with SP13. Our process chain time outs and hangs, but surprisingly we never get any error msg. And scarier part is, the problem seems to be intermittent. PC runs fine on some days and hangs on some.
Further analysis into the dump as below
Termination occurred in the ABAP program "SAPLRSSM" -
in "RSSM_SLEEP_DEBUG".
The main program was "SAPMSSY1 ".
In the source code the termination point is in (Include) program "LRSSMU39".
This refers to an issue that appears to have been addressed by OSS Note
934648(meant for SP8). This notes also indicates to populate RSADMIN table to
exclude "RSSM_SLEEP_DEBUG". Not sure if this note is valid for SP13? However we went ahead and populated the RSADMIN table.
So now we have no clue whats going on and where to fix the issue.
As per SAP suggestion we applied the following notes:
0000653996 Analyzing lock situations
0000893563 Correction: Deadlock on completion of a remote chain
0000994007 Corrections: Deadlock with external status query
0001005481 Correction: Process successful, but there is no instance
0001047174 Correction: Incorrect scope when locking in process chains
0001051957 Correction: TIME_OUT during dialog confirmation of processes
0001083660 Report for error stack analysis
Nothing seems to help us. And SAP suggested a few options, which we implemented to no rescue.
Im sure that many of the customers have applied SP13, and want some feedback from them, if this is happening in their systems too?
If so, how did you fix this issue?
Or this situation is unique to us?Please note that no settings were changed as of SP13 to that of what they were in SP12(unless it is a side effect of the patch itself). Everything worked fine with SP12 and is still working on the BIP system. All the problems are in BIQ patched to SP13.
Any pointers or insight would be appreciated. We have a customer msg open with SAP, and going back and forth, but nothing seemed to work as of today.
Thanks,
Voodi

Not sure which OSS helped us get past the issue, as SAP asked us to apply a ton of notes. But along which the notes, SAP has some suggestions for us, which we think did the magic. After the implementation of the suggestin we never faced the same issue again. The suggestion by SAP:
move the process chain callback in a batch job by executing
program RSSM_TRACE_SWITCH and selecting the flag "verifcation
of asynchronous processes - execute in batch".
Lemme know if this doesnt fix the issue, I can give all the notes that SAP asked us to apply.
Message was edited by:
voodi

Parallel processing and time-out

Hi all,
I've got a prob with doing a great number of postings.
While the time elapsed for these postings is too long, I tried to do it with an function module and "IN BACKGROUND TASK". Well, there is also a alternative "STARTING NEW TASK".
But I figured out, that these both variants are starting dialog work processes. I think there is a time out for dialog WP's of 300 seconds in standard.
Will this timeout kill the processes or not??
And witch alternative is the best to do some parallel processing??
thanx in advanced
regards
Olli

Hi Oliver,
Some solutions here:
1. You could increase the value of the dialog time-out (allthough this can only go to a maximum of 600 seconds). This parameter is in the SAP profiles (parameter name = rdisp/max_wprun_time).
2. As suggested by Christian, decrease the amount of work within one LUW. You can do this by inserting (from time to time) a COMMIT WORK. This COMMIT WORK also resets the timeslice counter of the running dialog process (thus giving again an extra timeslice to work). The downside is, that if you have many related objects to modify, your ROLLBACK options become limited.
3. Split the proces in several tasks and put the to work in the background (by scheduling jobs for them).
4. Program your own parallel handler (see sample code). With this you could process document by document (as if each is done separately). The number of dialog processes (minus 2) is the limit you could use.
Sample code:
* Declarations
CONSTANTS:
opcode_arfc_noreq TYPE x VALUE 10.
DATA:
   server       TYPE msname,
   reason       TYPE i,
   trace        TYPE i VALUE 0,
   dia_max      TYPE i,
   dia_free     TYPE i,
   taskid       TYPE i VALUE 0,
   taskname(20) TYPE c,
   servergroup TYPE rzlli_apcl.
* Parallel processes free check
CALL 'ThSysInfo' ID 'OPCODE' FIELD opcode_arfc_noreq
                 ID 'SERVER' FIELD server
                 ID 'NOREQ' FIELD dia_free
                 ID 'MAXREQ' FIELD dia_max
                 ID 'REASON' FIELD reason
                 ID 'TRACE' FIELD trace.
IF dia_free GT 1.
SUBTRACT 2 FROM dia_free.
SUBTRACT 2 FROM dia_max.
ENDIF.
* You must leave some dialogs free (otherwise no one can logon)
IF dia_free LE 1.
MESSAGE e000(38)
     WITH 'Not enough processes free'.
ENDIF.
* Prepare your run
ADD 1 TO taskid.
WRITE taskid DECIMALS 0 TO taskname LEFT-JUSTIFIED.
CONDENSE taskname.
* Run your pay load
CALL FUNCTION 'ZZ_YOUR_FUNCTION'
STARTING NEW TASK taskname
DESTINATION IN GROUP servergroup
EXPORTING
*   Your exporting parameters come here
EXCEPTIONS
    communication_failure = 1
    system_failure         = 2
    RESOURCE_FAILURE       = 3
    OTHERS                 = 4.
Of course you would put this within a loop and let your "payload" function fire off for each document.
You MUST check the number of free processes just before you run the payload.
And as last reminder: Do NOT use the ABAP statement WAIT (this will disrupt the counting of free processes).
Hope this will help you,
Regards,
Rob.

Time Out for a syncronus BPEL process

Hi All,
Need your help with regards to the following:
From a parent BPEL process we need to invoke a synchronous BPEL Process .This(child) could take anything between 20-30 seconds for processing a request.
Now the requirement is to time out the parent BPEL process if the BPEL process it is calling takes more than 25 seconds for processing a request.
If( time taken to get from partner process >25 sec)
time out
Else
Move along with the rest of the process.
Approaches considered:
1) Pick activity :
Fallout: the pick activity would work only when you are calling a asynchronous BPEL process.
2) Having the invoke activity in a scope and adding an on Alarm branch for the scope.
Fallout: The BPEL process manager executes all the other activities even after exceeding the maximum time the process is set for timing out.
That is if we consider the below scenario
If( time taken to get from partner process >25 sec)
time out
Else
move along with the rest of the process.
Instead of executing the if block( onAlarm) it is executing the else block.
Request you to suggests approaches to suffice this requirement.

Hi Sai Madalli,
An approach to it, would be use the syncMaxWaitTime with time that you need, its a configuration per domain.
http://download-west.oracle.com/docs/cd/B31017_01/integrate.1013/b28981/events.htm#BABGGADB
http://download-east.oracle.com/docs/cd/B31017_01/integrate.1013/b28981/app_trblshoot.htm
Regards

Time out error in deploying the process on weblogic server

Hi,
While deploying the BPEL process in Weblogic 10.3.4, following Exception comes on soa server console. I am sure this is not related to my application, but due to this I am not able to deploy the process on server, it lead with connection time out. I increased my connection time out also to 480.
Exception:
<Jun 8, 2011 10:15:37 PM SGT> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '0' for
queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "634" seconds working on the reques
t "weblogic.servlet.internal.ServletRequestImpl@22ea883[
POST /soa-infra/deployer HTTP/1.1
Connection: TE
TE: trailers, deflate, gzip, compress
User-Agent: Oracle HTTPClient Version 10h
Cookie2: $Version="1"
Accept-Encoding: gzip, x-gzip, compress, x-compress
ECID-Context:
Authorization: Basic d2VibG9naWM6d2VibG9naWMx
Cookie: JSESSIONID=JB0KNvdct5X1X5z02FhLDm8jVWjdvXB0chchkQhXpzQFGb9JlF8L!-186412258
Content-type: application/octet-stream
Content-Length: 14824044
]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-16 "[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in
native, suspended, priority=1, DAEMON> {
jrockit.net.SocketNativeIO.readBytesPinned(SocketNativeIO.java:???)
jrockit.net.SocketNativeIO.socketRead(SocketNativeIO.java:24)
java.net.SocketInputStream.socketRead0(SocketInputStream.java:???)
java.net.SocketInputStream.read(SocketInputStream.java:107)
oracle.net.nt.MetricsEnabledInputStream.read(TcpNTAdapter.java:707)
oracle.net.ns.Packet.receive(Packet.java:243)
oracle.net.ns.DataPacket.receive(DataPacket.java:106)
oracle.net.ns.NetInputStream.getNextPacket(NetInputStream.java:309)
oracle.net.ns.NetInputStream.read(NetInputStream.java:254)
oracle.net.ns.NetInputStream.read(NetInputStream.java:187)
oracle.net.ns.NetInputStream.read(NetInputStream.java:92)
oracle.jdbc.driver.T4CSocketInputStreamWrapper.readNextPacket(T4CSocketInputStreamWrapper.java:1
22)
oracle.jdbc.driver.T4CSocketInputStreamWrapper.read(T4CSocketInputStreamWrapper.java:77)
oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1172)
oracle.jdbc.driver.T4CMAREngine.unmarshalSB1(T4CMAREngine.java:1153)
oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:303)
oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:181)
oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:382)
oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:70)
oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1017)
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1330)
oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3722)
oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3869)
^-- Holding lock: oracle.jdbc.driver.T4CConnection@d2596e[thin lock]
oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.j
ava:1508)
weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:160)
oracle.mds.internal.persistence.db.platform.OracleDB.insertStreamedContent(OracleDB.java:890)
oracle.mds.internal.persistence.db.DBStreamedContentHelper.insertContent(DBStreamedContentHelper
.java:73)
oracle.mds.internal.persistence.db.BaseReposAccess.saveStreamedDocument(BaseReposAccess.java:173
0)
oracle.mds.internal.persistence.db.BaseReposAccess.saveStreamedDocument(BaseReposAccess.java:161
5)
oracle.mds.internal.persistence.db.BaseDBMSConnection.saveDocumentWithComment(BaseDBMSConnection
.java:1811)
oracle.mds.internal.persistence.db.BaseDBMSConnection.saveDocument(BaseDBMSConnection.java:1698)
oracle.mds.persistence.DelegatingMetadataStoreConnection.saveDocument(DelegatingMetadataStoreCon
nection.java:501)
oracle.mds.internal.persistence.BufferedMSConnection.saveDocument(BufferedMSConnection.java:545)
oracle.mds.persistence.PTransaction.saveStoreDocument(PTransaction.java:1314)
oracle.mds.persistence.PTransaction.saveDocument(PTransaction.java:824)
oracle.mds.internal.persistence.PersistenceUtils.createOrSaveDocument(PersistenceUtils.java:448)
oracle.mds.internal.transfer.InternalMDSTransfer.transferDocument(InternalMDSTransfer.java:3032)
oracle.mds.internal.transfer.InternalMDSTransfer.transferTransferUnit(InternalMDSTransfer.java:2
897)
oracle.mds.internal.transfer.InternalMDSTransfer.transferTransferUnitList(InternalMDSTransfer.ja
va:2828)
oracle.mds.internal.transfer.InternalMDSTransfer.execute(InternalMDSTransfer.java:1341)
oracle.mds.internal.transfer.InternalMDSTransfer.execute(InternalMDSTransfer.java:1263)
oracle.mds.internal.transfer.InternalMDSTransfer.transfer(InternalMDSTransfer.java:426)
oracle.integration.platform.blocks.deploy.servlet.MDSManager.transferCompositeData(MDSManager.ja
va:401)
oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProce
ssor.java:116)
^-- Holding lock: java.lang.Object@6253346[thin lock]
oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.j
ava:122)
oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.j
ava:107)
oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:
96)
oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:6
8)
oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSe
ssion(CompositeDeployerServlet.java:130)
oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeplo
yerServlet.java:109)
javax.servlet.http.HttpServlet.service(HttpServlet.java:700)
javax.servlet.http.HttpServlet.service(HttpServlet.java:815)
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:22
4)
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:108)
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:206)
weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:55)
oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:299)
oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:405)
oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:98)
oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:55)
oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:299)
oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:405)
oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:98)
oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:55)
oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:86)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:55)
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletCont
ext.java:3687)
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.
java:3681)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:308)
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:116)
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2213)
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2135)
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1420)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
weblogic.work.ExecuteThread.run(ExecuteThread.java:168)
>
<Jun 8, 2011 10:15:37 PM SGT> <Notice> <Diagnostics> <BEA-320068> <Watch 'StuckThread' with severity
'Notice' on server 'soa_server1' has triggered at Jun 8, 2011 10:15:37 PM SGT. Notification details
WatchRuleType: Log
WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'WL-000337') OR (MSGID = 'BEA-000337'))
WatchData: DATE = Jun 8, 2011 10:15:37 PM SGT SERVER = soa_server1 MESSAGE = [STUCK] ExecuteThread:
'0' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "634" seconds working on th
e request "weblogic.servlet.internal.ServletRequestImpl@22ea883[
POST /soa-infra/deployer HTTP/1.1
Connection: TE
TE: trailers, deflate, gzip, compress
User-Agent: Oracle HTTPClient Version 10h
Cookie2: $Version="1"
Accept-Encoding: gzip, x-gzip, compress, x-compress
ECID-Context:
Authorization: Basic d2VibG9naWM6d2VibG9naWMx
Cookie: JSESSIONID=JB0KNvdct5X1X5z02FhLDm8jVWjdvXB0chchkQhXpzQFGb9JlF8L!-186412258
Content-type: application/octet-stream
Content-Length: 14824044
]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-16 "[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in
native, suspended, priority=1, DAEMON> {
jrockit.net.SocketNativeIO.readBytesPinned(SocketNativeIO.java:???)
jrockit.net.SocketNativeIO.socketRead(SocketNativeIO.java:24)
java.net.SocketInputStream.socketRead0(SocketInputStream.java:???)
java.net.SocketInputStream.read(SocketInputStream.java:107)
oracle.net.nt.MetricsEnabledInputStream.read(TcpNTAdapter.java:707)
oracle.net.ns.Packet.receive(Packet.java:243)
oracle.net.ns.DataPacket.receive(DataPacket.java:106)
oracle.net.ns.NetInputStream.getNextPacket(NetInputStream.java:309)
oracle.net.ns.NetInputStream.read(NetInputStream.java:254)
oracle.net.ns.NetInputStream.read(NetInputStream.java:187)
oracle.net.ns.NetInputStream.read(NetInputStream.java:92)
oracle.jdbc.driver.T4CSocketInputStreamWrapper.readNextPacket(T4CSocketInputStreamWrapper.java:1
22)
oracle.jdbc.driver.T4CSocketInputStreamWrapper.read(T4CSocketInputStreamWrapper.java:77)
oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1172)
oracle.jdbc.driver.T4CMAREngine.unmarshalSB1(T4CMAREngine.java:1153)
oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:303)
oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:181)
oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:382)
oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:70)
oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1017)
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1330)
oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3722)
oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3869)
^-- Holding lock: oracle.jdbc.driver.T4CConnection@d2596e[thin lock]
oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.j
ava:1508)
weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:160)
oracle.mds.internal.persistence.db.platform.OracleDB.insertStreamedContent(OracleDB.java:890)
oracle.mds.internal.persistence.db.DBStreamedContentHelper.insertContent(DBStreamedContentHelper
.java:73)
oracle.mds.internal.persistence.db.BaseReposAccess.saveStreamedDocument(BaseReposAccess.java:173
0)
oracle.mds.internal.persistence.db.BaseReposAccess.saveStreamedDocument(BaseReposAccess.java:161
5)
oracle.mds.internal.persistence.db.BaseDBMSConnection.saveDocumentWithComment(BaseDBMSConnection
.java:1811)
oracle.mds.internal.persistence.db.BaseDBMSConnection.saveDocument(BaseDBMSConnection.java:1698)
oracle.mds.persistence.DelegatingMetadataStoreConnection.saveDocument(DelegatingMetadataStoreCon
nection.java:501)
oracle.mds.internal.persistence.BufferedMSConnection.saveDocument(BufferedMSConnection.java:545)
oracle.mds.persistence.PTransaction.saveStoreDocument(PTransaction.java:1314)
oracle.mds.persistence.PTransaction.saveDocument(PTransaction.java:824)
oracle.mds.internal.persistence.PersistenceUtils.createOrSaveDocument(PersistenceUtils.java:448)
oracle.mds.internal.transfer.InternalMDSTransfer.transferDocument(InternalMDSTransfer.java:3032)
oracle.mds.internal.transfer.InternalMDSTransfer.transferTransferUnit(InternalMDSTransfer.java:2
897)
oracle.mds.internal.transfer.InternalMDSTransfer.transferTransferUnitList(InternalMDSTransfer.ja
va:2828)
oracle.mds.internal.transfer.InternalMDSTransfer.execute(InternalMDSTransfer.java:1341)
oracle.mds.internal.transfer.InternalMDSTransfer.execute(InternalMDSTransfer.java:1263)
oracle.mds.internal.transfer.InternalMDSTransfer.transfer(InternalMDSTransfer.java:426)
oracle.integration.platform.blocks.deploy.servlet.MDSManager.transferCompositeData(MDSManager.ja
va:401)
oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProce
ssor.java:116)
^-- Holding lock: java.lang.Object@6253346[thin lock]
oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.j
ava:122)
oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.j
ava:107)
oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:
96)
oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:6
8)
oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSe
ssion(CompositeDeployerServlet.java:130)
oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeplo
yerServlet.java:109)
javax.servlet.http.HttpServlet.service(HttpServlet.java:700)
javax.servlet.http.HttpServlet.service(HttpServlet.java:815)
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:22
4)
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:108)
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:206)
weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:55)
oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:299)
oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:405)
oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:98)
oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:55)
oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:299)
oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:405)
oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:98)
oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:55)
oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:86)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:55)
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletCont
ext.java:3687)
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.
java:3681)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:308)
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:116)
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2213)
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2135)
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1420)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
weblogic.work.ExecuteThread.run(ExecuteThread.java:168)
SUBSYSTEM = WebLogicServer USERID = <WLS Kernel> SEVERITY = Error THREAD = [ACTIVE] ExecuteThread:
'5' for queue: 'weblogic.kernel.Default (self-tuning)' MSGID = BEA-000337 MACHINE = urasvr140 TXID =
CONTEXTID = da07387a98ce3972:315f7e44:1306f8b304d:-8000-0000000000000338 TIMESTAMP = 1307542537412
WatchAlarmType: AutomaticReset
WatchAlarmResetPeriod: 600000
>
<Jun 8, 2011 10:15:39 PM SGT> <Alert> <Diagnostics> <BEA-320016> <Creating diagnostic image in d:\or
acle\middleware\user_projects\domains\test_domain\servers\soa_server1\adr\diag\ofm\test_domain\soa_s
erver1\incident\incdir_54 with a lockout minute period of 1.>
<Jun 8, 2011 10:16:37 PM SGT> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '0' for
queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "694" seconds working on the reques
t "weblogic.servlet.internal.ServletRequestImpl@22ea883[
POST /soa-infra/deployer HTTP/1.1
Connection: TE
TE: trailers, deflate, gzip, compress
User-Agent: Oracle HTTPClient Version 10h
Cookie2: $Version="1"
Accept-Encoding: gzip, x-gzip, compress, x-compress
ECID-Context:
Authorization: Basic d2VibG9naWM6d2VibG9naWMx
Cookie: JSESSIONID=JB0KNvdct5X1X5z02FhLDm8jVWjdvXB0chchkQhXpzQFGb9JlF8L!-186412258
Content-type: application/octet-stream
Content-Length: 14824044
]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-16 "[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in
native, suspended, priority=1, DAEMON> {
jrockit.net.SocketNativeIO.readBytesPinned(SocketNativeIO.java:???)
jrockit.net.SocketNativeIO.socketRead(SocketNativeIO.java:24)
java.net.SocketInputStream.socketRead0(SocketInputStream.java:???)
java.net.SocketInputStream.read(SocketInputStream.java:107)
oracle.net.nt.MetricsEnabledInputStream.read(TcpNTAdapter.java:707)
oracle.net.ns.Packet.receive(Packet.java:243)
oracle.net.ns.DataPacket.receive(DataPacket.java:106)
oracle.net.ns.NetInputStream.getNextPacket(NetInputStream.java:309)
oracle.net.ns.NetInputStream.read(NetInputStream.java:254)
oracle.net.ns.NetInputStream.read(NetInputStream.java:187)
oracle.net.ns.NetInputStream.read(NetInputStream.java:92)
oracle.jdbc.driver.T4CSocketInputStreamWrapper.readNextPacket(T4CSocketInputStreamWrapper.java:1
22)
oracle.jdbc.driver.T4CSocketInputStreamWrapper.read(T4CSocketInputStreamWrapper.java:77)
oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1172)
oracle.jdbc.driver.T4CMAREngine.unmarshalSB1(T4CMAREngine.java:1153)
oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:303)
oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:181)
oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:382)
oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:70)
oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1017)
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1330)
oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3722)
oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3869)
^-- Holding lock: oracle.jdbc.driver.T4CConnection@d2596e[thin lock]
oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.j
ava:1508)
weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:160)
oracle.mds.internal.persistence.db.platform.OracleDB.insertStreamedContent(OracleDB.java:890)
oracle.mds.internal.persistence.db.DBStreamedContentHelper.insertContent(DBStreamedContentHelper
.java:73)
oracle.mds.internal.persistence.db.BaseReposAccess.saveStreamedDocument(BaseReposAccess.java:173
0)
oracle.mds.internal.persistence.db.BaseReposAccess.saveStreamedDocument(BaseReposAccess.java:161
5)
oracle.mds.internal.persistence.db.BaseDBMSConnection.saveDocumentWithComment(BaseDBMSConnection
.java:1811)
oracle.mds.internal.persistence.db.BaseDBMSConnection.saveDocument(BaseDBMSConnection.java:1698)
oracle.mds.persistence.DelegatingMetadataStoreConnection.saveDocument(DelegatingMetadataStoreCon
nection.java:501)
oracle.mds.internal.persistence.BufferedMSConnection.saveDocument(BufferedMSConnection.java:545)
oracle.mds.persistence.PTransaction.saveStoreDocument(PTransaction.java:1314)
oracle.mds.persistence.PTransaction.saveDocument(PTransaction.java:824)
oracle.mds.internal.persistence.PersistenceUtils.createOrSaveDocument(PersistenceUtils.java:448)
oracle.mds.internal.transfer.InternalMDSTransfer.transferDocument(InternalMDSTransfer.java:3032)
oracle.mds.internal.transfer.InternalMDSTransfer.transferTransferUnit(InternalMDSTransfer.java:2
897)
oracle.mds.internal.transfer.InternalMDSTransfer.transferTransferUnitList(InternalMDSTransfer.ja
va:2828)
oracle.mds.internal.transfer.InternalMDSTransfer.execute(InternalMDSTransfer.java:1341)
oracle.mds.internal.transfer.InternalMDSTransfer.execute(InternalMDSTransfer.java:1263)
oracle.mds.internal.transfer.InternalMDSTransfer.transfer(InternalMDSTransfer.java:426)
oracle.integration.platform.blocks.deploy.servlet.MDSManager.transferCompositeData(MDSManager.ja
va:401)
oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProce
ssor.java:116)
^-- Holding lock: java.lang.Object@6253346[thin lock]
oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.j
ava:122)
oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.j
ava:107)
oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:
96)
oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:6
8)
oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSe
ssion(CompositeDeployerServlet.java:130)
oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeplo
yerServlet.java:109)
javax.servlet.http.HttpServlet.service(HttpServlet.java:700)
javax.servlet.http.HttpServlet.service(HttpServlet.java:815)
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:22
4)
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:108)
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:206)
weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:55)
oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:299)
oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:405)
oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:98)
oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:55)
oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:299)
oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:405)
oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:98)
oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:55)
oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:86)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:55)
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletCont
ext.java:3687)
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.
java:3681)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:308)
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:116)
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2213)
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2135)
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1420)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
weblogic.work.ExecuteThread.run(ExecuteThread.java:168)
>
Please tell me what this is related to and how can I overcome this problem.
Thanks..

Have u tried by increasing the SyncMaxWaitTime property?
-chitrita

Report Times Out only on Dialog Application Server

Hi -
We are on ECC 6. We have a Central Instance and a Dialog Instance (both on AIX 5.3). When the endusers run S_ALR_87009788 (program RFRRBIL1), which can not be run as a background job, on the Central Instance it runs to completion in about 10 minutes. When they run the same report, with the same variant, on the Dialog Instance it times out in the SAPLGSAC program within the Include program LGSACF01.
I've checked and rechecked parameters on both servers and they match. CPU, memory and swap match as well.
To add to this, the report runs in 2 minutes on our ECQ system.
What else should I look at?
Thanks!
Margaret

> No, we do not have dedicated high-speed network connections between the application servers and the database server.
This explains why you can execute the program on the database server directly but not on the application server.
Most likely you have a 100 MBit connection, all other traffic is also going through that interface. So the application server must read all data from the database server, transfer it over the network to the application server and from there it has to be transmitted again to the client.
It's highly advised to not use the normal network interface for communication between app server and database but a dedicated network infrastructure to keep latencies low and to allow almost the same speed.
Markus

While Starting oacleAS time out while waiting for a managed process start

Hello Friends,
While starting the Oracle Application server, through OPMN command as well as from the services I am getting following error.
opmnctl: starting opmn and all managed processes...
================================================================================
opmn id=hydcgwsgess02:6200
0 of 1 processes started.
ias-instance id=GenPro.hydcgwsgess02.ind.ge.ad
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ias-component/process-type/process-set:
OC4J/home/default_group/
Error
--> Process (index=1,uid=461249245,pid=12988)
time out while waiting for a managed process to start
Log:
D:\product\10.1.3\OracleAS_1\opmn\logs\OC4J~home~default_group~1
========================================================
couldn't figure out what is the basic problem...
Normally when ever I make any changes in Oracle Sensor Edge Server, I used to get this error..
I have installed the Oracle Apps Server in Windows enviroment...
I will be very happy if some body can help me resolve the issue...
Regards
Nasim

i got the same error but in my case, I used HTTPDispatcher and found that the URL parameter was invalid, so I changed it in the edgeserver.xml and restart, it's ok for me.
Edited by: blackwaterpark on Oct 29, 2008 2:21 PM

Dialog process time out !!!

Similar Messages

Maybe you are looking for