cancel
Showing results for 
Search instead for 
Did you mean: 

sap instance not coming up after system refresh

Former Member
0 Kudos

Java instance not coming up after system refresh. All user are fine.

--------------------------------------------------------------------------------

stdout/stderr redirect

--------------------------------------------------------------------------------

node name   : server0

pid         : 2555

system name : BQN

system nr.  : 51

started at  : Sun Mar  3 14:57:20 2013

[Thr 01] MtxInit: 10001 0 2

(CompilerOracle read from file /sapmnt/BQN/exe/jvm/hpia64/sapjvm_4.1.023/sapjvm_4/jre/.hotspot_compiler)

SAP J2EE Engine Version 7.01   PatchLevel 75592. is starting...

Loading: LogManager ... 2527 ms.

Loading: PoolManager ... 19 ms.

Loading: ApplicationThreadManager ... 6.396: [GC 6.396: [ParNew: 409600K->3189K(512000K), 0.0409202 secs] 409600K->3189K(19947

52K), 0.0414696 secs] [Times: user=0.17 sys=0.01, real=0.04 secs]

722 ms.

Loading: ThreadManager ... 135 ms.

Loading: IpVerificationManager ... 16 ms.

Loading: ClassLoaderManager ... 137 ms.

Loading: ClusterManager ... 504 ms.

Loading: LockingManager ... 165 ms.

Loading: ConfigurationManager ... 4727 ms.

Loading: LicensingManager ... 171 ms.

Loading: CacheManager ... 224 ms.

Loading: ServiceManager ...

Loading services.:

  Service DQE started. (1 ms).

  Service memory started. (78 ms).

  Service cross started. (122 ms).

  Service file started. (218 ms).

  Service caf~eu~odi~mnuacc started. (4 ms).

  Service runtimeinfo started. (95 ms).

  Service timeout started. (154 ms).

  Service trex.service started. (238 ms).

  Service caf~eu~cc~api started. (499 ms).

  Service p4 started. (546 ms).

  Service userstore started. (74 ms).

  Service classpath_resolver started. (136 ms).

  Service jmx_notification started. (120 ms).

23.397: [GC 23.397: [ParNew: 412789K->19905K(512000K), 0.0897167 secs] 412789K->19905K(1994752K), 0.0902025 secs] [Times: user

=0.44 sys=0.01, real=0.09 secs]

29.823: [GC 29.823: [ParNew: 429505K->26042K(512000K), 0.0720009 secs] 429505K->26042K(1994752K), 0.0723633 secs] [Times: user

=0.45 sys=0.00, real=0.08 secs]

  Service log_configurator started. (11615 ms).

  Service locking started. (11 ms).

  Service http started. (408 ms).

  Service naming started. (1255 ms).

  Service failover started. (102 ms).

  Service licensing started. (92 ms).

  Service appclient started. (114 ms).

  Service javamail started. (217 ms).

  Service jmsconnector started. (233 ms).

  Service ts started. (280 ms).

  Service connector started. (294 ms).

  Service iiop started. (286 ms).

  Service deploy started. (15980 ms).

  Service com.sap.portal.runtime.config.kmreadonly started. (7 ms).

  Service MigrationService started. (64 ms).

  Service configuration started. (118 ms).

  Service bi~mmr~deployer started. (10 ms).

  Service dbpool started. (3371 ms).

  Service UT started. (21 ms).

  Service caf~eu~gp~mail~cf started. (130 ms).

  Service com.sap.security.core.ume.service started. (6113 ms).

Mar 3, 2013 2:58:08 PM   ...xt.<init>(UserContextSpi, Properties) [SAPEngine_System_Thread[impl:5]_47] Fatal: Can not instanti

ate UserContext with given properties.

  service security ================= ERROR =================

Core service security failed. J2EE Engine cannot be started.

com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:

        at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:194)

        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:83)

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

Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.

        at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:80)

        at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:405)

        at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:84)

        at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:58)

        at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:147)

        ... 5 more

com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:

        at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:194)

        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:83)

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

Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.

        at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:80)

        at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:405)

        at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:84)

        at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:58)

        at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:147)

        ... 5 more

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

Mar 3, 2013 2:58:08 PM              com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_47] Fatal: Critical shutdow

n was invoked. Reason is: Core service security failed. J2EE Engine cannot be started.

Heap

par new generation   reserved 614400K, committed 614400K, used 304855K [0x0000000000010000, 0x0000000025810000, 0x00000000258

10000)

  eden space 409600K,  68% used [0x0000000000010000, 0x0000000011057240, 0x0000000019010000)

  from space 102400K,  25% used [0x000000001f410000, 0x0000000020d7e9f0, 0x0000000025810000)

  to   space 102400K,   0% used [0x0000000019010000, 0x0000000019010000, 0x000000001f410000)

concurrent mark-sweep generation reserved 1482752K, committed 1482752K, used 0K [0x0000000025810000, 0x0000000080010000, 0x00

00000080010000)

concurrent-mark-sweep perm gen reserved 524288K, committed 524288K, used 40910K [0x0000000080010000, 0x00000000a0010000, 0x00

000000a0010000)

Accepted Solutions (0)

Answers (5)

Answers (5)

JPReyes
Active Contributor
0 Kudos

Java instance not coming up after system refresh

System refresh as DB clone?... you cannot refresh the java instance by doing a DB copy... You need to fo an export/import. Can you please tell us what method did you use for the refresh?..

Regards, Juan

former_member185239
Active Contributor
0 Kudos

Hi Basis,

Logon to Configtool

Goto service Service com.sap.security.core.ume.service under instance

Check the the below three things

1. hostname

2. user and its password

3. Persistent datasource

Just scroll down check the above

If possible paste the default trace.

With Regards

Ashutosh Chaturvedi

Asha_Pillai
Active Participant
0 Kudos

Hello.

Please check if SAP KBA 1658911 is useful.

Regards,

Asha

AtulKumarJain
Active Contributor
0 Kudos

Hi ,

Please use sap note :  1806517 to solve your issue.

Best Regards,

Atul

Former Member
0 Kudos

Hi ramu,

System is not able to find Instance ID. Could you please check if instance ID exists in config tool ?

Are there any changes in the system during or after export ?

Please also paste error logs from default trace after restarting the system again

Can you please check the database connection properties in the secure store ?

did you export also the java central instance, besides the database?

you can also try via config tool, on the source system to export the instance, and the import it in the config tool of the destination system.

please open the config tool -> secstore data  and update the password for SAPSR3DB as well as SAPJSF or J2EE_ADMIN or Administrator users.

Then try to restart and check whether it resolves the issue

Regards,

Prabaharan B

TomCenens
Active Contributor
0 Kudos

Hi Ramu

You should check your UME settings / user store settings. The logging above points out that the system is unable to properly get the usercontext:

"com.sap.security.core.ume.service"

Check your configuration of your J2EE instance. To which user store are you pointing (is it the correct one), which authentication are you using etc.

There are plenty of existing threads to further help you to check your configuration in the configtool or nwa:

https://scn.sap.com/thread/1707071

Best regards

Tom