java stack not running

[Former Member]

hi

when connecting through configtool "error occurred while working with configuration (scanning)" is flashed,in SAP MMC ,Java process table is empty & disp+work.exe is yellow,sapstart.trc gives following error:

1)ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1388

(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:4588) [nixxi.cpp 4247]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=3468)

• ERROR => DpProcKill: kill failed [dpntdisp.c 371]

&

2)DpSysAdmExtInit: VMC (JAVA VM in WP) is not active.

The OS is windows NT,DB is MSSQL Server 8.0,and we have ECC 6.0

kindly help , i have been stuck with this problem for past 2 days.

thanks

ravi

[Former Member · Accepted solution]

Hi,

Try to re-start Java stack from ABAP

TCode: SMICM -- > Administration --> J2EE Server --> Restart --> Yes.

If this doesn't work I would recommended to re-start your SAP system both (ABAP & JAVA).

Hope this helps.

Cheers,

Kalyan.

[Former Member · Accepted solution]

HI

Pls post the log of server0

[Former Member · Accepted solution]

I have tried to run Java stack via smicm but it didnt work and previously i had restarted ABAP+java but even this didnt solve the problem,

meanwhile i found the following error in Configtool.log:

Error occurred while working with Configuration.

com.sap.engine.frame.core.configuration.NameNotFoundException: A file entry with the name "~ume.superadmin.activated" cannot be found in the configuration "cluster_data/server/ID14213850/services/com.sap.security.core.ume.service".

[Former Member · Accepted solution]

Sorry but ,server0 directory in j2ee cluster contains many log and trace files ,which of those do we need to see?????

[JPReyes · Accepted solution]

I think he's talking about std_server0.out also post errors on std_dispatcher.out.

Regards

Juan

[vikash_pakhrin · Accepted solution]

Hi Ravi,

For startup problems. Always check for logs in /usr/sap/<SID>/DVE*/work directory.

you can check the log files in the sequence below. This will help u isolate the problem in which phase ur j2ee is facing the issue.

dev_jcontrol

jvm_bootstrap*

jvm_dispatcher.out

jvm_server<n>.out

std_dispatcher.out

std_server<n>.out //depending on the no. of server process you have starts from 0,1...etc

What are these logs saying?

Best Regards,

Vikash

[Former Member · Accepted solution]

hi

Interestingly both the files std_server0.out & std_dispatcher.out flashes no error,each of services mentioned in those files have started fine.what do i do now??

thanks

ravi

[Former Member · Accepted solution]

hi

<dev_jcontrol>

4)ERROR => invalid return code of process [bootstrap] (exitcode = 66) [jstartxx.c 1642]

[Thr 5776] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc = 66)

[Thr 5776] JControlCloseProgram: started (exitcode = 66)

[Thr 5776] JControlCloseProgram: good bye... (exitcode = 66)

jvm_bootstrap*

Exception occurred:

com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!

at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:422)

at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)

at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)

-

---

==[ Caused by: ]==----

---

com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:360)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:125)

at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)

at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)

at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)

at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)

at com.sap.engine.bootstrap.Synchronizer.<init>(Synchronizer.java:60)

at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:419)

at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)

at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)

Caused by: java.sql.SQLException: [SAP_NWMss][SQLServer JDBC Driver]Error establishing socket. Connection refused: connect

at com.sap.nwmss.jdbc.base.BaseExceptions.createException(Unknown Source)

at com.sap.nwmss.jdbc.base.BaseExceptions.getException(Unknown Source)

at com.sap.nwmss.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)

at com.sap.nwmss.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)

at com.sap.nwmss.jdbc.base.BaseConnection.connect(Unknown Source)

at com.sap.nwmss.jdbc.base.BaseConnection.setupImplConnection(Unknown Source)

at com.sap.nwmss.jdbc.base.BaseConnection.open(Unknown Source)

at com.sap.nwmss.jdbc.base.BaseDriver.connect(Unknown Source)

at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)

at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)

at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:302)

... 14 more

[Bootstrap module]> Problem occurred while performing synchronization.

No local properties available for [ConnectionsManipulator].

No local properties available for [LicensingManager].

No local properties available for [ClassLoaderManager].

No local properties available for [PoolManager].

No local properties available for [LogManager].

No local properties available for [CacheManager].

No local properties available for [IpVerificationManager].

No local properties available for [kernel_shell_commands].

No local properties available for [PortsManager].

No local properties available for [LockingManager].

No local properties available for [ThreadManager]

jvm_server0.out

java.lang.NullPointerException

at com.sap.engine.boot.FrameThread.shutdown(FrameThread.java:101)

at com.sap.engine.boot.StartFrame.shutdown(StartFrame.java:163)

at com.sap.engine.boot.Start$1.run(Start.java:42)

std_server0.o00

SAP J2EE Engine Version 7.00 PatchLevel is running!

PatchLevel January 31, 2007 18:37 GMT

>

Login :### Excluding compile: com.sap.engine.services.webservices.jaxrpc.encoding.TypeMappingImpl::initializeRelations

1. Excluding compile: com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType::_loadInto

2. Excluding compile: com.sap.engine.services.webservices.jaxrpc.encoding.InstanceBuilder::readElement

3. Excluding compile: com.sap.engine.services.webservices.jaxrpc.encoding.InstanceBuilder::readSequence

SAP J2EE Engine Version 7.00 PatchLevel is shutting down! PatchLevel January 31, 2007 18:37 GMT

Stopping services.

Service com.sap.aii.adapter.file.svc stopped. (0 ms)

Service com.sap.aii.af.ispeak.svc stopped. (31 ms)

Service com.sap.aii.adapter.mail.svc stopped. (0 ms)

Service com.sap.aii.adapter.jdbc.svc stopped. (0 ms)

Service com.sap.aii.adapter.rfc.svc stopped. (266 ms)

Service com.sap.aii.adapter.xi.svc stopped. (32 ms)

Service com.sap.aii.adapter.bc.svc stopped. (0 ms)

Service com.sap.aii.adapter.marketplace.svc stopped. (0 ms)

Service com.sap.aii.adapter.jms.svc stopped. (0 ms)

Service com.sap.aii.af.ms.svc stopped. (47 ms)

Service com.sap.aii.af.svc stopped. (0 ms)

Service com.adobe~XMLFormService stopped. (0 ms)

Service com.adobe~FontManagerService stopped. (15 ms)

Service rfcengine stopped. (0 ms)

Service ejb stopped. (5375 ms)

Service com.sap.aii.af.security.service stopped. (0 ms)

Service com.sap.aii.af.cpa.svc stopped. (62 ms)

Service sld stopped. (0 ms)

Service com.adobe~TrustManagerService stopped. (16 ms)

Service com.adobe~DocumentServicesConfiguration stopped. (0 ms)

Service com.adobe~DocumentServicesDestProtoService stopped. (0 ms)

Service tc_disdic~srv stopped. (0 ms)

Service com.adobe~PDFManipulation stopped. (0 ms)

Service com.adobe~DocumentServicesLicenseSupportService stopped. (0 ms)

Service com.adobe~DocumentServicesBinaries2 stopped. (0 ms)

Service com.adobe~DataManagerService stopped. (0 ms)

Service webdynpro stopped. (0 ms)

Service tc_secwssec~service stopped. (0 ms)

Service tc_secvsi~service stopped. (0 ms)

Service pmi stopped. (16 ms)

Service tc_secdestinations~service stopped. (0 ms)

Service tc_secsecurestorage~service stopped. (0 ms)

Service appclient stopped. (0 ms)

Service jmsconnector stopped. (0 ms)

Service servlet_jsp stopped. (1687 ms)

Service adminadapter stopped. (0 ms)

Service com.adobe~LicenseService stopped. (0 ms)

Service monitor stopped. (344 ms)

Service basicadmin stopped. (78 ms)

Service configuration stopped. (0 ms)

Service dsr stopped. (47 ms)

Service telnet stopped. (0 ms)

Service tc_eCATTPingservice stopped. (0 ms)

Service shell stopped. (0 ms)

Service caf_umrelgroups~imp stopped. (0 ms)

Service ssl stopped. (0 ms)

Service keystore stopped. (0 ms)

Service classload stopped. (0 ms)

Service jms_provider stopped. (16 ms)

Service caf_ummetadata~imp stopped. (0 ms)

Service applocking stopped. (0 ms)

Service tc_lmctc_confsservice_sda stopped. (0 ms)

Service tc.monitoring.logviewer stopped. (265 ms)

Service CUL stopped. (0 ms)

Service apptracing stopped. (31 ms)

Service jmx stopped. (16 ms)

Service security stopped. (0 ms)

Service com.sap.security.core.ume.service stopped. (0 ms)

Service dbpool stopped. (125 ms)

Service connector stopped. (125 ms)

Service webservices stopped. (656 ms)

Service licensing stopped. (0 ms)

Service iiop stopped. (63 ms)

Service ts stopped. (0 ms)

Service failover stopped. (0 ms)

Service javamail stopped. (0 ms)

Service naming stopped. (0 ms)

Service userstore stopped. (15 ms)

Service memory stopped. (0 ms)

Service MigrationService stopped. (0 ms)

Service file stopped. (0 ms)

Service bi_mmrdeployer stopped. (0 ms)

Service deploy stopped. (0 ms)

Service locking stopped. (0 ms)

Service classpath_resolver stopped. (0 ms)

Service p4 stopped. (16 ms)

Service cross stopped. (0 ms)

Service http stopped. (0 ms)

Service caf_runtimeconnectivity~impl stopped. (0 ms)

Service timeout stopped. (0 ms)

Service trex.service stopped. (0 ms)

Service log_configurator stopped. (0 ms)

Service jmx_notification stopped. (0 ms)

Service runtimeinfo stopped. (0 ms)

i cant consolidate all this info

thanks

ravi

[Former Member · Accepted solution]

Please check whether db user "sapsr3db" is locked in database. If yes unlock and change the password. Once that is done goto Configtool and update the password for SAPSR3DB in secure store.

Apply and save the changes. Restart.

[Former Member · Accepted solution]

Connect to Oracle and check the following.

select USERNAME,USER_ID,ACCOUNT_STATUS from dba_users and check if any of the OPS$ accounts are locked .

Unlock it and reset the password and populate the same in secure store in configtool .

[Former Member · Accepted solution]

hi

as i've mentioned at the start that we're using MS SQL Sever 8.0 .how would i check in that. As BR tools are available for Oracle only.

thanks

ravi

[JPReyes · Accepted solution]

connect to MSSQL via "sqlplus" and check that the user is not locked with the command above.

Also check note 400241 if you are having issues with OPS$ users.

Regards

Juan

[Former Member · Accepted solution]

Hi Ravi,

Can you check through config tool whether emergency user is activated.

cluster_data -> Server -> cfg -> services -> Propertysheet com.sap.security.core.ume.service

Parameter: ume.superadmin.activated

Value: true

Regards,

Ganesh

[Former Member · Accepted solution]

hi ganesh

as i've mentioned earlier that configtool is down and visual administrator is also not running so i cant check property sheets from there.

thanks

Ravi

[lakshminarayanan_m · Accepted solution]

Hi ,

What is your database oracle or db2 or what.

If it is oracle, - check the user sapsiddb in oracle , whether the user account is locked .

to check in oracle us cmd :

" select username, account_status from dba_users; "

if the users sapsiddb is locked , unlock the user

" alter user sapsiddb account unlock; "

Cuold you pls update.

regards

MLN

[lakshminarayanan_m · Accepted solution]

whats up?

[JPReyes · Accepted solution]

whats up?

What's up with what?...

refrain from making unnecesary posts.

Regards

Juan

[Former Member · Accepted solution]

hi laxminarayana

the database we're using MSSQL Server 8.0......which users to check and how??

thanks

Ravi

[JPReyes · Accepted solution]

Are you reading the thread at all?...

People is suggesting you to check that the users are not locked.

Follow the advice above.

Regards

Juan

[Former Member · Accepted solution]

hi juan

i am sure that i'm reading the thread but kindly please PAY ATTENSION that people other than YOU are suggesting to check ORACLE USERS while WE DONT HAVE ORACLE INSTALLED IN OUR SAP SYSTEM RATHER WE HAVE MSSQL SERVER 8.0 INSTALLED,which i've mentioned when i stated the problem.

And as i have'nt worked in MSSQL,so i dont have an idea as to what users need to be checked in MSSQL for the current problem,i am trying to communicate the same to others as well.

Meanwhile i 've checked we dont have a problem with OPS$ user in MSSQL,as suggested by you in your post,but even this has'nt solved the problem.

thanks

Edited by: ravi raj on Dec 2, 2008 4:42 PM

Edited by: ravi raj on Dec 2, 2008 4:45 PM

[JPReyes · Accepted solution]

I was very clear in my post and told you that the recommended SQL commands suggested could be used via sqlplus in MSSQL.

Since then you haven't updated the post.

You need to keep clear track of your action in the thread so people can recommend next actions to take.

Regards

Juan

BTW: Usage of UPPERCASE is not recommended in the "Rules of Engagement".

[Former Member · Accepted solution]

Hi,

Check this thread , similarity in both the cases is the bootstrap error, not sure but just give it a try to start SDM in that way.

Regards

KVR

[Former Member · Accepted solution]

hi KVR

the thread link that you've mentioned in your post doesn't exist anymore

thanks

Ravi

[Former Member · Accepted solution]

Remove the "," from the link. the thread is valid

Regards,

Jazz

[Former Member · Accepted solution]

Hi Ravi,

Could you please use jcmon pf=/usr../<instance_profile>

and try to start from there check at which step java stops.

You can also try this

Open command prompt in directory /usr/sap///SDM/program and execute:

sdm jstartup "mode=integrated"

and try to start Java again.

Please let us know your status.

Thanks&Regards,

Gagan Deep Kaushal

[Former Member · Accepted solution]

Hi gagandeep

i executed the command u've mentioned in your post & restarted java rhereafter, It executed sucessfully without stopping anywhere.And gives a return code=0 & a message:- Operation mode for Jstartup framework has already been set to "integrated",at the end.

But it doesn't solve the problem.

Thanks

Ravi

[Former Member · Accepted solution]

Hi,

have You recently Update your kernel Version?

This may cause in case you have Different versions of sapstartsrv.exe.

Pleaes confirm..

Regards,

Gagan Deep Kaushal

[Former Member · Accepted solution]

hi Gagandeep

no i haven't upgraded kernel anytime recent.And,Sorry i forgot to tell you i'm still working on first part of the two suggestions which you gave in your previous post....will update on that as well once i'm done.

Thanks

Ravi

Edited by: ravi raj on Dec 3, 2008 2:03 PM

[Former Member · Accepted solution]

hi jazz

i've tried the solution given in link in ur post,but SDM does'nt come up even after completing the mentioned steps over there sucessfully.

Thanks

Ravi

Edited by: ravi raj on Dec 3, 2008 3:32 PM

[Former Member]

hi

sorry for a late reply.

The problem was related to default port 1433 used in jdbc/pool/EPA/Url key in secure store of the configtool being blocked, it can be resolved by either unblocking the port or specifying a free port, for eg: i used port 2433 instead of the defualt one.

Following SAP notes were helpful in analysis of the issue:

sapnote_0000940893

sapnote_0000997510

thanks

ravi

Edited by: ravi raj on Apr 22, 2009 7:07 AM

[Former Member]

Hi Ravi ,

Please go through This Note and set VM parameter According to this

Note [723909|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=723909] - Java VM settings for J2EE 6.40/7.0.

Regards,

Gagan Deep Kaushal

[Former Member]

hi Gagandeep

Thanks for your quick replies,i 've checked my Java VM settings,there seems no problems with them.

reagards

Ravi

[Former Member]

Hi,

Firstly you have to check the server0.log file inthe folder

usr/sap/sid/instance/j2ee/cluster/server0/log/system it contains the more detailed info.

Regards,

Vamshi.

[Former Member]

Hi

Check out the sapnote " Note 1124079 - Connection error in the gateway " which speaks about anomoly in the software component release SAP_Basis.

I hope this may help you

Rgds

Radhakrishna D S