j2ee server is not getting up

[Former Member]

Dear All,

Solution manager j2ee server is getting up.It showing error j2ee server stoped -11113.I have changed the password of j2ee_admin and sapjsf from ume after that i restarted the server but j2ee server is not getting up.

I m pasting dev_server0 log

[Thr 5840] Wed Jun 09 11:31:11 2010

[Thr 5840] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes

[Thr 5840] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework

[Thr 5840] JLaunchISetClusterId: set cluster id 3448950

[Thr 5840] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]

[Thr 5840] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]

Wed Jun 09 11:31:17 2010

7.007: [ParNew 163840K->12575K(966656K), 0.0406053 secs]

Wed Jun 09 11:31:21 2010

10.555: [ParNew 176415K->14733K(966656K), 0.0385660 secs]

Wed Jun 09 11:31:24 2010

13.614: [ParNew 178573K->16345K(966656K), 0.0291049 secs]

Wed Jun 09 11:31:26 2010

15.909: [ParNew 180185K->18610K(966656K), 0.0285077 secs]

Wed Jun 09 11:31:30 2010

19.597: [ParNew 182450K->23228K(966656K), 0.0471396 secs]

[Thr 5616] Wed Jun 09 11:31:33 2010

[Thr 5616] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver

[Thr 5616] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI

[Thr 3800] Wed Jun 09 11:31:34 2010

[Thr 3800] JLaunchIExitJava: exit hook is called (rc = -11113)

[Thr 3800]

ERROR => The Java VM terminated with a non-zero exit code.

Please see SAP Note 943602 , section 'J2EE Engine exit codes'

for additional information and trouble shooting.

Thr 3800] JLaunchCloseProgram: good bye (exitcode = -11113)

Kindly suggest me how to solve this error.

Regards

Ashok

[former_member204746]

do what your log says to do:

Please see SAP Note 943602 , section 'J2EE Engine exit codes'

for additional information and trouble shooting.

what are your SAP/Os/DB versions.

[Former Member]

Hi my friend

I cannot tell which JVM you're using by your post. If it's IT4J, run CONFIGJVM once:

On the ADM or OFR user menu --> 7. Define or Change SAP --> 4. SAP Java Stack --> 2. Configure VM Options - Apply

Regards,

[brian_walker]

I don't believe this was the correct forum to post this question in as the issue does not appear related to DB2 z/OS.

Brian

[markus_doehr2]

Please check the logfiles

dev_server0

std_server0.out

Markus

[Former Member]

Hi Markus,

Thanks for ut reply,

I m pasting the logs of std_server0

-

---

stdout/stderr redirect

-

---

node name : server0

pid : 4700

system name : FCS

system nr. : 00

started at : Thu Jun 10 13:29:10 2010

Loading: LogManager ... 1031 ms.

Loading: PoolManager ... 15 ms.

Loading: ApplicationThreadManager ... 110 ms.

->26496K(966656K), 0.0437374 secs]

Jun 10, 2010 1:29:36 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_56] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "Name or password is incorrect (repeat logon)". This message is critical if it appears during the startup of the AS Java.

Jun 10, 2010 1:29:36 PM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_56] Fatal:

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: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Name or password is incorrect (repeat logon)

Service log_configurator started. (7469 ms).

Service locking started. (0 ms).

Service naming started. (235 ms).

Service http started. (281 ms).

Service failover started. (47 ms).

Service appclient started. (110 ms).

Service javamail started. (110 ms).

Service ts started. (109 ms).

Service jmsconnector started. (141 ms).

Service licensing started. (15 ms).

Service connector started. (188 ms).

Service iiop started. (109 ms).

Service webservices started. (390 ms).

Service deploy started. (10938 ms).

Service configuration started. (16 ms).

Service bi_mmrdeployer started. (0 ms).

Service MigrationService started. (31 ms).

Service dbpool started. (1063 ms).

Service UT started. (15 ms).

18.214: [ParNew 181998K->26061K(966656K), 0.0468565 secs]

Jun 10, 2010 1:30:45 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_53] Fatal: Initialization of ABAP

com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Password logon no longer possible - too many failed attempts

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

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

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

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Password logon no longer possible - too many failed attempts

security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)

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

... 6 more

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

Jun 10, 2010 1:30:45 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_53] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Regards

Adil

[markus_doehr2]

> Jun 10, 2010 1:29:36 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_56] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "Name o

The user SAPJSF can't logon to ABAP and hence the J2EE engine doesn't start.

Use configtool and change the password to the correct one, then restart the engine.

Markus

[Former Member]

Hi Markus,

Thsnks for ur reply,

When i login cofig tool i folow the path Global server Configuration->services->com.sap.security.core.ume.service

under this

ume.r3.connection.master.user -> sapjsf but there no field to enter the password.

.Actualy i have changed the password from abap system of sapjsf and after that i restarted the server.

Should i give the same password which i given in abap system of SAPJSF.

Kindly suggest me how to solve this.

Regards

Adil

[franz_hiltscher]

Hello Adil,

the fields are sorted in alphabetical order.

I will find ume.r3.conneciton.master.passwd a few entries above from user.

Yes you have to set the password as in the abap.

Kind Regards

Franz

[Former Member]

Dear All,

Thnx for ur support.Changing the sapjsf password in config tool resolve my issue.

Regards

Ashok