org.mule.api.lifecycle.InitialisationException: Service not set, this service has not been initialized properly.

MuleSoft JIRA | Victor Bonillo | 5 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    See configuration posted here. When you send a message to a flow containing a WSProxyService component, it throws an exception. This does not fail on Mule startup, but when the first message is received. The weird part is that this will NOT fail when using a service with identical configuration. Steps to reproduce: 1) Deploy the app. 2) Send message to http://0.0.0.0:8090/service/MyProxy. Curling it like this should be enough: curl http://0.0.0.0:8090/service/MyProxy 3) You will get this message: ERROR 2011-11-03 13:19:04,594 [HttpConnector.receiver.09] org.mule.exception.DefaultMessagingExceptionStrategy: ******************************************************************************** Message : Service not set, this service has not been initialized properly. Code : MULE_ERROR-71999 -------------------------------------------------------------------------------- Exception stack is: 1. Service not set, this service has not been initialized properly. (org.mule.api.lifecycle.InitialisationException) org.mule.module.cxf.WSProxyService:254 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/lifecycle/InitialisationException.html) -------------------------------------------------------------------------------- Root Exception stack trace: org.mule.api.lifecycle.InitialisationException: Service not set, this service has not been initialized properly. at org.mule.module.cxf.WSProxyService.initialise(WSProxyService.java:254) at org.mule.module.cxf.WSProxyService.onCall(WSProxyService.java:113) at org.mule.model.resolvers.CallableEntryPointResolver.invoke(CallableEntryPointResolver.java:50) + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ******************************************************************************** Also, you will get this line in the HTTP response: Component that caused exception is: DefaultJavaComponent{MyProxy.commponent.726841077}. Message payload is of type: String 4) Stop mule. 5) Comment the "MyProxy" flow, uncomment the "MyProxy" service. 6) Start Mule 7) Send message to http://0.0.0.0:8090/service/MyProxy. Curling it like this should be enough: curl http://0.0.0.0:8090/service/MyProxy 8) This time, no errors are displayed.

    MuleSoft JIRA | 5 years ago | Victor Bonillo
    org.mule.api.lifecycle.InitialisationException: Service not set, this service has not been initialized properly.
  2. 0

    See configuration posted here. When you send a message to a flow containing a WSProxyService component, it throws an exception. This does not fail on Mule startup, but when the first message is received. The weird part is that this will NOT fail when using a service with identical configuration. Steps to reproduce: 1) Deploy the app. 2) Send message to http://0.0.0.0:8090/service/MyProxy. Curling it like this should be enough: curl http://0.0.0.0:8090/service/MyProxy 3) You will get this message: ERROR 2011-11-03 13:19:04,594 [HttpConnector.receiver.09] org.mule.exception.DefaultMessagingExceptionStrategy: ******************************************************************************** Message : Service not set, this service has not been initialized properly. Code : MULE_ERROR-71999 -------------------------------------------------------------------------------- Exception stack is: 1. Service not set, this service has not been initialized properly. (org.mule.api.lifecycle.InitialisationException) org.mule.module.cxf.WSProxyService:254 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/lifecycle/InitialisationException.html) -------------------------------------------------------------------------------- Root Exception stack trace: org.mule.api.lifecycle.InitialisationException: Service not set, this service has not been initialized properly. at org.mule.module.cxf.WSProxyService.initialise(WSProxyService.java:254) at org.mule.module.cxf.WSProxyService.onCall(WSProxyService.java:113) at org.mule.model.resolvers.CallableEntryPointResolver.invoke(CallableEntryPointResolver.java:50) + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ******************************************************************************** Also, you will get this line in the HTTP response: Component that caused exception is: DefaultJavaComponent{MyProxy.commponent.726841077}. Message payload is of type: String 4) Stop mule. 5) Comment the "MyProxy" flow, uncomment the "MyProxy" service. 6) Start Mule 7) Send message to http://0.0.0.0:8090/service/MyProxy. Curling it like this should be enough: curl http://0.0.0.0:8090/service/MyProxy 8) This time, no errors are displayed.

    MuleSoft JIRA | 5 years ago | Victor Bonillo
    org.mule.api.lifecycle.InitialisationException: Service not set, this service has not been initialized properly.

    Root Cause Analysis

    1. org.mule.api.lifecycle.InitialisationException

      Service not set, this service has not been initialized properly.

      at org.mule.module.cxf.WSProxyService.initialise()
    2. CXF Module
      WSProxyService.onCall
      1. org.mule.module.cxf.WSProxyService.initialise(WSProxyService.java:254)
      2. org.mule.module.cxf.WSProxyService.onCall(WSProxyService.java:113)
      2 frames
    3. Mule Core
      CallableEntryPointResolver.invoke
      1. org.mule.model.resolvers.CallableEntryPointResolver.invoke(CallableEntryPointResolver.java:50)
      1 frame