cancel
Showing results for 
Search instead for 
Did you mean: 

Error in START_J2EE_INITIAL phase of PI7.1 Ehp1 Upgrade

Former Member
0 Kudos

START_J2EE_INITIAL_TJI_02.LOG

-


com.sap.sdt.j2ee.phases.PhaseTypeControlEngine com.sap.sdt.ucp.phases.PhaseException Could not start AS Java instance with name J2EE and number 03 of the standard system. START_J2EE_INITIAL DOWNTIME UPGRADE NetWeaver Upgrade SAPJup Java Upgrade

-


dev_server0 log

F [Thr 26215] Tue Dec 1 20:22:27 2009

F [Thr 26215] *** WARNING => SfCFramework::registerNatives: failed for com.sap.conn.rfc.driver.CpicDriver [sfxxifrw.hpp 165]

M

M [Thr 21075] Tue Dec 1 20:22:46 2009

M [Thr 21075] ***LOG Q0I=> NiPConnect: 127.0.0.1:3305: connect (79: A remote host refused an attempted connect operation.) [nixxi.cpp 2777]

M [Thr 21075] *** ERROR => NiPConnect: SiConnect failed for hdl 25/sock 72

(SI_ECONN_REFUSE/79; I4; ST; 127.0.0.1:3305) [nixxi.cpp 2777]

-


std_server0. log

Service [com.sap.security.core.ume.service] start ================= ERROR =================

com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: com.sap.conn.jco.JCoException: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed

Connection parameters: TYPE=A DEST=SAPJup ASHOST=localhost SYSNR=05 PCS=1

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

ERROR partner '127.0.0.1:3305' not reached

TIME Tue Dec 1 20:17:29 200

RELEASE 711

COMPONENT NI (network interface)

VERSION 39

RC -10

MODULE nixxi.cpp

LINE 2777

DETAIL NiPConnect: 127.0.0.1:3305

SYSTEM CALL connect

ERRNO 79

ERRNO TEXT A remote host refused an attempted connect operation.

COUNTER 3

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

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

at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)

at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)

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

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

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

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

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: com.sap.conn.jco.JCoException: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed

Connection parameters: TYPE=A DEST=SAPJup ASHOST=localhost SYSNR=05 PCS=1

-


In this phase it is trying to starup the instance with 03 sys no, but std_server0 log shows that ume service is trying to connect

to instance with sys-no 05 ( shadow).

I also refered to the wiki link,

https://wiki.sdn.sap.com/wiki/pages/viewpage.action?spaceKey=JSTSG&title=(SLTG)(SAPJUP)+Problems-P1&...

where it says the DDIC password needs to be same in both 000 and the ume store client ( eg 030), which i checked in our case

and the DDIC password is the same,

Experts please help, helpful answers will be fully rewarded with points.

Thanks,

Govind

Edited by: Govind Prathi on Dec 2, 2009 5:24 PM

Edited by: Govind Prathi on Dec 2, 2009 5:27 PM

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello Govind,

many years ago but I'm facing the same problem with a dual stack upgrade (solman 7.2).

Within that start of java the required abap shadow instance isn't running any more. Have you found a solution for your problem? Because I'm not able to start shadow instance at that point in time.

Many thanks and kind regards

Roland

Former Member
0 Kudos

Hi Govind,

please post the /work/dev_jcontrol trace file.

maybe the following link helps you to analyze your problem regarding RFC_ERROR_COMMUNICATION

http://help.sap.com/saphelp_nw70/helpdata/EN/20/361941edd5ef23e10000000a155106/content.htm

Please have a look in dev_jrfc.trc files. These files are written by JRFC and can be found in the directories j2ee/cluster/server* of the J2EE Application Server Installation. The following document describes, how tracing can be switched on/off:

http://help.sap.com/saphelp_nw70/helpdata/en/f6/daea401675752ae10000000a155106/content.htm

Be sure that j2ee_admin user is not locked.

Check /etc/services for '127.0.0.1:3305'

please also be sure that the UME.Properties settings in com.sap.security.core.ume.service are correct:

Please start offline configtool, goto cluster_data - server - cfg - services and check the property sheet

com.sap.security.core.ume.service

please also update ume.r3.connection.master.ashost with hostname of your portal server.

then restart your JAVA instance.

Is this dual stack (ABAP+JAVA) ?

Does your system is running on High Availability server?

Gerd

Edited by: Gerd Schuster on Dec 2, 2009 5:09 PM

Edited by: Gerd Schuster on Dec 2, 2009 5:20 PM