Dispatcher is not initialized


Please look at this bellow error provide the solution.

8833],ErrorMsg=com.wm.app.b2b.server.ServiceException: [ISS.0098.9013]
Dispatcher is not initialized,ServiceName=wm.server.publish:publish<<<.
[8832] at java.lang.Thread.run(Thread.java:534)
[8831] at com.wm.util.pool.PooledThread.run(PooledThread.java:105)
[8830] at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:312)
[8829] at com.wm.app.b2b.server.InvokeHandler.process(InvokeHandler.java:119)

Did you resolve this issue?If so please let me know the resolution

What is your webMethdos version?

Did you restart your server in order for the dispatcher to load and start automatically?

Did you make sure the broker settings are correct on IS admin under Messaging?

Did you check your dispatch.cnf file in your integration server config directory. See if it matches with your broker settings. If its not you can back up the file, get the IS down and delete it from the config folder and restart the server.

Happy New Year 2015 :slight_smile:

Hello All,
Issue resolved by doing following steps:

1.Shut down the server
2.Clean the cache
3.Remove below files from IS folder
4.Restart server

I am not sure whether you have noticed the below information:

/DocumentStore - The files in this subdirectory contain the locally persisted documents being processed by the Integration Server. The loss of these files will result in the loss of any persisted documents.

/WmRepository4 - The files in this subdirectory contain metadata for the Integration Server. The loss of
these files could result in loss of configuration information and may require manual reconfiguration.

did you make sure that your configuration are correct after you resolved the issue.

Hi There,

As per design, the Dispatcher is initialized at very beginning of IS startup but it actually starts its activity of sending towards Broker and receiving events from Broker after all the packages are loaded.

Dispatcher needs the namespace to be loaded before starting the receiving and sending the events. In startup service, we can’t wait for the Dispatcher to start because for the Dispatcher to start the namespace should be loaded.

So, it is not possible to build an startup service which uses a built-in service that involves the Dispatcher, like in this case the built-in service “pub.publish:publish”.