org.apache.axis2.AxisFault

The input stream for an incoming message is null. ERROR [WatchDog] - Graph execution finished with error ERROR [WatchDog] - Node ENDECA_ADD_OR_UPDATE_RECORDS0 finished with status: ERROR caused by: Component pre-execute initialization failed. ERROR [WatchDog] - Node ENDECA_ADD_OR_UPDATE_RECORDS0 error details: Element [ENDECA_ADD_OR_UPDATE_RECORDS0:Add/Update Records]-Component pre-execute initialization failed.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web1265

  • The input stream for an incoming message is null. ERROR [WatchDog] - Graph execution finished with error ERROR [WatchDog] - Node ENDECA_ADD_OR_UPDATE_RECORDS0 finished with status: ERROR caused by: Component pre-execute initialization failed. ERROR
  • via Oracle Community by 957489, 1 year ago
    The input stream for an incoming message is null. ERROR [WatchDog] - Graph execution finished with error ERROR [WatchDog] - Node ENDECA_ADD_OR_UPDATE_RECORDS0 finished with status: ERROR caused by: Component pre-execute initialization failed. ERROR
  • Error while obtaining API information from gateway. The input stream for an incoming message is null.
  • Stack trace

    • org.apache.axis2.AxisFault: The input stream for an incoming message is null. ERROR [WatchDog] - Graph execution finished with error ERROR [WatchDog] - Node ENDECA_ADD_OR_UPDATE_RECORDS0 finished with status: ERROR caused by: Component pre-execute initialization failed. ERROR [WatchDog] - Node ENDECA_ADD_OR_UPDATE_RECORDS0 error details: Element [ENDECA_ADD_OR_UPDATE_RECORDS0:Add/Update Records]-Component pre-execute initialization failed. at org.jetel.graph.Node.run(Node.java:407) at java.lang.Thread.run(Thread.java:619)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.