Solved: Dispatcher running, but no server connected

Hi,

we are using mysap on windows 2k3 with oracle was java and abap . connection through browser was working fine but when server is restarted browser is giving below error

"Dispatcher running , but no server is connected "

Thanks in advance

regards

Lallan Tripathi

SAP Managed Tags:
SAP NetWeaver Application Server

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Hello Lallan,

Each instance has a dispatcher node and one or more server nodes. The Java dispatcher receives the client request and forwards it to the server process. The server processes of the J2EE Engine actually execute the J2EE applications and process and replies to requests. Therefore the dispatcher process is much faster than the server process and when you restart the instance it starts first. In the time when the dispatcher already started, but the server process is still starting, the dispatcher could receive requests, but doesnu2019t have where to send them. Therefore you get the below error message. Please wait until the server process is in running mode and the error message should disappear.

Of course the same error could occur if the server process is broken. Check the std_server0.out and the dev_server0 log files from the work directory and the defaultTrace file from the server0/log directory if that is the case.

Regards,

Ventsi Tsachev

Technology Development Support (J2EE Engine)

SAP Labs, Palo Alto, Ca (USA)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

Thanks for your reply . I have restarted the server also but still same error message is comming " Dispatcher running, but no server connected"

I am attaching the both file output .

pl. help how to look in this file and how to trace the error .

1. OUTPUT OF std_serve0.out

stdout/stderr redirect

node name : server0

pid : 4004

system name : PR4

system nr. : 00

started at : Mon Dec 25 19:59:52 2006

CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources

CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain

CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub

CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS

CompilerOracle: exclude iaik/security/md/SHA a

CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices

CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile

CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup

SAP J2EE Engine Version 6.40 PatchLevel 87289.311 is starting...

Loading: LogManager ... 3985 ms.

Loading: PoolManager ... 0 ms.

Loading: ApplicationThreadManager ... 375 ms.

Loading: ThreadManager ... 203 ms.

Loading: IpVerificationManager ... 16 ms.

Loading: ClassLoaderManager ... 31 ms.

Loading: ClusterManager ... 1578 ms.

Loading: LockingManager ... 109 ms.

Loading: ConfigurationManager ... 2422 ms.

Loading: LicensingManager ... 141 ms.

Loading: ServiceManager ...

0.000: [GC 0.000: [DefNew: 43519K->3428K(65280K), 0.0463950 secs] 43519K->3428K(502528K), 0.0464542 secs]

Loading services.:

Service memory started. (1562 ms).

Service runtimeinfo started. (1047 ms).

Service cross started. (3156 ms).

Service file started. (1532 ms).

Service timeout started. (1813 ms).

Service jmx_notification started. (297 ms).

Service trex.service started. (63 ms).

Service userstore started. (16 ms).

Service tc_secvsi~service started. (8391 ms).

Service tc_secwssec~service started. (14546 ms).

66.701: [GC 66.713: [DefNew: 46948K->5530K(65280K), 0.7279713 secs] 46948K->5530K(502528K), 0.7280322 secs]

Service p4 started. (27828 ms).

Service classpath_resolver started. (125 ms).

Service log_configurator started. (56391 ms).

Service locking started. (16 ms).

Service naming started. (2172 ms).

Service ts started. (781 ms).

Service appclient started. (109 ms).

Service jmsconnector started. (46 ms).

Service failover started. (15 ms).

Service licensing started. (79 ms).

Service javamail started. (5094 ms).

Service http started. (2922 ms).

Service connector started. (235 ms).

89.559: [GC 89.559: [DefNew: 49050K->6774K(65280K), 0.1170674 secs] 49050K->6774K(502528K), 0.1171244 secs]

Service deploy started. (16907 ms).

Service webservices started. (16625 ms).

Service configuration started. (15 ms).

Service apptracing started. (453 ms).

105.391: [GC 105.391: [DefNew: 50294K->8767K(65280K), 0.0681039 secs] 50294K->8767K(502528K), 0.0681606 secs]

Service dbpool started. (14093 ms).

Dec 25, 2006 8:03:54 PM ...asource.imp.R3Persistence.doInitRfc() [SAPEngine_System_Thread[impl:5]_32] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "User SAPJSF has no RFC authorization for function group SYST .". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{

jco.client.lang=

jco.client.user=SAPJSF

jco.client.mshost=

jco.client.snc_myname=

jco.client.receiverid_guest=master

jco.client.group=

jco.client.snc_lib=

jco.client.sysnr=00

jco.client.client=000

jco.client.poolmaxsize=10

jco.client.trace=

jco.client.abap_debug=

jco.client.gwserv=

jco.client.poolmaxwait=

jco.client.ashost=neerajit

jco.client.snc_mode=0

jco.client.r3name=

jco.client.snc_qop=

jco.client.gwhost=

jco.client.msserv=

jco.client.receiverid=master

jco.client.passwd=********

jco.client.snc_partnername=

}

Dec 25, 2006 8:03:54 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_32] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.

service com.sap.security.core.ume.service ================= ERROR =================

Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

com.sap.engine.frame.ServiceException: User SAPJSF has no RFC authorization for function group SYST .

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:531)

at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)

at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:201)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)

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)

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: User SAPJSF has no RFC authorization for function group SYST .

at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:2099)

at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:2315)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:280)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:224)

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:528)

... 6 more