cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with Adapter ..

Former Member
0 Kudos

Hi,

In our scenario, we are using sender file adapter for handling multiple messages for an interface. The processing mode is Exactly Once. Actually we are doing load testing.. If we have 100 messages, out of which 38th message is a malformed one. The Adapter is not polling the particluar message and even it is blocking the remaining messages.

Is there an alternative to paralelly process the remaining 62 messages? by pass/ignore the malformed one.. though we will raise alert for that particular 38th message.. Basically the adapter should not be a hurdle..

Any Ideas?

Ramani

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Ramani,

These cases are generally seen when using FTP when the file channel gets locked by accessing such malformed file and it blocks the other files from getting picked.

To remove such locks you need to manually goto Visual Admin at server level , and delete the locks from the service--> Locking Adapter. You can see your channel name here. Select the channel and delete the lock.

To avoid doing this manually everytime you can do the below Configure a parameter "Timeout(secs)" in the Source tab, add 300 secs as the value.

Try doing this, it should help you.

Thanks

Dhwani

Answers (2)

Answers (2)

Former Member
0 Kudos

If you have FCC and the malformation of file is due to excess/less fields then try using

NameA.missingLastfields and NameA.additionalLastFields.

Then the file will be picked by fileadapter but error out with mapping exception. The file channel continues with next file.

former_member187339
Active Contributor
0 Kudos

Hi Ramani,

>>Is there an alternative to paralelly process the remaining 62 messages? by pass/ignore the malformed one.. though we will raise alert for that particular 38th message.. Basically the adapter should not be a hurdle..

Remove EOIO then the alert will be raised but messages will not be effected. But if you have EOIO then the failed message need to be manually removed and then only further processing will happen... This is EOIO (exactly once and that too in order..)

Regards

Suraj