Debugging JMS adapter with Module Configuration

Question

Hi.
I have a problem debugging my JMS adapter with module configuration.
All I get from the Message Monitor is a status "System Error", and no error category or error message.
I know there's an error in my Module configuration design, since it works fine without.
My configuration looks like this:
PROCESSING SEQUENCE:
1     localejbs/AF_Modules/MessageTransformBean     Local Enterprise Bean     XML2Plain
2     localejbs/SAP XI JMS Adapter/ConvertMessageToBinary     Local Enterprise Bean     convert_XI2Bin
3     localejbs/SAP XI JMS Adapter/SendBinarytoXIJMSService     Local Enterprise Bean     exit
MODULE CONFIGURATION:
XML2Plain     Transform.Class     com.sap.aii.messaging.adapter.Conversion
XML2Plain     Transform.ContentType     text/plain;charset=utf-8
XML2Plain     xml.conversionType     StructXML2Plain
XML2Plain     xml.addHeaderLine     0
XML2Plain     xml.recordsetStructure     STARTRECORD,DATARECORD,SERVICEYDELSERRECORD,SLUTRECORD
XML2Plain     xml.STARTRECORD.fieldFixedLengths     2,8,6,7,10,7,3,3
XML2Plain     xml.DATARECORD.fieldFixedLengths     2,8,6,4,35,17,7,7,7,5,5,5,18,18,18,18,18,18,18,18,18,9
XML2Plain     xml.SERVICEYDELSERRECORD.fieldFixedLengths     2,8,6,4,3,20,18,18,18
XML2Plain     xml.SLUTRECORD.fieldFixedLengths     2,8,6,7,10,7
XML2Plain     xml.STARTRECORD.fixedLengthTooShortHandling     Cut
XML2Plain     xml.DATARECORD.fixedLengthTooShortHandling     Cut
XML2Plain     xml.SERVICEYDELSERRECORD.fixedLengthTooShortHandling     Cut
XML2Plain     xml.SLUTRECORD.fixedLengthTooShortHandling     Cut
The structure of the message looks like this:
<STARTRECORD> (occurence = 1)
<DATARECORD> (occurence = 1..unbounded)
--- <SERVICEYDELSERRECORD> (occurence = 0..unbounded)
<SLUTRECORD> (occurence = 1)
I've crosschecked every field, and it length and all looks like it should!
The worst part is the one not getting the reason why it fails. Any way I can get this information?
I've tried to look in the Adapter Framework log, but I have no clue where to look for anything usefull.
Help
Regards Peter

Answer 1

Hello,
Below is the module configuration in my JMS sender channel:
Check Message          Local Enterprise Bean          key
ConvertJMSMessageToBinary      Local Enterprise Bean      convert_JMS2Bin
ConvertBinaryToXMBMessage     Local Enterprise Bean      convert_Bin2XI
CallSapAdapter                Local Enterprise Bean          call_AF_MS
CheckMessage is a custom module which does some check on the incoming message.
Now what I want to know is at which position should I include the DynamicConfiguration Bean? Should it be included at position 1 or at position 2 or someother position?
~Thanks.