![]() This will ensure that the service does not run before Integration Server has started. The startup service can then call the service that you want to run. 08:50:05 CEST Dispatcher startedįor Integration Server 6.0.1, install the appropriate fix.Ĭreate a startup service that first calls a Java service that sleeps for a period of time that is longer than the time is takes Integration Server to start up. The Dispatcher has fully started only after the following line is written in the server log: Integration Server creates a new dispatch.cnf file during the startup sequence. If the dispatch.cnf file is corrupted, back up the file, delete the original file, and restart Integration Server. Problems exist with the dispatch.cnf file. This error might occur for the following reasons:Ī package startup service, or a scheduled service that uses Broker publishing, is invoked before the Integration Server and the Dispatcher have fully started. Hangs After the Line Dispatcher Is Not Initialized 20:16:08 CST WmRNIF20TRP: Startup service (wm.ip.rnif20.mime:init)Ĭan please try this one. ![]() 20:16:08 CST WmRNIF20TRP: Startup service (wm.ip.rnif20.util:init) 20:16:08 CST WmRNLargeDocSample: Startup service (wm.b2b.rn.largeDocSample.init:startup) 20:16:08 CST WmRosettaNet: Startup service (wm.ip.rn.util:init) 20:16:08 CST WmRNIF11TRP: Startup service (wm.ip.rnif11.util:init) 20:16:08 CST WmIPRoot: Startup service (wm.ip.util:init) 20:16:08 CST WmPRT: Startup service (wm.prt.admin:brokerPush) 18:30:39 CST WmPRT: Startup service (wm.prt.admin:startup) 18:30:39 CST WmAdmin: Startup service (wm.administrator.admin:initialize) 18:30:39 CST WmAdmin: Startup service (wm.administrator.repo:centralRepoRegister) 18:30:39 CST WmPKI: Startup service (wm.:init) 18:30:39 CST WmDB: Startup service (wm.server.db:startup) I think this case is not normal,why these two step need 106 mins,please help me resolve this issue. I try to startup the webmethods6.1 IS service,then i wait and wait …and at last i find it need a long time to startup IS service successful about two hours.Then i check the serverlog and find there need 106 mins between one step(wm.prt.admin:startup) and next step(wm.prt.admin:brokerPush). There has old version webMethods about 6.1 and the OS version is Windows 2003.Īt 5/22, i want to shutdown ths IS ,but the shutdown command was not worked in half an hour.Then i forced to shutdown the webMethods services at windows task manager. I has one issue about WebMehods 6.1 IS startup.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |