org.mule.umo.ComponentException: Direct access to underlying service object is not allowed in the SedaModel. If this is for a unit test, make sure you are using the TestSedaModel ('seda-test'). Component that caused exception is: hop1. The current UMOMessage is null! Please report this to null

MuleSoft JIRA | Andrew Perepelytsya | 9 years ago
  1. 0

    {panel} ================================================================================ = Testing: multicast routing over two endpoints = = (org.mule.providers.vm.issues.MulticastRouterMule2112TestCase) = ================================================================================ org.mule.umo.ComponentException: Direct access to underlying service object is not allowed in the SedaModel. If this is for a unit test, make sure you are using the TestSedaModel ('seda-test'). Component that caused exception is: hop1. The current UMOMessage is null! Please report this to null at org.mule.impl.model.seda.SedaComponent.getInstance(SedaComponent.java:675) at org.mule.providers.vm.issues.MulticastRouterMule2112TestCase.testMulticastRoutingOverTwoEndpoints(MulticastRouterMule2112TestCase.java:34) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.mule.tck.AbstractMuleTestCase.runBare(AbstractMuleTestCase.java:206) at org.mule.tck.AbstractMuleTestCase.run(AbstractMuleTestCase.java:176) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:40) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90) Process finished with exit code -1 {panel}

    MuleSoft JIRA | 9 years ago | Andrew Perepelytsya
    org.mule.umo.ComponentException: Direct access to underlying service object is not allowed in the SedaModel. If this is for a unit test, make sure you are using the TestSedaModel ('seda-test'). Component that caused exception is: hop1. The current UMOMessage is null! Please report this to null
  2. 0

    {panel} ================================================================================ = Testing: multicast routing over two endpoints = = (org.mule.providers.vm.issues.MulticastRouterMule2112TestCase) = ================================================================================ org.mule.umo.ComponentException: Direct access to underlying service object is not allowed in the SedaModel. If this is for a unit test, make sure you are using the TestSedaModel ('seda-test'). Component that caused exception is: hop1. The current UMOMessage is null! Please report this to null at org.mule.impl.model.seda.SedaComponent.getInstance(SedaComponent.java:675) at org.mule.providers.vm.issues.MulticastRouterMule2112TestCase.testMulticastRoutingOverTwoEndpoints(MulticastRouterMule2112TestCase.java:34) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.mule.tck.AbstractMuleTestCase.runBare(AbstractMuleTestCase.java:206) at org.mule.tck.AbstractMuleTestCase.run(AbstractMuleTestCase.java:176) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:40) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90) Process finished with exit code -1 {panel}

    MuleSoft JIRA | 9 years ago | Andrew Perepelytsya
    org.mule.umo.ComponentException: Direct access to underlying service object is not allowed in the SedaModel. If this is for a unit test, make sure you are using the TestSedaModel ('seda-test'). Component that caused exception is: hop1. The current UMOMessage is null! Please report this to null
  3. 0

    Start Page: /home/CPAS/Forum

    labkey.org | 1 year ago
    org.mule.umo.ComponentException: Failed to invoke org.labkey.pipeline.mule.PipelineJobRunner. Component that caused exception is: PipelineJobRunnerUMO. Message payload is of type: ActiveMQTextMessage
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Start Page: /home/Demos/CPAS/Forum

    labkey.org | 4 months ago
    org.mule.umo.ComponentException: Failed to invoke org.labkey.pipeline.mule.PipelineJobRunner. Component that caused exception is: PipelineJobRunnerUMO. Message payload is of type: ActiveMQTextMessage
  6. 0

    Mirth channel performs replication messages between two tables in a local DBMS on the same server as Mirth, polling each 500 ms 100 new messages. Mirth 2.1 RC1 , 256 MB Java Heap size, on Windows XP pro 32 / 2 GB RAM using Oracle 10gR2 SGBD. (same error with the same test using Postgres 8.4 SGBD for Mirth 2.1 RC1 + inbound and outbound Postgres tables) The error occurred after a start and stop of the channel , Having previously received a significant number of messages - in full archive mode - (here after 100,000 msg , 0.7 KB/msg sized, for this test). For each message received (archived as received but not distributed): (not marked as Sent, nor errored or queued) the following error in Mirth log: [2011-04-21 17:11:21,542] ERROR (com.mirth.connect.connectors.jdbc.JdbcMessageReceiver:194): Error in channel: ZBR1_Y1_ADT_DEPUIS_CPAGE org.mule.umo.ComponentException: Cannot route event as component "f28d7ea9-8e4d-46db-9c38-6fca9e4838af" is stopped. Connector that caused exception is: f28d7ea9-8e4d-46db-9c38-6fca9e4838af. Message payload is of type: org.apache.commons.dbutils.BasicRowProcessor$CaseInsensitiveHashMap at org.mule.impl.model.AbstractComponent.sendEvent(AbstractComponent.java:258) at org.mule.impl.MuleSession.sendEvent(MuleSession.java:201) at org.mule.routing.inbound.InboundMessageRouter.send(InboundMessageRouter.java:176) at org.mule.routing.inbound.InboundMessageRouter.route(InboundMessageRouter.java:143) at org.mule.providers.AbstractMessageReceiver$DefaultInternalMessageListener.onMessage(AbstractMessageReceiver.java:487) at org.mule.providers.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:266) at org.mule.providers.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:229) at com.mirth.connect.connectors.jdbc.JdbcMessageReceiver.processMessage(JdbcMessageReceiver.java:179) at org.mule.providers.TransactedPollingMessageReceiver$1.doInTransaction(TransactedPollingMessageReceiver.java:98) at org.mule.transaction.TransactionTemplate.execute(TransactionTemplate.java:72) at org.mule.providers.TransactedPollingMessageReceiver.poll(TransactedPollingMessageReceiver.java:104) at org.mule.providers.PollingMessageReceiver.run(PollingMessageReceiver.java:97) at org.mule.impl.work.WorkerContext.run(WorkerContext.java:290) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575) at java.lang.Thread.run(Unknown Source)

    Mirth Project | 6 years ago | Bruno MARTIN
    org.mule.umo.ComponentException: Cannot route event as component "f28d7ea9-8e4d-46db-9c38-6fca9e4838af" is stopped. Connector that caused exception is: f28d7ea9-8e4d-46db-9c38-6fca9e4838af. Message payload is of type: org.apache.commons.dbutils.BasicRowProcessor$CaseInsensitiveHashMap

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. org.mule.umo.ComponentException

      Direct access to underlying service object is not allowed in the SedaModel. If this is for a unit test, make sure you are using the TestSedaModel ('seda-test'). Component that caused exception is: hop1. The current UMOMessage is null! Please report this to null

      at org.mule.impl.model.seda.SedaComponent.getInstance()
    2. org.mule.impl
      SedaComponent.getInstance
      1. org.mule.impl.model.seda.SedaComponent.getInstance(SedaComponent.java:675)
      1 frame
    3. org.mule.providers
      MulticastRouterMule2112TestCase.testMulticastRoutingOverTwoEndpoints
      1. org.mule.providers.vm.issues.MulticastRouterMule2112TestCase.testMulticastRoutingOverTwoEndpoints(MulticastRouterMule2112TestCase.java:34)
      1 frame
    4. Java RT
      DelegatingMethodAccessorImpl.invoke
      1. sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      2. sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      3. sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      3 frames
    5. Mule Functional Test Framework (TCK)
      AbstractMuleTestCase.run
      1. org.mule.tck.AbstractMuleTestCase.runBare(AbstractMuleTestCase.java:206)
      2. org.mule.tck.AbstractMuleTestCase.run(AbstractMuleTestCase.java:176)
      2 frames
    6. IDEA
      JUnitStarter.main
      1. com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:40)
      1 frame
    7. Java RT
      DelegatingMethodAccessorImpl.invoke
      1. sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      2. sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      3. sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      3 frames
    8. IDEA
      AppMain.main
      1. com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)
      1 frame