OSB File Proxy Error Handling

Hi,
I've encountered a strange behaviour in my proxy service.
Legend:
FPS -> File-based Proxy Service, reads files from a local directory
EH -> ErrorHandler of the FPS
JBS -> JMS-based Business Service, writes to a JMS Queue
Scenario: FPS reads files and calls JBS to put messages in a queue
Problem:
When testing my FPS, when there is an error (for example in the Service Callout to the JBS) I noticed that the system instanciates a new Proxy Service to "retry" the same file. I also noticed that if I place a Reply Action in the of my EH, this retry mechanism doesn't happen.
What I gather from this is that the file adaptor is somehow transactional, retrying the process (only once) in the event of an error.
Question:
Is this the normal behaviour for a file adaptor? If so, how can I configure the number of retries?
Thanks,
Adel

As mentioned before, in the tests I executed I noticed that when there's an error, the system automatically retries the file by creating a new instance of the same Proxy Service.I'm little confused what type of errors you are talking. Under the hood MDB is used (that is the reason you see JMS queues wlsb.internal.transport.task.queue.ftp,wlsb.internal.transport.task.queue.file). Based on you error you can easily figure out what might be the cause. I suspect that to be effect of redelivery-limit=1.
eg in xbusResources-jms.xml in your domain config
<queue name="wlsb.internal.transport.task.queue.file">
<sub-deployment-name>wlsbJMSServer</sub-deployment-name>
<delivery-failure-params>
<redelivery-limit>1</redelivery-limit>
</delivery-failure-params>
<jndi-name>wlsb.internal.transport.task.queue.file</jndi-name>
</queue>
So, what's I'm trying to figure out is if this behaviour is normal? Is this the way OSB implements retry at the Proxy Service level when it's configured with a file-adaptor?Same behavior will also be in FTP/SFTP as with File
Thanks
Manoj

Similar Messages

Client ABAP proxy error handling. Please help!

Hi Experts,
   I have following scenario:
   SAP ECC (ABAP Client Proxy) -> PI(XI)-->(SOAP) Third party web service System
   This is Asynchronous.
   What will happen when ABAP client Proxy in ECC sends data to PI but PI is down?
   Will the message be queued in ECC? Can the queued message be processed automatically when PI is UP later?
   Please help.
Thanks & Regards
Gopal

Hello Gopal,
Correct, it should be an automatic entry into the queue!
refer below for a detailed understanding!
/people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies     XI: Reliable Messaging u2013 EOIO in ABAP Proxies
/people/krishna.moorthyp/blog/2005/12/23/monitoring-for-processed-xml-messages-in-abap-proxy     Monitoring for Processed XML messages in ABAP Proxy
Weblog to send Response from RFC to File in Asyn Mode Using Proxy [original link is broken]     Weblog to send Response from RFC to File in Asyn Mode Using Proxy
/people/michal.krawczyk2/blog/2009/06/20/pixi-abap-proxies-say-goodbye-to-executeasynchronous-method     PI/XI: ABAP Proxies say goodbye to Execute_Asynchronous method
/people/krishnakumar.ramamoorthy3/blog/2008/11/02/error-handling-framework-for-abap-proxies--part-1     Error handling framework for ABAP proxies - Part 1
/people/krishnakumar.ramamoorthy3/blog/2008/12/19/error-handling-framework-for-abap-proxies--part-2     Error handling framework for ABAP proxies - Part 2
Regards,
Jilan

File Adapter Error Handling from Batch job

Dear all,
I'd like to handle error information by batch job process.
However I can't find out the error flag from the file adapter.
My XI setting is below.
1.FIle to File conversinn by using File adapter
2.Async setting
3.Not use BPM
Anyway,we only want to judge the status for XI process from Batch process like MS-DOS batch.
Kindly please tell me the detail explanation.
Regards,
Masayuki.

Hi Masayuki,
Please take a look at these..
http://help.sap.com/saphelp_nw2004s/helpdata/en/fa/09714d543b11d1898e0000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/fa/0971c2543b11d1898e0000e8322d00/frameset.htm
cheers,
Prashanth

File Adapter Error Handling

Hi All,
I am using File adapter to read the xml file and FTP it to another directory ( BPEL 10.1.3)
If i put any xml file in the input directory , it picks up the file and FTP it , but the as the xml file will not match the xsd, it out put some xml file which doesnt have any data. I
if the xml file not as per XSD then it should throw error or ?
If i put the correct xml file it FTP it to output directory with correct xml file.
My question is how do i handle the situation/error where xml file is not well formed or xml is not as per the xsd, so that it should stop the process and will log the error and put the file in some other directory.
Please help.
Thanks and Regards,
Vikram Singh

Hi,
Yes, i did checked in the folder.
Also did the following changes as per the Adapter dev guide, Now i am able to validate the file but its not writing the rejected file messgae to the specified director.
bpel.xml details -----
<BPELSuitcase>
<BPELProcess id="Airtricity_Credit" src="Airtricity_Credit.bpel">
<partnerLinkBindings>
<partnerLinkBinding name="Read_Credit_File">
<property name="wsdlLocation">Read_Credit_File.wsdl</property>
<property name="validateXML">true</property>
</partnerLinkBinding>
</partnerLinkBindings>
<activationAgents>
<activationAgent className="oracle.tip.adapter.fw.agent.jca.JCAActivationAgent" partnerLink="Read_Credit_File">
<property name="portType">Read_ptt</property>
<property name="rejectedMessageHandlers">
file://C:\product\10.1.3.1\OracleAS_1\bpel/samples/tutorials/124.AQAdapter/AQMessageRejectionHandler/rejected
</property>
</activationAgent>
</activationAgents>
</BPELProcess>
</BPELSuitcase>
++++++++++++++++++++++++++++++
Please help.
Thanks ,
vikram Singh

File-Proxy (Error while receiving by HTTP )

Hi All,
I have a problem in the scenario file to Proxy....which is that after placing a source file successfuly in the source directory.... it is showing an information message in the XML message monitoring(sxmb_moni) like below
Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)
Could anybody explain the problem please????where i need to configure to reslove this.
Thanks.
Respond me Imme pls.

First thing to check is that the adapter_plain service is activated in the transaction SICF. (path: default_host-> sap -> xi -> adapter_plain
Then check that the http service is running properly (transaction SMICM).
Also, unless you are connecting to an SAP webAS, you should give a username and password, rather than "Use Logon data fotr SAP System". You could also maintain the URL and authentication data as an sm59 destination and use that in the adapter.
Please look at these...
INTEGRATION_DIRECTORY_HMI: Connection fails
ICM_HTTP_CONNECTION_FAILED
SAF - ICM_HTTP_CONNECTION_FAILED
HTTP adapter setup
Check out this SAP Note- 824554
Also this links
ICM_HTTP_CONNECTION_FAILED
Cache Refresh~
https://websmp201.sap-ag.de/~sapdownload/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf
ICM_HTTP_CONNECTION_FAILED ERROR
error code: 400, error text: ICM_HTTP_CONNECTION_FAILED
Error With ABAP Client proxy
Message not reaching Integration server
HTTP content sever - error?
Error in content server configuration
HTTP Client : Code 110 reason
RFC: INTEGRATION_DIRECTORY_HMI
Content server config - error?
Thanks
Swarup

File Polling Error Handling

Hello,
I want to know how I can capture the error message in my BPEL process when I submit a wrong xml file to file adapter. I can process an xml file because the xsd is validated, but I want to know how to capture the error message (Error while translating) when a wrong xml is submitted. I see error message in Enterprise Manager (11G), but I want to capture this error message in my BPEL process and send out an email notification with the file name and error message.
Please advise.
Thanks

I tried this, but no luck.
When I submit a wrong xml, then it wont even create an instance ID. Below is the error I see in EM.
Non Recoverable System Fault :
Error while translating. Error while translating. Error occured while translating content from file /LAX_Dock/nipun/BurnNotice.xml Please make sure that the file content conforms to the schema. Make necessary changes to the file content or the schema.
Thanks for your help.

Osb - bind error handler to proxy service

Hi!
I have got a proxy service which polls a POP3 server to download emails and process them.
My question: How could I bind an error handler to proxy service for noticing when the POP3 server is not available?
So I would like to put an alert when the OSB looses the connection to email server. I tried to put an error handler to top component on message flow but it doesn't work...
Could anyone help me?
Thanks!
Viktor

For poller transports (email/File/FTP etc) it is not possible to catch errors of transport layer, in your service error handler. Re: OSB - Error Handler in FTP Transport for TransportException
Thanks
Manoj
Edited by: Manoj Neelapu on Jun 28, 2010 3:51 PM

Error Handling in OSB

Hi,
In OSB how to catch all different errors and send them to specific
For ex:
1.if i get a "file not found" error, i need to send an email notification
2.if i get an arithmetic error , i need to send it to database
like any other errors...
Can we handle all those errors in a single error handler and send them to specific targets
let me know any questions

basically what is did is create a generic proxy service which will contain all the logic to handle your faults.
so in your case you could create a soap or xml proxy service (let's name it ErrorHospital).
the input of this proxy service needs to contain all the data you need to decide what to do with a certain error.
for now let's make the interface something like
<errorMetadata>
<error>{$fault}</error>
<payload>{$body}</payload>
</errorMetadata>you could just add me metadata from the proces which is failing ofcourse, it's up to you to decide what data you need.
now in for example the EmployeeService something fails.
In the EmployeeService you add a service error handler, and for the start in this service error handler we will only do a publish to our new 'ErrorHospital'.
Create the <errorMetadata> element in here and do the publish.
At this stage we have all the metadata available in our ErrorHospital proxy service, so we can execute all the logic needed for any specifica error.
In the ErrorHospital proxyservice you could add something like
if $body/errorMetadata/error/faultCode = 'MAIL-001' then send mail (by use of a mail transport business service (this expression won't work, but just to show what's possible)
in my blog i used a ErrorRepository in which i configure what actions to execute based on the errorCode
so you could add MAIL-001 in this repository and define something like
log_YN = Y
mail_YN = Y
report_YN =N
the generic logic in your errorHospital proxy service will contain a list of
if - then - else combinations to decide if it should mail, or if it should log or if it should report
and this will work on every errorCode you define in the ErrorRepository.
It's a solution we use at my current customer too and works pretty nice, and the administrators can update the ErrorRepository file from the console on production if they decide on a certain moment that they need logging on some errorCode for example
hope it's a bit clear like this

Report and Alert don't executed in the error handler with a JMS proxy service

Hi,
I'm working with OSB 11.1.1.4.0 and I'm facing a problem with the error handler of my JMS proxy service.
My error handler contains two main elements :
- a Report action
- an Alert with a JMS destination defined
When the business service failed the message remain in the queue. It's the expected behavior.
The problem is :
- the report is missing
- the alert is raised but missing in the JMS destination defined in the Alert setting.
I've noticed if I add a Reply with Failure or Success, Report and Alert are successfully executed.
Unfortunately the message don't remain in the JMS queue.
What can I do in order to have my report/alert done and the JMS transaction rollback in order to keep the message in the queue ?
I've already met this problem in the past with alsb v3 and my solution was to add Service Callout in the error handler in order to externalize these actions.
This solution is not convenient and I hope another solution is possible.

Inventorying workgroups can be difficult, especially when it comes to remote access and network security. Because workgroups are not centrally managed, some of the items discussed in this
wiki article on preparing your workgroup environment may require you to visit each machine individually.
For non-domain credentials, you do not use the <systemname>\<user> format, you simply enter the user name. Regarding how to enter the credentials, if you have an account that uses the same username and password on all machines and is an administrator
on all of those machines, then you can enter that in the All computers credentials page of the wizard. You can also do this if they are different user names. However, if some machines have an account with the same user name, such as Administrator,
but different passwords on each machine, you will need to use the Manually enter computer names discovery method, and then enter the information for each group or each machine.
As you can tell, workgroup environments can quickly negate any benefit that the agentless inventory nature of MAP provides.
Please remember to click "Mark as Answer" on the post that helps you, and to click
"Unmark as Answer" if a marked post does not actually answer your question. Please
VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.

How to create a generic error handling proxy?

Hello,
i have few services proxies.
I want to create a generic error handling osb proxy which does only errorhandling.
This proxy would be called by all my services.Now suppose my services proxies would throw any error,the control will pass to error handling block of proxy..from there i will call this generic errorhandling proxyusing a service callout or publish action.In this proxy i want to do all my error handling based on 'n' conditions.and i want to pass the message to the fault variable of services proxy..kindly suggest ways..*main challenge is passing the message to the fault variable of services proxy*

Hi,
For generic error handling framework or common error handling framework...create a bpel process which takes the error details payload and sends the inf/data as email to the particular receipients.
create business process with bpel process and proxy using business service.so wen ever error occurs at stage or route or proxy level ..call error handler action in OSB.Assign error handler details to the bpel input payload.
FOR EX:
<soap-env:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<com:test>
<com:ProcessInfo>testDetails</com:ProcessInfo>
<com:BusinessProcessName>testprocess</com:BusinessProcessName>
<com:BusinessProcessInstanceId>{fn-bea:uuid()}</com:BusinessProcessInstanceId>
<com:BusinessProcessStep>ReqLayer</com:BusinessProcessStep>
<com:ErrorCode>{string($fault/ctx:errorCode)}</com:ErrorCode>
<com:ErrorType>Technical</com:ErrorType>
<com:StatusCode>Error</com:StatusCode>
<com:ImplementationCode>OSB</com:ImplementationCode>
<com:ErrorDescription>{string($fault/ctx:reason)}</com:ErrorDescription>
<com:ErrorDateTime>{fn:current-dateTime()}</com:ErrorDateTime>
<com:Node>{string($fault/ctx:location/ctx:node)}</com:Node>
<com:Path>{string($fault/ctx:location/ctx:path)}</com:Path>
</com:test>
</soap-env:Body>
this assign the error details values to the bpel process.

Error Handling in Inbound ABAP Proxy with EOIO

Hi,
The scenario
I have a File to ABAP Proxy scenario and since the requirement is that the messages have to be processed in a single queue in the SAP system (i.e. EOIO), the sender file channel was configured to be EOIO. This ensures that all messages that enters the SAP system are put in a single queue and then processed one after the other.
The Issue
Now if one of the messages that enter SAP system fails during the processing in the ABAP program, the queue gets stuck and all messages after that go into a scheduled state. And one has to manually clear the errored message in order to continue processing the other waiting messages.
The Question
I know this is a default behavior in an EOIO scenario, however is there any way in which if a message fails in the ABAP program then one can automatically push it out of the queue and keep processing the other messages after it ?
Thanks
Bharath

As a general rule I only use EOIO when there is a possibility of dependancy between messages (message 1 must be first and finsihed before message 2 starts). Assuming your just moving the errored message asside, I would assume that EOIO should be just EO.
Alternatively, change the ABAP proxy to handle the error and return a clean status. Exception handling (try/catch) should be used were ever dangerous code is being used.
If alerting in the proxy end point is to much trouble - change your proxy to a sync scenario return the error to PI and fire alerts from there <- I think this should be avoided but it will work.
The main point is the exception handling so that the proxy fails "gracefully".

File Proxy Service Problem on errors

In continuation of this thread...
File Proxy Service Problem on errors
We are now facing two problems.
1.The proxy service is executed twice
2.File is getting moved to error directory with prefixed file names which we are not able to retrieve and use in the notification email.
Not sure how to fix :(

1.The proxy service is executed twice Check if this is due to transaction timeout issue as discussed here. Re: OSB File polling working twice with the same file
2.File is getting moved to error directory with prefixed file names which we are not able to retrieve and use in the notification email.I am not sure wehther you have any option here. You can check with support. Alternatively can raise notification mail with the timestamp and some file/business identifier from the file. The support person can then open the file from error directory to verify the file/business id in the file or educate the support user that the files will have a prefix

OSB 10gR3 Error handling and reporting action approach

My use case:
Simple Proxy service routes to an external web service created as Business service in OSB
Whenever there is transport error/soap fault from the external web service, that error needs to be reported along with the original request received by the proxy service.
What I have tried so far?
Created a error handler/stage in the route node of my proxy service. Within that stage, added a report action to report $body which contains the error received from the external service. I created a report index key/value to report for this request, I used a specific element in the body of the original request sent to the proxy service.
Within the route error handling stage, I realized that $body which had my original request to the proxy service lost its content and replaced by the fault from external WS. So I made a copy of $body in my request pipeline and tried to use an element from that copy to index my failed request. But the copied variable always seem to be empty within the error handling stage.
So, my questions to the experts,
1)What variables are visible within the error handling stage/scope?
2)What is the best way(less overhead) to preserve my original request as $body context variable is already changed with fault by the time error handler is invoked? Remember I wanted to report the original request only incase of error, for success cases I don't care/I don't want to un-necessarily add an overhead of copying to a vairbale.
3)Is there another proper way to simply report the original request received by proxy and fault received from external service for a given key in the request, say orderId
Sample proxy request:
<MyData>
<OrderId>123</OrderId>
</MyData>

1)What variables are visible within the error handling stage/scope? $fault - http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/context.html#wp1051816
$body - http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/context.html#wp1103311
2)What is the best way(less overhead) to preserve my original request as $body context variable is already changed with fault by the time error handler is invoked? Remember I wanted to report the original request only incase of error, for success cases I don't care/I don't want to un-necessarily add an overhead of copying to a variable.Can you print $body and $fault variables in your error handler?. Are they different ? What I'm suspecting is the back-end webservice is faulting (returning soap-fault and http response =5xx). There is no other way I can think of than copying the contents of $body to a separate variable.
Thanks
Manoj

How to use Request header in the OSB error handler

Hi
I have a scenario where OSB proxy service accptes the payload and routes to the target service
and before routing, I'm generating UUId and inserting in to the request header and publishing the request payload along with UUID to another service.
when the target service is thrown some business fault,i need to publish the fault along with the header(which has UUID).since my target service sends only fault body,header is getting emptied in the error hanlder section.
How can I use the requestheader in the error handler section. Any help is highly appreciated.
Thanks,
N
Edited by: user13154768 on Sep 23, 2010 3:25 AM
Edited by: user13154768 on Sep 23, 2010 3:26 AM

Just assign your request header ($header) to your variable (e.g. $myRequestHeader) and than use this variable in your error handler. Fault response will override your $header but can't override $myRequestHeader.

OSB 10.3g file proxy and how to process files sequentially

Hi all,
I've a folder that contains some files that I need to process sequentially by a file proxy:
/tmp/osb/msg > ls -l
-rw-r--r-- 1 weblogic weblogic 904 Jul 22 12:02 yyy_C0001279792949924_20100722_120229_BU.yyy.CH_ASS_xxx.xml
-rw-r--r-- 1 weblogic weblogic 917 Jul 22 12:02 yyy_C0001279792949955_20100722_120229_BU.yyy.CH_ASS_xxx.xml
-rw-r--r-- 1 weblogic weblogic 932 Jul 22 12:02 yyy_C0001279792949986_20100722_120229_BU.yyy.CH_ASS_xxx.xml
-rw-r--r-- 1 weblogic weblogic 858 Jul 22 12:02 yyy_C0001279792950017_20100722_120230_BU.yyy.CH_ASS_xxx.xml
-rw-r--r-- 1 weblogic weblogic 890 Jul 22 12:02 yyy_C0001279792950033_20100722_120230_BU.yyy.CH_ASS_xxx.xml
-rw-r--r-- 1 weblogic weblogic 790 Jul 22 12:02 yyy_C0001279792950064_20100722_120230_BU.yyy.CH_ASS_xxx.xml
-rw-r--r-- 1 weblogic weblogic 844 Jul 22 12:02 yyy_C0001279792950096_20100722_120230_BU.yyy.CH_ASS_xxx.xml
-rw-r--r-- 1 weblogic weblogic 937 Jul 22 12:02 yyy_C0001279792950111_20100722_120230_BU.yyy.CH_ASS_xxx.xml
-rw-r--r-- 1 weblogic weblogic 813 Jul 22 12:02 yyy_C0001279792950142_20100722_120230_BU.yyy.CH_ASS_xxx.xml
-rw-r--r-- 1 weblogic weblogic 963 Jul 22 12:02 yyy_C0001279792950158_20100722_120230_BU.yyy.CH_ASS_xxx.xml
this is the list of the files sorted alphabetically but also is the list sorted by creation time (each filename (after yyy_C) contains a timestamp and also a date).
The file proxy is configured as belows:
Service Type : Any XML Service
Protocol : file
Endpoint URI : file:///tmp/osb/msg
Get All Headers : No
File Mask : yyy*.xml
Polling Interval: 30
Read Limit : 0
Sort By Arrival : true
Scan SubDirectories: false
Pass By Reference : false
Post Read Action : archive
Stage Directory : /tmp/osb/stage
Archive Directory : /tmp/osb/archive
Error Directory : /tmp/osb/error
Request encoding : utf-8
Content Streaming : Disabled
I used "Sort By Arrival : true" because from doc (http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/httppollertransport/index.html) I read:
"This parameter indicates the sequence of events raised in the order of the arrival of files. The default value for this parameter is False"
It is not clear if 'order of the arrival' means by time of the arrival or by 'alphabetical order'.
I did a test using the above settings but I see from OSB log file that the files are processed neither by time order nor by alphabetical order:
####<Jul 22, 2010 12:33:24 PM CEST> <... ExecuteThread: '4' ... <BEA1-07857BB52A53B9043886> <> <1279794804450> ...########## ready to process filename: .../tmp/osb/msg/yyy_C0001279792949955_20100722_120229_BU.yyy.CH_ASS_xxx.xml
####<Jul 22, 2010 12:33:24 PM CEST> <... ExecuteThread: '0' ... <BEA1-078F7BB52A53B9043886> <> <1279794804454> ...########## ready to process filename: .../tmp/osb/msg/yyy_C0001279792949924_20100722_120229_BU.yyy.CH_ASS_xxx.xml
####<Jul 22, 2010 12:33:24 PM CEST> <... ExecuteThread: '1' ... <BEA1-07907BB52A53B9043886> <> <1279794804457> ...########## ready to process filename: .../tmp/osb/msg/yyy_C0001279792949986_20100722_120229_BU.yyy.CH_ASS_xxx.xml
####<Jul 22, 2010 12:33:24 PM CEST> <... ExecuteThread: '0' ... <BEA1-07917BB52A53B9043886> <> <1279794804462> ...########## ready to process filename: .../tmp/osb/msg/yyy_C0001279792950064_20100722_120230_BU.yyy.CH_ASS_xxx.xml
####<Jul 22, 2010 12:33:24 PM CEST> <... ExecuteThread: '1' ... <BEA1-07927BB52A53B9043886> <> <1279794804467> ...########## ready to process filename: .../tmp/osb/msg/yyy_C0001279792950017_20100722_120230_BU.yyy.CH_ASS_xxx.xml
####<Jul 22, 2010 12:33:24 PM CEST> <... ExecuteThread: '0' ... <BEA1-07937BB52A53B9043886> <> <1279794804607> ...########## ready to process filename: .../tmp/osb/msg/yyy_C0001279792950142_20100722_120230_BU.yyy.CH_ASS_xxx.xml
####<Jul 22, 2010 12:33:24 PM CEST> <... ExecuteThread: '4' ... <BEA1-07947BB52A53B9043886> <> <1279794804611> ...########## ready to process filename: .../tmp/osb/msg/yyy_C0001279792950111_20100722_120230_BU.yyy.CH_ASS_xxx.xml
####<Jul 22, 2010 12:33:24 PM CEST> <... ExecuteThread: '4' ... <BEA1-07957BB52A53B9043886> <> <1279794804615> ...########## ready to process filename: .../tmp/osb/msg/yyy_C0001279792950096_20100722_120230_BU.yyy.CH_ASS_xxx.xml
####<Jul 22, 2010 12:33:24 PM CEST> <... ExecuteThread: '4' ... <BEA1-07967BB52A53B9043886> <> <1279794804618> ...########## ready to process filename: .../tmp/osb/msg/yyy_C0001279792950033_20100722_120230_BU.yyy.CH_ASS_xxx.xml
####<Jul 22, 2010 12:33:24 PM CEST> <... ExecuteThread: '1' ... <BEA1-07977BB52A53B9043886> <> <1279794804630> ...########## ready to process filename: .../tmp/osb/msg/yyy_C0001279792950158_20100722_120230_BU.yyy.CH_ASS_xxx.xml
How could I process files sequentially ?
I think using also Read Limit = 1 and Polling Interval = 1 sec doesn't work, because
- if the proxy instance P1 reading file A takes more than 1 sec
- after 1 sec a second proxy instance P2 starts to process file B
- but P2 can completes its processing before P1 ...
What do you suggest to do ?
Thanks in advance
ferp

Hi Anuj,
even trying with
- Read Limit 1
- Polling Interval 1
- Sort By Arrival true
I see from OSB log file that the files are processed neither by time order nor by alphabetical order:
####<Jul 22, 2010 2:35:56 PM CEST> ... ExecuteThread: '0' ...<BEA1-07F27BB52A53B9043886> <> <1279802156519> .../tmp/osb/msg/yyy_C0001279792949955_20100722_120229_BU.yyy.CH_ASS_xxx.xml
####<Jul 22, 2010 2:35:58 PM CEST> ... ExecuteThread: '0' ...<BEA1-07F47BB52A53B9043886> <> <1279802158508> .../tmp/osb/msg/yyy_C0001279792949924_20100722_120229_BU.yyy.CH_ASS_xxx.xml
####<Jul 22, 2010 2:36:00 PM CEST> ... ExecuteThread: '1' ...<BEA1-07F67BB52A53B9043886> <> <1279802160525> .../tmp/osb/msg/yyy_C0001279792949986_20100722_120229_BU.yyy.CH_ASS_xxx.xml
####<Jul 22, 2010 2:36:02 PM CEST> ... ExecuteThread: '4' ...<BEA1-07F87BB52A53B9043886> <> <1279802162544> .../tmp/osb/msg/yyy_C0001279792950064_20100722_120230_BU.yyy.CH_ASS_xxx.xml
####<Jul 22, 2010 2:36:04 PM CEST> ... ExecuteThread: '0' ...<BEA1-07FA7BB52A53B9043886> <> <1279802164564> .../tmp/osb/msg/yyy_C0001279792950017_20100722_120230_BU.yyy.CH_ASS_xxx.xml
####<Jul 22, 2010 2:36:06 PM CEST> ... ExecuteThread: '1' ...<BEA1-07FC7BB52A53B9043886> <> <1279802166584> .../tmp/osb/msg/yyy_C0001279792950142_20100722_120230_BU.yyy.CH_ASS_xxx.xml
####<Jul 22, 2010 2:36:08 PM CEST> ... ExecuteThread: '0' ...<BEA1-07FE7BB52A53B9043886> <> <1279802168606> .../tmp/osb/msg/yyy_C0001279792950111_20100722_120230_BU.yyy.CH_ASS_xxx.xml
####<Jul 22, 2010 2:36:10 PM CEST> ... ExecuteThread: '4' ...<BEA1-08007BB52A53B9043886> <> <1279802170624> .../tmp/osb/msg/yyy_C0001279792950096_20100722_120230_BU.yyy.CH_ASS_xxx.xml
####<Jul 22, 2010 2:36:12 PM CEST> ... ExecuteThread: '0' ...<BEA1-08027BB52A53B9043886> <> <1279802172644> .../tmp/osb/msg/yyy_C0001279792950033_20100722_120230_BU.yyy.CH_ASS_xxx.xml
####<Jul 22, 2010 2:36:14 PM CEST> ... ExecuteThread: '4' ...<BEA1-08047BB52A53B9043886> <> <1279802174664> .../tmp/osb/msg/yyy_C0001279792950158_20100722_120230_BU.yyy.CH_ASS_xxx.xml
As said I think that using Read Limit = 1 and Polling Interval = 1 sec doesn't work, because
- if the proxy instance P1 reading file A takes more than 1 sec for processing the file
- after 1 sec a second proxy instance P2 starts to process file B
- but P2 can completes its processing before P1 ...
Do you know if OSB when polling a file, takes it only when OSB recognizes the file has been written completely ?
I mean what happens if OSB wakes up while the file producer is still writing the file ?
Regards
ferp

OSB File Proxy Error Handling

Similar Messages

Maybe you are looking for