New Installed SAP server Java Instance not working

[Former Member]

Dear all ,

I have checked the status of java instance through http://hostname:port , its shows 503 Service Unavailable

7.00

Dispatcher running but no server connected!

Details:

No details available

Kindly advise

[Former Member]

answered

[Former Member]

What is your UME data source ?

Also check using JCMON what is the status of SDM, Server ?

Regards,

[former_member524429]

Hi,

Its Standalone JAVA system or ABAP+JAVA stacks ?

If its ABAP+JAVA stack then also check the account status of SAPJSF, J2EE_GUEST users in the client (000 or 001 or any other) which is mentioned in ...UME.secureStore.. proeprties of configtool.

Check server node processes are started/running properly ? It may be stopped.

Start jcmon under <sid>adm user and look at the status.

jcmon pf=/sapmt/<SID>/profile/<SID>_JC<nn>_hostname.

Check there what status shows for server node.

Have you checked the dev_server0, dev_server1... std_server0.out..., jvm_server0.out.., dev_jcontrol,,,jvm_dispatcher.out log files ? Analyze the error/earnings written in that log files and post them.

Regards,

Bhavik G. Shroff

Edited by: Bhavik G. Shroff on Nov 26, 2010 3:37 PM

[Former Member]

Dear all,

Pls check the std_server0.out log:

stdout/stderr redirect

-

---

node name : server0

pid : 3956

system name : ISO

system nr. : 00

started at : Sat Nov 27 12:31:46 2010

Reserved 1610612736 (0x60000000) bytes before loading DLLs.

[Thr 460] MtxInit: -2 0 0

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 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

CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue

CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode

CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode

CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects

CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement

CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence

CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations

CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto

SAP J2EE Engine Version 7.00 PatchLevel is starting...

Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect

Loading: LogManager ... 1938 ms.

Loading: PoolManager ... 0 ms.

Loading: ApplicationThreadManager ... 94 ms.

Loading: ThreadManager ... 47 ms.

Loading: IpVerificationManager ... 15 ms.

Loading: ClassLoaderManager ... 78 ms.

Loading: ClusterManager ... 578 ms.

Loading: LockingManager ... 344 ms.

Loading: ConfigurationManager ... 0.000: [ParNew 81920K->2295K(1007616K), 0.0103595 secs]

4360 ms.

Loading: LicensingManager ... 15 ms.

Loading: CacheManager ... 110 ms.

Loading: ServiceManager ...

Loading services.:

Service timeout started. (16 ms).

Service runtimeinfo started. (16 ms).

Service memory started. (16 ms).

Service cross started. (547 ms).

Service file started. (704 ms).

Service trex.service started. (15 ms).

16.308: [ParNew 84215K->6501K(1007616K), 0.0213662 secs]

Service p4 started. (2000 ms).

Service classpath_resolver started. (63 ms).

Service userstore started. (0 ms).

Service jmx_notification started. (31 ms).

Service log_configurator started. (13969 ms).

Service locking started. (0 ms).

Service naming started. (328 ms).

Service ts started. (93 ms).

Service failover started. (15 ms).

Service licensing started. (0 ms).

Service appclient started. (47 ms).

Service iiop started. (1500 ms).

Service javamail started. (1984 ms).

Service jmsconnector started. (62 ms).

Service connector started. (188 ms).

Service http started. (609 ms).

29.199: [ParNew 88421K->12341K(1007616K), 0.0302151 secs]

Service webservices started. (1641 ms).

Service deploy started. (13125 ms).

Service configuration started. (16 ms).

Service MigrationService started. (0 ms).

Service bi_mmrdeployer started. (0 ms).

Service dbpool started. (1125 ms).

[Former Member]

continue...

Nov 27, 2010 12:33:37... com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_70] 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: "Connect to SAP gateway failed

Connect_PM TYPE=A ASHOST=localhost SYSNR=00 GWHOST=localhost GWSERV=sapgw00 PCS=1

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR timeout occured

TIME Sat Nov 27 12:33:37 2010

RELEASE 700

COMPONENT NI (network interface)

VERSION 38

RC -5

MODULE gwxx.c

LINE 480

DETAIL timeout 60000 msecs

SYSTEM CALL NiRead

COUNTER 1

". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{

passwd=********

receiverid=master

sysnr=$$

client=001

poolmaxsize=10

user=SAPJSF

receiverid_guest=master

ashost=localhost

poolmaxwait=10000

}

".

Nov 27, 2010 12:33:37... com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_70] 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: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.

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

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

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

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

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed

Connect_PM TYPE=A ASHOST=localhost SYSNR=00 GWHOST=localhost GWSERV=sapgw00 PCS=1

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR timeout occured

TIME Sat Nov 27 12:33:37 2010

RELEASE 700

COMPONENT NI (network interface)

VERSION 38

RC -5

MODULE gwxx.c

LINE 480

DETAIL timeout 60000 msecs

SYSTEM CALL NiRead

COUNTER 1

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

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

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

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)

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

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

at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)

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

... 6 more

com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.

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

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

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

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

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed

Connect_PM TYPE=A ASHOST=localhost SYSNR=00 GWHOST=localhost GWSERV=sapgw00 PCS=1

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR timeout occured

TIME Sat Nov 27 12:33:37 2010

RELEASE 700

COMPONENT NI (network interface)

VERSION 38

RC -5

MODULE gwxx.c

LINE 480

DETAIL timeout 60000 msecs

SYSTEM CALL NiRead

COUNTER 1

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

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

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

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)

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

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

at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)

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

... 6 more

[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Nov 27, 2010 12:33:37... com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_70] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

-

---

[Former Member]

Nov 27, 2010 12:37:15... com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_54] 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: "Connect to SAP gateway failed

Connect_PM TYPE=A ASHOST=localhost SYSNR=00 GWHOST=localhost GWSERV=sapgw00 PCS=1

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR timeout occured

TIME Sat Nov 27 12:37:15 2010

RELEASE 700

COMPONENT NI (network interface)

VERSION 38

RC -5

MODULE gwxx.c

LINE 480

DETAIL timeout 60000 msecs

SYSTEM CALL NiRead

COUNTER 1

". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{

passwd=********

receiverid=master

sysnr=$$

client=001

poolmaxsize=10

user=SAPJSF

receiverid_guest=master

ashost=localhost

poolmaxwait=10000

}

".

Nov 27, 2010 12:37:15... com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_54] 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: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.

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

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

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

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

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed

Connect_PM TYPE=A ASHOST=localhost SYSNR=00 GWHOST=localhost GWSERV=sapgw00 PCS=1

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR timeout occured

TIME Sat Nov 27 12:37:15 2010

RELEASE 700

COMPONENT NI (network interface)

VERSION 38

RC -5

MODULE gwxx.c

LINE 480

DETAIL timeout 60000 msecs

SYSTEM CALL NiRead

COUNTER 1

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

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

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

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)

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

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

at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)

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

... 6 more

com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.

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

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

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

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

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed

Connect_PM TYPE=A ASHOST=localhost SYSNR=00 GWHOST=localhost GWSERV=sapgw00 PCS=1

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR timeout occured

TIME Sat Nov 27 12:37:15 2010

RELEASE 700

COMPONENT NI (network interface)

VERSION 38

RC -5

MODULE gwxx.c

LINE 480

DETAIL timeout 60000 msecs

SYSTEM CALL NiRead

COUNTER 1

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

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

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

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)

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

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

at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)

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

... 6 more

[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Nov 27, 2010 12:37:15... com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_54] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Kindly advise

[Former Member]

make sure your sapjsf is not locked at the backend as it is dual stack.

[Former Member]

Hi,

Have you checked Note 965451 - Error, while preloading security provider classes ?

Cheers...,

Raghu

[Former Member]

Sateesh,

check the work directory and default trace to see if this is pointing to any logs.

[Former Member]

Hello

The step by step for this kind of error analysis will be

1. try to clean stop and then start again .most of the time it works if windows system

2. check different logs generallay provided by SAp system in /usr/sap/SID/instance/work directory

3. since this is is JAVA system you can check ,dev_disp,dev_bootstrap,dev_sdm,dev_server,dev_jcontrol,dev_server ,javm_bootstrap_ID.log

4. to check if database connection available use R3trans -d

5. based on this you can best judge and solve the issue with help of any note available in SMP

6. If you would like paste the excact error logs from above file here

Hope helps

Success!!!

Edited by: Ganesh Gambhir on Nov 26, 2010 1:26 PM