IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

Business connector exceptions

  • 1.  Business connector exceptions

    Posted Mon September 12, 2005 04:32 PM

    Hi,

    I am getting the following error once BC server was restarted after a power shutdown.Need to know the rootcause of these exceptions and wat they mean.also how they can be eliminated as these errors keep repeating.There seems to be data loss due to these exceptions in the inbound side.The actual process is that idocs are being sent from sap to an external vendor through business connector.

    Error being reported is:

    com.sap.mw.jco.JCO$Exception: (108) RFC_ERROR_INTERNAL: internal error

    at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeCreateTID(Native Method)

    at com.sap.mw.jco.rfc.MiddlewareRFC$Client.createTID(MiddlewareRFC.java:1246)

    at com.sap.mw.jco.JCO$Client.createTID(JCO.java:3903)

    at com.wm.pkg.sap.rfc.SAPSession.createTID(SAPSession.java:768)

    at pub.sap.client.createTID(client.java:373)

    at java.lang.reflect.Method.invoke(Native Method)

    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)

    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)

    at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)

    at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)

    at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)

    at com.wm.lang.flow.FlowState.step(FlowState.java:430)

    at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)

    at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)

    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)

    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:496)

    at wm.server.net.EmailTransaction$RunService.write(EmailTransaction.java:1375)

    at wm.server.net.EmailTransaction$RunService.run(EmailTransaction.java:1218)

    at com.wm.util.pool.PooledThread.run(C:/NT/Perforce/basis/4.1.0-terra/module/core/source/com/wm/util/pool/PooledThread.java:103)

    at java.lang.Thread.run(Unknown Source)

    and

    com.sap.mw.idoc.IDoc$Exception: (3) IDOC_ERROR_ILLEGAL_TYPE: The document does not correspond to the associated repository.

    at com.sap.mw.idoc.jco.JCoIDoc$JCoDocumentList.add(JCoIDoc.java:3095)

    at com.wm.pkg.sap.rfc.SAPSession.sendIDoc(SAPSession.java:671)

    at pub.sap.client.sendIDoc(client.java:356)

    at java.lang.reflect.Method.invoke(Native Method)

    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)

    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)

    at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)

    at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)

    at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)

    at com.wm.lang.flow.FlowState.step(FlowState.java:430)

    at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)

    at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)

    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)

    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:496)

    at wm.server.net.EmailTransaction$RunService.write(EmailTransaction.java:1375)

    at wm.server.net.EmailTransaction$RunService.run(EmailTransaction.java:1218)

    at com.wm.util.pool.PooledThread.run(C:/NT/Perforce/basis/4.1.0-terra/module/core/source/com/wm/util/pool/PooledThread.java:103)

    at java.lang.Thread.run(Unknown Source).

    please clarify on this regard.

    thanks in advance.

    r


    #Integration-Server-and-ESB
    #webMethods
    #Adapters-and-E-Standards


  • 2.  RE: Business connector exceptions

    Posted Mon September 12, 2005 05:15 PM

    Generally this happens when your IDOC is not well formatted (i mean not well structured).

    Just check the parent child relationship of the segments in SAP and check whether they are satified in BC.

    This error comes from SAP, when it tries to read the IDOC.

    HTH
    BS


    #webMethods
    #Integration-Server-and-ESB
    #Adapters-and-E-Standards