cancel
Showing results for 
Search instead for 
Did you mean: 

File adapter - Unexpected exception running file2xmbprocessor

Former Member
0 Kudos

Hallo,

I've a fileadapter running and a couple of time the adapter is running fine.

After a while I get the following exception:

-


<i>Unexpected exception running file2xmbprocessor

java.util.NoSuchElementException

at java.util.TreeMap$EntryIterator.nextEntry(TreeMap.java:1024)

at java.util.TreeMap$KeyIterator.next(TreeMap.java:1051)

at com.sap.aii.messaging.adapter.File2XMBProcessor.processFileAccess(ModuleFile2XMB.java:1383)

at com.sap.aii.messaging.adapter.File2XMBProcessor.run(ModuleFile2XMB.java:872)

at java.lang.Thread.run(Thread.java:534)

File adapter processing stopped</i>

-


I have no idea whats wrong.

Any idea

Thanks harald

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member189324
Contributor
0 Kudos

Hi Harald,

You have a problem in your mapping. Test the mapping first and correct the errors.

Regards

Prasad

SAP Netwaver RIG-XI

SAP Labs LLC, USA

Former Member
0 Kudos

Hi Prasad,

sorry - but I can't understand what you mean.

The file-adapter I'm talking about runs on a fileserver. This adapter read the files and send them to the XI-System where a java-mapping is running.

Therefore I can't believe that the problem is the mapping.

The way I see it is that the error must be in a part of the file-read-process because the exception says

<b><u>[fileprocessor]</u> Error: Unexpected exception running file2xmbprocessor

java.util.NoSuchElementException

at java.util.TreeMap$EntryIterator.nextEntry </b>

Could you please explain what you mean.

Thanks and best regards

Harald

Former Member
0 Kudos

Hallo Harald,

to me it seems that the file that should be processed, does not look like expected. Did you check the file that should be processed when this error appears?

I guess, you are sending an XML file, than you could check its validity against its schema definition.

Best regards

Christine

Former Member
0 Kudos

Hallo Christine,

thanks for the replay.

I've checked the files several times. It's not just one file, the problem appears with different files and in the next try the same file runs fine.

We have the same problem with different file adapters.

In my case the adapter is sending plain text files to XI. But we also send XML files and we have the same phenomenon.

Any other idea?

Best regards

Harald

Former Member
0 Kudos

Hi all,

the problem is solved.

We have pached the file-adapter-engine

from patchlevel 3 to patchlevel 4.

The bug was in the file-adapter by working with file.processingOrder = byDate

That's it.

Thanks and best regards

Harald