cancel
Showing results for 
Search instead for 
Did you mean: 

SP14 Module Processor Issue

Former Member
0 Kudos
53

Hello,

I hava developped in SP10 multiple Module Processor and everything works fine.

I have upgraded to SP14 and redeployed the Module Processor and at each execution of a Module Processor, i've got the error in RWB/Monitoring Adapter : "java.lang.ClassCastException" ?????

I somebody as an idea.

Regards,

Vincent

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Tssssssssss what a nightmare, how to make simple when one can make complicated !!!!!

Regards,

Vincent

Former Member
0 Kudos

Alex,

Why i are you tell that it was strange that the module processor works without "localejbs" ?

Second thing, when i try to process an empty file, the file disapear of the directory but nothing is sent to IS and the module processor doesn't execute, have you got an idea ?

Regards,

Vincent

former_member184154
Active Contributor
0 Kudos

> Why i are you tell that it was strange that the

> module processor works without "localejbs" ?

Because apart from the JNDI name that you chose for your module when deploying, I've always seen "localejbs/" before it when declaring the module chain...

> Second thing, when i try to process an empty file,

> the file disapear of the directory but nothing is

> sent to IS and the module processor doesn't execute,

> have you got an idea ?

Empty file is picked up anyway, but as there's no payload to process, nothing happens and no data are sent to IS. Quite correct

Cheers,

Alex

Former Member
0 Kudos

OK for JNDI but for the empty it's a problem, let me explain the scenario :

I have configured a file sender adapter with file Content Conversion. I have 2 kinds of records Header and Items.

i have defined the 'Key Field Name' based on the first character of each line of my flat file and the values associated :

Header.keyFieldValue = 1

Item.keyFieldValue = 2

Flat file example :

1;Headerfield1;Headerfield2

2;ItemField1;ItemField2;ItemField3;ItemField4;

2;ItemField1;ItemField2;ItemField3;ItemField4;

2;ItemField1;ItemField2;ItemField3;ItemField4;

and everything works fine !

But now imagine you receive a bad file like this :

xxxxx;ohhohoh;llllll

y;sdfsdfs;zezerz;zerzer

e;zerzerze;zezerzerzer

The result is : No error is generated (first why ???? ) and because the adapter cannot match the keyFieldValue it seems consider that it has received an empty file and nothing is sent to IS so no alert is generated ????? in this case the approach is not really correct !

Regards,

Vincent

former_member184154
Active Contributor
0 Kudos

Wow, you're right.

The adapter is very tolerant and sometimes even ignorant but, believe me, I've already opened an OSS message for this, and the answer was "nada", <i>the adapter is just like that</i>. Basically SAP's claim is that the Adapter should not be trapping this kind of errors.

Actually what is it supposed to do in this case?

My suggestion is that you write a module to do some preprocessing checks on the file and based on that you can fire en email or whatever. Sounds too housemade? It is, but the std is of no help in this case, as far as I know at least.

Alex

Message was edited by: Alessandro Guarneri

Former Member
0 Kudos

I think i have found, the problem is with the JNDI Name.

If i declare in hte module part of the Adapter configuration, the JNDI Name of the EJB with "localejbs" at first it works ????????????? so strange....

Regards,

Vincent

former_member184154
Active Contributor
0 Kudos

Actually it's strange it was working without "localejbs/"... but anyway, good job.

Regards,

Alex

former_member184154
Active Contributor
0 Kudos

Try looking in log and trace file. That should help you find the exact line nr in your java code that is throwing the exc.

Paste it here.

Alex

Former Member
0 Kudos

Hello Alex,

I have got this error in trc file :

#1.5#02004C4F4F500057000014120000082C00040A294826598D#1137072327093#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#2##sa_C11_1778150#Guest#d7adf720836c11da877002004c4f4f50#XI AF File2XI[:DEFASER:READ_MM02]##0#0#Warning##Java###Catching #1#com.sap.engine.services.ts.exceptions.BaseIllegalStateException: Thread is not associated with any transaction context.

at com.sap.engine.services.ts.jta.impl.TransactionManagerImpl.rollback(TransactionManagerImpl.java:483)

at com.sap.aii.adapter.file.File2XI.processFileList(File2XI.java:1598)

at com.sap.aii.adapter.file.File2XI.invoke(File2XI.java:602)

at com.sap.aii.af.service.scheduler.JobBroker$Worker.run(JobBroker.java:449)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)