Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-6683

camel-sap component fails to start periodically

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • fuse-7.1
    • jboss-fuse-6.2.1
    • Camel
    • % %
    • Hide

      1. Configure an integration with SAP
      2. Start Camel route
      or
      1. Shutdown camel-sap or Fuse instance by any correct way when integration with SAP is configured
      2. Start camel-sap of Fuse instance

      Show
      1. Configure an integration with SAP 2. Start Camel route or 1. Shutdown camel-sap or Fuse instance by any correct way when integration with SAP is configured 2. Start camel-sap of Fuse instance

      Camel-sap fails to start from time to time with this exception:

      2017-03-21 18:33:47,135 | WARN | org.fusesource.camel.component.sap.SapSynchronousRfcServerComponent | | | 251 - org.fusesource.camel-sap - 6.2.1.redhat-169 | JCoServerThread-19 | >>> Error occured on ... connection ...|3303|...
      java.lang.ExceptionInInitializerError
      at java.lang.J9VMInternals.ensureError(J9VMInternals.java:134)[:1.7.0]
      at java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:123)[:1.7.0]
      at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.addNamespaceDeclarations(XMLSaveImpl.java:894)
      at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.traverse(XMLSaveImpl.java:601)
      at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.save(XMLSaveImpl.java:251)
      at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doSave(XMLResourceImpl.java:331)
      at org.eclipse.emf.ecore.resource.impl.ResourceImpl.save(ResourceImpl.java:1417)
      at org.eclipse.emf.ecore.resource.impl.ResourceImpl.save(ResourceImpl.java:986)
      at org.fusesource.camel.component.sap.util.Util.save(Util.java:138)[251:org.fusesource.camel-sap:6.2.1.redhat-169]
      at org.fusesource.camel.component.sap.ServerTIDHandler.saveTIDs(ServerTIDHandler.java:151)[251:org.fusesource.camel-sap:6.2.1.redhat-169]
      at org.fusesource.camel.component.sap.ServerTIDHandler.checkTID(ServerTIDHandler.java:87)[251:org.fusesource.camel-sap:6.2.1.redhat-169]
      at com.sap.conn.jco.rt.DefaultServerWorker.onCheckTID(DefaultServerWorker.java:202)[sapjco3.jar:20161207 2131 [3.0.16 (2016-12-06)]]
      at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2927)[sapjco3.jar:20161207 2131 [3.0.16 (2016-12-06)]]
      at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2860)[sapjco3.jar:20161207 2131 [3.0.16 (2016-12-06)]]
      at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2656)[sapjco3.jar:20161207 2131 [3.0.16 (2016-12-06)]]
      at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:275)[sapjco3.jar:20161207 2131 [3.0.16 (2016-12-06)]]
      at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:356)[sapjco3.jar:20161207 2131 [3.0.16 (2016-12-06)]]
      at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:232)[sapjco3.jar:20161207 2131 [3.0.16 (2016-12-06)]]
      at java.lang.Thread.run(Thread.java:809)[:1.7.0]
      Caused by: java.lang.NullPointerException
      at org.eclipse.emf.ecore.xml.namespace.impl.XMLNamespacePackageImpl.initializePackageContents(XMLNamespacePackageImpl.java:356)[251:org.fusesource.camel-sap:6.2.1.redhat-169]
      at org.eclipse.emf.ecore.xml.namespace.impl.XMLNamespacePackageImpl.init(XMLNamespacePackageImpl.java:128)[251:org.fusesource.camel-sap:6.2.1.redhat-169]
      at org.eclipse.emf.ecore.xml.namespace.XMLNamespacePackage.<clinit>(XMLNamespacePackage.java:69)[251:org.fusesource.camel-sap:6.2.1.redhat-169]
      ... 17 more

      and it seems to be related with failure of initialization of TID store.

      The issue could be related with this: Bug 394659

            Unassigned Unassigned
            elomonos Evgenii Lomonosov (Inactive)
            Jan Bouska Jan Bouska
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: