EP 6.0 SP2 P4 J2EE Cluster - 503! - Initialization of Dispatcher failed

Hello,
I have the following problem:
SAP EP-Version: J2EE Cluster with SAP EP 6.0 SP2 Patch 4 and J2EE PL23
After the Installation on the second Clusternode,
-> "Additional SAP J2EE System for a portal Cluster" I get after the call of the URL: "http://<Servername>:50000/irj" the following error message: "Service Unavailable 503! - javax.servlet.UnavailableException: Initialization of Dispatcher failed".
It looks like, that after the synchronisation no applications would have been copied to the second Clusternode. -> There are no irj-Folder as sample on the second Clusternode.
What is the problem? - How can I deploy the application later now ?
About your assistance I would be happy.
Thanks in advance.
Ralf

Hello John,
We have checked the configuration of the ports and none of the used (join port, open port) ports repeats itself inside the same host, adittional we have change ports that repeat in different host.
The problem presist.
Adittional I send error messages:
1.- When we try to access to EP 60 SP2 in BSC
Service Unavailable 503!
javax.servlet.UnavailableException: Initialization of Dispatcher failed
 at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:370)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:212)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.access$400(Dispatcher.java:40)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:447)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:415)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
 at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:665)
 at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:312)
 at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
 at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1229)
 at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
 at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
 at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
2.- Startup sequence in BSC.
Service Unavailable 503!
javax.servlet.UnavailableException: Initialization of Dispatcher failed
 at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:370)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:212)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.access$400(Dispatcher.java:40)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:447)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:415)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
 at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:665)
 at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:312)
 at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
 at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1229)
 at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
 at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
 at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
Portal initialization in progress ...
Loading core applications:
Loading application: com.sap.portal.license.runtime
Loading application: com.sap.portal.pcd.aclservice
Loading application: com.sap.portal.pcd.basicrolefactory
Loading application: com.sap.portal.pcd.basictransport
Loading application: com.sap.portal.pcd.configservice
Loading application: com.sap.portal.pcd.glservice
Loading application: com.sap.portal.pcd.lockservice
Loading application: com.sap.portal.pcd.plconnectionservice
Loading application: com.sap.portal.pcd.softcacheservice
Loading application: com.sap.portal.pcd.textrepository
Loading application: com.sap.portal.pcd.traceservice
Loading application: com.sap.portal.pcd.umwrapperservice
Loading application: com.sap.portal.pcm.admin.apiservice
Loading application: com.sap.portal.runtime.config
Loading application: com.sap.portal.runtime.system.authentication
Loading application: com.sap.portal.runtime.system.clusterinformation
Loading application: com.sap.portal.runtime.system.inqmy
Loading application: com.sap.portal.runtime.system.notification
Loading application: com.sap.portal.runtime.system.permission
Loading application: com.sap.portal.runtime.system.repository
Loading application: com.sap.portal.umeregistration
Loading application: com.sap.portal.usermanagement
Loading services:
Loading service: com.sap.portal.license.runtime|license
Loading service: com.sap.portal.pcd.aclservice|aclconnector
Loading service: com.sap.portal.pcd.basicrolefactory|factory
Loading service: com.sap.portal.pcd.basictransport|transport
Loading service: com.sap.portal.pcd.configservice|configuration
Loading service: com.sap.portal.pcd.glservice|generic_layer
Loading service: com.sap.portal.pcd.lockservice|locks
Loading service: com.sap.portal.pcd.plconnectionservice|connections
Loading service: com.sap.portal.pcd.softcacheservice|softcache
Loading service: com.sap.portal.pcd.textrepository|TextRepositoryService
Loading service: com.sap.portal.pcd.traceservice|traces
Loading service: com.sap.portal.pcd.umwrapperservice|umwrapper
Loading service: com.sap.portal.pcm.admin.apiservice|default
Loading service: com.sap.portal.runtime.config|config
Loading service: com.sap.portal.runtime.config|config_deployment
Loading service: com.sap.portal.runtime.system.authentication|authentication
Loading service: com.sap.portal.runtime.system.clusterinformation|clusterinformation
Loading service: com.sap.portal.runtime.system.notification|notification
Loading service: com.sap.portal.runtime.system.notification|SAPJ2EEHttpService
Loading service: com.sap.portal.runtime.system.repository|application_repository
Loading service: com.sap.portal.umeregistration|ume_registration
Loading service: com.sap.portal.usermanagement|usermanagement
Loading service: com.sap.portal.usermanagement|user_management_engine
Loading service: com.sap.portal.usermanagement|security
Aug 23, 2004 10:20:55 AM # System_Thread_84 Fatal [Portal.init] Application Broker - initialization failed.
com.sapportals.portal.prt.runtime.PortalException: [Portal Application Broker] applications start failed
 at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1223)
 at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1152)
 at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:343)
 at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:55)
 at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
 at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
 at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:124)
 at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
 at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
 at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
Caused by: com.sapportals.portal.prt.runtime.PortalException: [PortalServiceItem.startServices] service initialisation step 2 failed: com.sap.portal.usermanagement|user_management_engine
 at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:915)
 at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1262)
 at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1218)
 at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1152)
 at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:343)
 at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:55)
 at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
 at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
 at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:124)
 at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
 at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
 at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
Caused by: com.sapportals.portal.prt.core.broker.PortalServiceInstantiationException: Could not instantiate implementation class com.sap.ip.portal.service.ume.UserManagementEngine of Portal Service com.sap.portal.usermanagement|user_management_engine because: could not load the service
 at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:747)
 at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:909)
 at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1262)
 at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1218)
 at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1152)
 at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:343)
 at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:55)
 at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
 at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
 at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:124)
 at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
 at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
 at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
Caused by: java.lang.NullPointerException
 at com.sapportals.portal.prt.service.config.ConfigService.findArchiveWithName(ConfigService.java:1247)
 at com.sapportals.portal.prt.service.config.ConfigService.installPortalRootPlugin(ConfigService.java:1229)
 at com.sapportals.portal.prt.service.config.ConfigService.performInitialization(ConfigService.java:1036)
 at com.sapportals.portal.prt.service.config.ConfigService.internalInit(ConfigService.java:945)
 at com.sapportals.portal.prt.service.config.ConfigService.umeInitialized(ConfigService.java:398)
 at com.sap.portal.service.umeRegistration.UMERegistration.fireEvents(UMERegistration.java:123)
 at com.sap.portal.service.umeRegistration.UMERegistration.triggerMe(UMERegistration.java:109)
 at com.sap.ip.portal.service.ume.UserManagementEngine.fireEvents(UserManagementEngine.java:245)
 at com.sap.ip.portal.service.ume.UserManagementEngine.afterInit(UserManagementEngine.java:85)
 at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:736)
 at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:909)
 at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1262)
 at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1218)
 at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1152)
 at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:343)
 at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:55)
 at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
 at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
 at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:124)
 at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
 at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
 at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
java.security.PrivilegedActionException: com.sapportals.portal.prt.core.PortalCoreInitializerException: Main initialization of plugin failed
 at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:134)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
 at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
 at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:124)
 at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
 at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
 at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
Caused by: java.lang.IllegalStateException: [Portal.init] Application Broker - initialization failed.
 at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:349)
 at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:55)
 at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
 at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
 at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:124)
 at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
 at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
 at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
WARNING: Dispatcher could not be set up:
javax.servlet.UnavailableException: Initialization of Dispatcher failed
javax.servlet.UnavailableException: Initialization of Dispatcher failed
 at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:370)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
 at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
 at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:124)
 at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
 at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
 at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
com.sapportals.portal.prt.dispatcher.DispatcherException: Previous dispatcher initialization failed. Check logs for details.
 at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:256)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:212)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.access$400(Dispatcher.java:40)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:447)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:415)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
 at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
 at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:665)
 at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:312)
 at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
 at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1229)
 at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
 at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
 at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)

Similar Messages

J2EE cluster error while deploying "EAR" file from SDM tool

Hi all,
I am new to CRM ISA development side. I am learning how to build b2c ear file base on b2c.ear and then how to deploy through SDM. Everything is working fine till build tool. Successfully build my own b2c_ashish.ear file. then I started SDM GUI and try to deploy it. In SAP MMC all process are running. J2EE engine is also running fine. I have describe below which step I took.
PL. go through it an let me know about my mistake.
I am just pasting that portion of error which I am getting when I am accessing "/b2c_kce/b2c/init.do"
===================
A runtime error occurred
Contact the administrator
Start application
==================
do you have any idea in which log file it writes error so I can open that file and . I tried to access log file from "Admin" page.
If I am trying to access "/b2c_kce/admin/index.jsp" I am able to access those pages without problem only "/b2c_kce/b2c/init.do" I am getting problem like above "run time error Occured"
When I click on "Start Application" it is opening new window and showing same text.
I checked SAP MMC. it is showing all node Green "dgntisa", "dgntisa1" and "dgntisa0" Also All process like under "dgntisa0" process "jcontrol.exe" and "igswd.exe " are green.
I build "b2c_ashish" new by using build tool. It was also successful.
I start SDM server by "StartServer.bat" and after that I start SDM remote GUI.
I select "Deployment" tab and add "crm.b2c_ashish" for deployment then I click on Start button and I got below error for "J2EE Cluster" that "SDM could not start J2EE cluster on the host dgntisa"
Pl. if you have any idea then pl. let me know how to solve this error.
Deployment started Sun May 14 14:24:50 PDT 2006
===========================================================================
Starting Deployment of crm.b2c_ashish
Aborted: development component 'crm.b2c_ashish'/'sap.com'/'SAP AG'/'400.200605141307':
SDM could not start the J2EE cluster on the host dgntisa! The online deployment is terminated. JStartup Framework is not able to deliver an information about the cluster control instances! Please check the status of the J2EE Engine
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Deployment of crm.b2c_ashish finished with Error (Duration 3250 ms)
===========================================================================
Above error start ater restarting "WAS" server. Now You can not deploy or undeploy any SDA or SCA component.
I follow above mentioned steps 2 time after restarting "WAS" server. but it seems that one service for J2EE cluster is not started. I also chekced the running mode of SDM and SAP J2EE version. SDM Runing mode is "integrated" and SAP J2EE version is " 6.30" While using a build file it is showing J2EE engin version.
=======================================================

Would you post the same thread under SAP Netweaver or WAS?

SDM Deployment Failed--SDM could not start the J2EE cluster on the DB Host

HI,
I am trying to deploy ESS packges in EP through SDM.But while deploying I am getting this error in SDM at the start itself:-
Error: An error occured while starting a cluster instance.
Oct 14, 2008 5:14:41 PM Error: There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage
Please check if there is an appropriate running cluster instances
SDM could not start the J2EE cluster on the host SBPEPDB1! The online deployment is terminated.
There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage
I am pasting the full LOG File details:-
Oct 14, 2008 6:32:00 PM Info: Starting cluster instance processes.
Oct 14, 2008 6:32:00 PM Error: An error occured while starting a cluster instance.
Oct 14, 2008 6:32:00 PM Error: There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage . The instances, returned by MessageServer [MS host: SBPEPCI1; MS port: 3900], are :
Name:JM_T1223989073901_0_CPCAPP109
Host:SBPEPCI1
State:5
HostAddress:172.17.131.38
Name:JC_CPCAPP109_EPP_01
Host:CPCAPP109
State:5
HostAddress:172.17.131.31
Please check if there is an appropriate running cluster instances.
Oct 14, 2008 6:32:00 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 14, 2008 6:32:00 PM Error: Aborted: development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0', grouped by software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':
SDM could not start the J2EE cluster on the host SBPEPDB1! The online deployment is terminated.
There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage .
The instances, returned by MessageServer [MS host: SBPEPCI1; MS port: 3900], are :
Name:JM_T1223989073901_0_CPCAPP109
Host:SBPEPCI1
State:5
HostAddress:172.17.131.38
Name:JC_CPCAPP109_EPP_01
Host:CPCAPP109
State:5
HostAddress:172.17.131.31
Please check if there is an appropriate running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Oct 14, 2008 6:32:04 PM Info: Starting to save the repository
Oct 14, 2008 6:32:05 PM Info: Finished saving the repository
Oct 14, 2008 6:32:07 PM Info: Starting: Initial deployment: Selected software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0' will be deployed.
Oct 14, 2008 6:32:07 PM Error: Aborted: software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':
Failed deployment of SDAs:
development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0' : aborted
Please, look at error logs above for more information!
I have checked the CONFIGTOOl and the properties seem to be OK.
I tried SHUTTING DOWN all APPLICATION servers & Restarting the DEPLOYMENT,but it still Failed
Pls suggest.
Regards,
Abhijeet
I

Hi George,
Thnx for your reply.
I have stopped all Application servers and kept only the CI-DB instances running.Retried deploying the ESS packages but still getting the same error.
Have checked the Visual admin,it is not in SAFE mode,it working normally.
Have alos checked the CLUSTER Manager Property Values in both Visual Admin & Config Tool,they are alright.
About the Cluster Resources,can you pls specify what exactly do you mean by "Cluster Resources are running or not".
I think if the application servers are stopped,then the Cluster resources shudnt come into play right?? Correct me if I am wrong.
Kindly suggest what other steps I shud take.
Regards,
Abhijeet

J2EE Cluster Error while deploying ISA b2c.ear file.

Hi All,
I am trying to deploy b2c.ear file through SDM deploytool.
My build tool is working fine. In SAP MMC all node is green. All J2EE service is running. But when I try to deploy file through SDM i am getting below error.
Deployment started Sun May 14 14:24:50 PDT 2006
===========================================================================
Starting Deployment of crm.b2c_ashish
Aborted: development component 'crm.b2c_ashish'/'sap.com'/'SAP AG'/'400.200605141307':
SDM could not start the J2EE cluster on the host dgntisa! The online deployment is terminated. JStartup Framework is not able to deliver an information about the cluster control instances! Please check the status of the J2EE Engine
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Deployment of crm.b2c_ashish finished with Error (Duration 3250 ms)
===========================================================================
IF some one has any idea then pl. show me the way. I am new to CRM ISA side so pl. help me out.
Thanks in advance.
Ashish Patel.

Hi Rajesh,
Below is the part of the log file.
==============================
#1.5#0013D4B7BFFF002600000001000001A800041439E82CD452#1148138847796#com.sap.engine.services.monitor.common.Template##com.sap.engine.services.monitor.common.Template######25430f40e81511da9ca50013d4b7bfff#SAPEngine_System_Thread[impl:5]_52##0#0#Error##Plain###javax.management.InstanceNotFoundException: com.sap.default:name=com.sapmarkets.isa.core.jmx.ext.MyXCMInstProvider,SAP_J2EEApplicationPerNode=sap.com/crm.b2c_dgn,j2eeType=SAP_ApplicationResourcePerNode,SAP_J2EEClusterNode=8527350,SAP_J2EECluster=ITG not in repository
     at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1291)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)
     at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:300)
     at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:234)
     at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:559)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
     at com.sap.engine.services.monitor.mbeans.Template.pollDynamicData(Template.java:891)
     at com.sap.engine.services.monitor.mbeans.Template.handleNotification(Template.java:847)
     at com.sap.engine.services.jmx.server.AscynchronousProxyListener.handleNotification(AscynchronousProxyListener.java:51)
     at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:94)
     at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:61)
     at com.sap.engine.services.jmx.timer.j2ee.Timer.sendTimerNotification(Timer.java:407)
     at com.sap.engine.services.jmx.timer.j2ee.TimerNotificationEntry.timeout(TimerNotificationEntry.java:69)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:50)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)
=========================
According to log file it says that
SAP_J2EECLUSTER = ITG is not in Repository.
It looks like that some parameter setting is missing. Do you have any idea where I can set "SAP_J2EECLUSTER" Parameter.
Thanks.
Ashish Patel.

Seeburger logging in j2ee\cluster\tmp

Hello all,
We are experiencing massive logging in \j2ee\cluster\tmp. Numerous files (today over 5000 of them) with an .swp extention are created. In the files, the following text can be found:
InhouseDocReader moveNext(): com.seeburger.jucon.dochandler.TradacomDocReader Exception, offset[126(read Segment : STX)]: unexpected Subelement delimiter found : field STDS expected. : Group STX:STDS : Error at casting Group Description.
Maybe a field with the same name is existing...
DESCRIPTION: [not specified] at position [not specified] causes a general exception: [not specified]
Can somebody tell me where these files are comming from and how we can dam the flood of these files?
Kind regards, Wilbert

Hello all,
We are experiencing massive logging in \j2ee\cluster\tmp. Numerous files (today over 5000 of them) with an .swp extention are created. In the files, the following text can be found:
InhouseDocReader moveNext(): com.seeburger.jucon.dochandler.TradacomDocReader Exception, offset[126(read Segment : STX)]: unexpected Subelement delimiter found : field STDS expected. : Group STX:STDS : Error at casting Group Description.
Maybe a field with the same name is existing...
DESCRIPTION: [not specified] at position [not specified] causes a general exception: [not specified]
Can somebody tell me where these files are comming from and how we can dam the flood of these files?
Kind regards, Wilbert

Directory size of ...../ j2ee/cluster/server ?

Hi Everybody,
Can anyone pls tell me if their "server" directory size under ..../j2ee/cluster/server increased drastically after the installation of the ME 2.1 Server component on J2EE Engine on WAS 6.20.
A file called "dev_Icom" in the directory .../j2ee/cluster/server is taking away 11Gb.
Please confirm.
I am using J2EE SP24.
Thnx
Meesum
Message was edited by: Meesum Kirmani

HI,
If you do not enter the cluster ID,the EOIO channel is activated automatically on a different working node.
This configuration ensures node failover by the adapter in a clustered environment.
Regards,
Akshay Jamgaonkar.
Dont forget to give points.

WDRuntimeException: Failed to create J2EE cluster node in SLD

Hello,
I am getting the below error, but to my knowledge I have everything set up properly. Let me briefly outline the logistics (I am running everything LOCALLY (will move to remote later)):
WAS 6.4 SP12
Set up JCo and tests fine
Set up Visual Administrator / SLD Data Supplier / HTTP and CIM configured and seem to test fine
Created SLD and it tests OK
Created Technical Landscape
I have noticed that in SP12, in the SLD config I actually have a NEW category called "System Landscape" above my "Technical Landscape" link. I have not seen this option in previous versions SP9 or SP11. Is it mandatory to configure this?
Also, I created a model for Adaptive RFC and found the function I needed successfully.
Anyway, here is the error when trying to deploy...
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Error while obtaining JCO connection.
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)
Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create J2EE cluster node in SLD for 'J2E.SystemHome.bc347792': com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND: No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",Name="J2E.SystemHome.bc347792"
Any help will be appreciated!

I figured it out for those that may have a similar problem.
Although I had created and tested my JCo's properly and they were working fine, somehow, and I still don't know why, they went RED in the JCo Maintainence screen.
I had to "create" again and it works fine now.

Zip files in j2ee/cluster/server0/log/archive, Can somebody explain these?

Our file system is filling up on our PI system, I see allot of .ZIP files in this directory, can I just delete them?
j2ee/cluster/server0/log/archive

Hi David,
as you can read [here|http://help.sap.com/saphelp_sem60ep1/helpdata/EN/f6/7d814282cfc153e10000000a1550b0/frameset.htm] the ZIP files contain old log files so you can delete them to free up space.
Hope this helps,
Robert

J2EE Cluster is not created during system copy.

Hi all,
Iu2019ve been trying to perform a system copy on our PI 7.0 sp14 test system & create a second system on the same server.
I used the standard Sapinst tools for this because it is a PI ABAP+JAVA system.
The copy process went smooth but after it finished I realized that the ABAP side has been installed correctly but when I tried running "SXMB_IFR" I saw that the system points me to the source system J2EE process.
Looking into the file system of the target system, I saw that under the path \usr\sap\<SID>\<Instance>\j2ee\cluster only the bootstrap folder exists. Of course that in the SAP MMC, you cannot see any J2EE process under the new system process list.
I tried using a newer sapinst but that didnu2019t help.
Anyone ever encounter anything like that?
Thanks for your help.
Regards,
Yoav Zilberman

He again,
Now i finally managed to make all the J2EE process work but i keep having issues with the "server0" process in both systems on the server.
the first system i starts works fine but the second one will get the error: [Thr 8944] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\XIQ\DVEBMGS00\exe\jvmx.jar ; (SID changes according to which system started first).
Thanks,
Yoav

SPML usage in J2EE cluster with multiple servers

We are using SPML direct provisioning to create users in UME.
The J2EE cluster we are using has 2 server instances for scalibaility
reasons. Both of the servers are on the same host..
Is SPML supported on such a clsuter or only 1 of the servers can be
used at a time?
In case only 1 seerver can be used, can you please tell us how thsi
canbe achieved as we will need more than 1 server to handle the worklaod.
Many thanks,
Vikrant Sud

HI,
I am not clear with your Q.,
Any way please try to see below links , may be helpfull..
http://help.sap.com/saphelp_nw04/helpdata/en/7e/5df96381ec72468a00815dd80f8b63/content.htm
/people/saravanakumar.kuppusamy2/blog/2005/01/19/rdbms-system-integration-using-xi-30-jdbc-senderreceiver-adapter
Multiple Senders on A2A
Error in sender JDBC Adapater
JDBC sender adapter
Multiple interfaces with same receiver
regards
Chilla..

Webdispacther + J2EE Cluster wrong balancing

Hello,
We have a problem.
We have a webdispatcher that sends information to a J2EE cluster with 3 nodes with 2 serves each.
The problem is that it does not do the balancing correctly. It only balances to the 1 and 3 node. How can I check or configure so the balancing goes to the 3 nodes instead of the 2 nodes?.
The configuration of the webdispatcher is:
SAPSYSTEMNAME = WPE
SAPGLOBALHOST = madrsiwd03
SAPSYSTEM = 10
INSTANCE_NAME = W10
DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTI386
DIR_EXECUTABLE = $(DIR_CT_RUN)
rdisp/mshost = madrsiep03.indra.es
ms/http_port = 8101
icm/max_conn = 16384
icm/max_sockets = 16384
icm/req_queue_len = 6000
icm/min_threads = 100
icm/max_threads = 250
mpi/total_size_MB = 500
mpi/max_pipes = 21000
icm/server_port_0 = PROT=HTTP,PORT=81$$,TIMEOUT=900,PROCTIMEOUT=600
icm/server_port_1 = PROT=ROUTER,PORT=82$$,TIMEOUT=900,PROCTIMEOUT=600,VCLIENT=1
The configuration of the J2EE cluster is:
SAPSYSTEMNAME = XXX
SAPSYSTEM = 01
INSTANCE_NAME = SCS01
DIR_CT_RUN = $(DIR_EXE_ROOT)/run
DIR_EXECUTABLE = $(DIR_INSTANCE)/exe
SAPLOCALHOST = madarrsiclpee
OS_UNICODE = uc
rdisp/msserv = 0
rdisp/msserv_internal = 3901
ms/standalone = 1
ms/server_port_0 = PROT=HTTP,PORT=81$$
ms/server_port_1 = PROT=HTTPS,PORT=82$$
enque/serverinst = 01
enque/table_size = 4096
rdisp/enqname = $(rdisp/myname)
enque/snapshot_pck_ids = 100
Best Regards.
Pablo Mortera.

If I understand your question, you have 2 J2EE Instances with 1 and 2 Server nodes on each and Web DIspatcher is pushing load only to the Instance with 1 Server node, right?
1. Go to webdisp admin page @ http://host/wdisp/admin --> click monitor server groups , here you can see the J2EE instances and thier capacity . You can also see how many requests are sent to each instance.
2. You can RIGHT CLICK on the the J2EE Instance and Change the CAPACITY of the desired Instance to send more load.
Thanks
SM

Problem with deploying : SDM could not start the J2EE cluster on the host .

Hello, All
I have following problem with deploying the aplication I get this messenger:
16/09/2008 07:59:44 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : 192.168.0.14
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/PENITU1/LOCALS~1/Temp/temp47114ZChangeRequestDatabase.ear
Result
=> deployment aborted : file:/C:/DOCUME1/PENITU1/LOCALS~1/Temp/temp47114ZChangeRequestDatabase.ear
Aborted: development component 'ZChangeRequestDatabase'/'local'/'LOKAL'/'0.2008.05.03.04.24.17'/'0':
SDM could not start the J2EE cluster on the host Jupiter! The online deployment is terminated. There is no cluster control instance running on host Jupiter which is described in SecureStorage . The instances, returned by MessageServer [MS host: Jupiter; MS port: 3901], are :|Name:JM_T1221612526745_0_penitus15 |Host:PENITUS15 |State:5|HostAddress:192.168.0.205||Name:JM_T1221612357814_0_Jupiter |Host:pfs |State:5|HostAddress:192.168.0.14||Name:JC_Jupiter_JTP_00 |Host:pfs |State:5|HostAddress:192.168.0.14|Please check if there is an appropriate running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Deployment exception : The deployment of at least one item aborted
I dont'n know How do I solver this error?
- I reviewed the virtual memory and I increase the virtual memory
- I restarted the server and the system
- I reviwed the parameter in the config tool --> cluster --> security storage it is OK
Any suggestion for solver this problem
Thanks
Regards
DS

I found this messenger in Additional log information., Please si
17/09/2008 03:04:51 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[004]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[C:\usr\sap\JTP\JC00\SDM\program\log\sdmcl20080917200328.log]/>
<!PATTERN[sdmcl20080917200328.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
Sep 17, 2008 1:04:40 PM Info: -
Starting deployment -
Sep 17, 2008 1:04:40 PM Info: Error handling strategy: OnErrorStop
Sep 17, 2008 1:04:40 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Sep 17, 2008 1:04:40 PM Info: Update strategy: UpdateAllVersions
Sep 17, 2008 1:04:40 PM Info: Starting deployment prerequisites:
Sep 17, 2008 1:04:40 PM Info: Loading selected archives...
Sep 17, 2008 1:04:40 PM Info: Loading archive 'C:\usr\sap\JTP\JC00\SDM\program\temp\temp62604ZIssueDatabase.ear'
Sep 17, 2008 1:04:41 PM Info: Selected archives successfully loaded.
Sep 17, 2008 1:04:41 PM Info: Actions per selected component:
Sep 17, 2008 1:04:41 PM Info: Initial deployment: Selected development component 'ZIssueDatabase'/'local'/'LOKAL'/'0.2008.04.17.10.53.03'/'0' will be deployed.
Sep 17, 2008 1:04:41 PM Info: Ending deployment prerequisites. All items are correct.
Sep 17, 2008 1:04:43 PM Error: Unable to compare host[Jupiter] and host[PENITUS15] Throwable: java.net.UnknownHostException Throwable message: PENITUS15: PENITUS15
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs: pfs
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Info: Saved current Engine state.
Sep 17, 2008 1:04:45 PM Info: Starting: Initial deployment: Selected development component 'ZIssueDatabase'/'local'/'LOKAL'/'0.2008.04.17.10.53.03'/'0' will be deployed.
Sep 17, 2008 1:04:45 PM Info: SDA to be deployed: C:\usr\sap\JTP\JC00\SDM\root\origin\local\ZIssueDatabase\LOKAL\0\0.2008.04.17.10.53.03\temp62604ZIssueDatabase.ear
Sep 17, 2008 1:04:45 PM Info: Software type of SDA: J2EE
Sep 17, 2008 1:04:45 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[PENITUS15] Throwable: java.net.UnknownHostException Throwable message: PENITUS15
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Info: Starting cluster instance processes.
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[PENITUS15] Throwable: java.net.UnknownHostException Throwable message: PENITUS15
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Error: An error occured while starting a cluster instance.
Sep 17, 2008 1:04:45 PM Error: There is no clutser control instance running on host Jupiter which is described in SecureStorage .
The instances, returned by MessageServer [MS host: Jupiter; MS port: 3901], are :
Name:JM_T1221672404781_2_penitus15
Host:PENITUS15
State:5
HostAddress:192.168.0.215
Name:JM_T1221679486171_0_Jupiter
Host:pfs
State:5
HostAddress:192.168.0.14
Name:JC_Jupiter_JTP_00
Host:pfs
State:5
HostAddress:192.168.0.14
Please check if there is an appropriate running cluster instances.
Sep 17, 2008 1:04:45 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 17, 2008 1:04:45 PM Error: Aborted: development component 'ZIssueDatabase'/'local'/'LOKAL'/'0.2008.04.17.10.53.03'/'0':
SDM could not start the J2EE cluster on the host Jupiter! The online deployment is terminated.
There is no clutser control instance running on host Jupiter which is described in SecureStorage .
The instances, returned by MessageServer [MS host: Jupiter; MS port: 3901], are :
Name:JM_T1221672404781_2_penitus15
Host:PENITUS15
State:5
HostAddress:192.168.0.215
Name:JM_T1221679486171_0_Jupiter
Host:pfs
State:5
HostAddress:192.168.0.14
Name:JC_Jupiter_JTP_00
Host:pfs
State:5
HostAddress:192.168.0.14
Please check if there is an appropriate running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Sep 17, 2008 1:04:45 PM Info: Starting to save the repository
Sep 17, 2008 1:04:46 PM Info: Finished saving the repository
Sep 17, 2008 1:04:47 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Sep 17, 2008 1:04:47 PM Error: -
At least one of the Deployments failed -
Any help will be well received about this problema
Thk
Regards
DS

Deployment SDM could not start the J2EE Cluster on the host nw4host

Hello,
I installed the WAS testdrive on Linux SUSE 9.3 and the SNDS on WinXP.
I am trying to deploy the welcome application from the SNDS and get the following error message:
SDM could not start the J2ee Cluster on the host nw4host! The online deployment is terminated. JStartup Framework ist not able to deliver an information about the cluster control instances! Please check the status of the J2EE Engine.
I can start the J2EE Start page on port 50000, the system info shows that dispatcher, server0 and SDM are running. I can start the visual admin with go, the SDM with RemoteGui and the DeployTool.
The comand startsap check nw4host shows, everythings running:
nw4host:nw4adm 54> startsap check nw4host
Checking ADA db Database
ABAP Database is running
Checking ADA db Database
J2EE Database is running
See logfile JdbcCon.log
Checking SAP NW4 Instance SCS01
Instance SCS01 is running
Checking SAP NW4 Instance DVEBMGS00
Instance DVEBMGS00 is running
Logging in to SAP with the Java Gui, the ICM says:
ABAP Server operational        = TRUE
J2EE Server configured         = FALSE
J2EE HTTP port                 = 50000
J2EE HTTPS port                = 50001
J2EE Server operational        = TRUE
Default root access handler    = ABAP
URL Prefix Table loaded        = TRUE
Any idea where the problem could be ?
Thanks, Manfred.

changed the ip address for nw4host in etc/hosts to the real ip address of the server where application runs

NW4: SDM could not start the J2EE cluster on the host nw4host

Hello,
in NW4 i get this error when i try to deploy the welcome webdynpro:
SDM could not start the J2EE cluster on the host nw4host! The online deployment is terminated. JStartup Framework is not able to deliver an information about the cluster control instances! Please check the status of the J2EE Engine.
I am using NW4 (built 28.9.04) on Suse 9.0 and the corresponding IDE (2.04) on Windows 2000.
In the J2EE view of the IDE everything (SDM, Dispatcher and Server) is green. I can start the examples on port 50000. According to systeminfo everything is running.
I searched in OSS and found Note 738402. But there is no EOF in the SDM-logfile. And when i started the J2EE-Configtool the value for "admin/host/SID" is not localhost.
Any hints?
Regards,
Nico.

Hello,
> Developer Studio -> Preferences -> SAP J2EE Engine ?
of course. Every icon (SDM, Dispatcher and server) is green in the J22E-View of the IDE. I still get this error message.
Regards,
Nico.

SDM could not start the J2EE cluster on the host Error on Deployments

Hi,
We are sudenly getting this Error when trying to make a Deployment in the NWDE:
Settings
SDM host : 10.26.26.198
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/ALMA1.CAR/LOCALS~1/Temp/temp49346WDWFApp.ear
Result
=> deployment aborted : file:/C:/DOCUME1/ALMA1.CAR/LOCALS~1/Temp/temp49346WDWFApp.ear
Aborted: development component 'WDWFApp'/'local'/'LOKAL'/'0.2007.02.16.15.11.28'/'0':SDM could not start the J2EE cluster on the host vmxtbcsapep01! The online deployment is terminated. There is no clutser control instance running on host vmxtbcsapep01 which is described in SecureStorage . The instances, returned by MessageServer [MS host: vmxtbcsapep01; MS port: 3901], are :|Name:JM_T1171660289517_0_ALMACARVAJAL |Host:miriamdragustinovis |State:5|HostAddress:10.21.69.164||Name:JM_T1171656308064_0_vmxtbcsapep01 |Host:cvespinosa |State:5|HostAddress:10.26.26.198||Name:JC_vmxtbcsapep01_CPQ_00 |Host:cvespinosa |State:5|HostAddress:10.26.26.198|Please check if there is an appropriate running cluster instances. (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Deployment exception : The deployment of at least one item aborted
And in the sdm log file we got this kind of errors:
Feb 16, 2007 2:13:46 PM Error: Unable to compare host[vmxtbcsapep01] and host[miriamdragustinovis] Throwable: java.net.UnknownHostException Throwable message: miriamdragustinovis
Feb 16, 2007 2:13:46 PM Error: Unable to compare host[vmxtbcsapep01] and host[cvespinosa] Throwable: java.net.UnknownHostException Throwable message: cvespinosa
Feb 16, 2007 2:13:46 PM Error: Unable to compare host[vmxtbcsapep01] and host[cvespinosa] Throwable: java.net.UnknownHostException Throwable message: cvespinosa
Feb 16, 2007 2:13:46 PM Error: An error occured while starting a cluster instance.
Feb 16, 2007 2:13:46 PM Error: There is no clutser control instance running on host vmxtbcsapep01 which is described in SecureStorage .
The instances, returned by MessageServer [MS host: vmxtbcsapep01; MS port: 3901], are :
Name:JM_T1171656916610_0_ALMACARVAJAL
Host:miriamdragustinovis
State:5
HostAddress:10.21.69.164
Name:JM_T1171656308064_0_vmxtbcsapep01
Host:cvespinosa
State:5
HostAddress:10.26.26.198
Name:JC_vmxtbcsapep01_CPQ_00
Host:cvespinosa
State:5
HostAddress:10.26.26.198
Any Idea what can be wrong? we have even restarted de AIX Server and starting all the services and it is still not working.
Thanx in Advanced!
Gerardo J

Hi Gerardo,
I encountered exactly the same error, but had a different solution as I was expecting from the error-message.
In my case I was forced by the Visual Administrator to change the administration password, since the time was up on it. But as the password for the Visual Administrator is saved within the database, the password for the SDM is stored within the secure store (file-system) and changing the password just in VA will not automatically change it also in the secure store. But since both passwords for the internal usage need to be equalized, I encountered problems afterwards when trying to deploy something and I got the same error message. However the sense of restriction is meant here, the solution on it was rather simple as follows (Just note that you need to enter a dummy-password first, before setting the correct one similar to your visual administrator):
1. create a telnet session to your J2EE using a command line shell
2. enter "jump 0" to get on the correct node within your J2EE
3. enter "add user" to gain access to user-specific commands
4. enter "password <Administrator> <temporarily new password>"
5. exit
6. create another telnet session to your J2EE using a command line shell
7. after succeeded the login, you will now be forced to enter a new password - so enter "password <Administrator> <origin password of the Visual Administrator>"
8. exit
9. now start the config-tool of the engine
10. apply to the DB-default-question with "yes"
11. select the Secure Store on the left
12. select the entry "admin/password/..." that you can see it in the bottom lines.
13. click "Remove" to delete it from the list
14. set the password similar to the Visual Administrator password within the "Value" line (take care as you can not see the digits).
15. click "Add" to add it back to the list
16. click the disc symbol in the top of the UI to save the new password (if you don't get a dialog afterwards that the data has been stored, something may hasn't worked fine when removing/adding the password-entry, in this case repeat the action on it).
17. After exiting the config-tool, you need to restart the entire J2EE.
18. Your hopefully finished by success ;o))
Best regards
Jochen

EP 6.0 SP2 P4 J2EE Cluster - 503! - Initialization of Dispatcher failed

Similar Messages

Maybe you are looking for