cancel
Showing results for 
Search instead for 
Did you mean: 

Error while starting JSPM

Former Member
0 Kudos

Hello


I upgrade JSPM .in 7.01 SP7 but while starting JSPM  are getting error:

File JSPM_MAIN_1_01.LOG

<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[1.5.3.7185 - 630]/-->

<!--NAME[/usr/sap/SMS/DVEBMGS00/j2ee/JSPM/log/log_2013_01_04_14_46_45/JSPM_MAIN_1_01.LOG]/-->

<!--PATTERN[JSPM_MAIN_1_01.LOG]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %m)]/-->

<!--ENCODING[UTF8]/-->

<!--LOGHEADER[END]/-->

Jan 4, 2013 2:48:21 PM [Info]: Phase JSPM/JSPMPhases/JSPM_MAIN has been started.

Jan 4, 2013 2:48:21 PM [Info]: Phase type is com.sap.sdt.jspm.phases.PhaseTypeJSPM.

Jan 4, 2013 2:48:21 PM [Info]: Starting Initialize dialog...

Jan 4, 2013 2:48:21 PM [Info]: Detecting system parameters...

Jan 4, 2013 2:48:21 PM [Info]: You can find additional information in log file /usr/sap/SMS/DVEBMGS00/j2ee/JSPM/log/log_2013_01_04_14_46_45/DETECT_SYSTEM_PARAMETERS_01.LOG.

Jan 4, 2013 2:48:24 PM [Error]: Exception has occurred during the execution of the phase.

Jan 4, 2013 2:48:24 PM [Error]: Error while retrieving profile using filter SCSInstanceFilter/sid:SMS/host:null.

Jan 4, 2013 2:48:24 PM [Error]: Cannot initialize application data.

Jan 4, 2013 2:48:24 PM [Info]: Phase JSPM/JSPMPhases/JSPM_MAIN has been completed.

Jan 4, 2013 2:48:24 PM [Info]: Start time: 2013/01/04 14:48:21.

Jan 4, 2013 2:48:24 PM [Info]: End time: 2013/01/04 14:48:24.

Jan 4, 2013 2:48:24 PM [Info]: Duration: 0:00:02.995.

Jan 4, 2013 2:48:24 PM [Info]: Phase status is error.

More informations with file TroubleTicket_01.txt

Trouble Ticket Report

Java Support Package Manager for SAP NetWeaver'04s

SID................: SMS

Hostname...........: devsmssa

Install directory..: /usr/sap/SMS

Database...........: Oracle

Operating System...: UNIX

JDK version........: 1.4.2 IBM Corporation

JSPM version.......: 7.01.8.1.1

System release.....: 700

ABAP stack present.: false

The execution ended in error.

Cannot initialize application data.

Error while retrieving profile using filter SCSInstanceFilter/sid:SMS/host:null.

More information can be found in the log file /usr/sap/SMS/DVEBMGS00/j2ee/JSPM/log/log_2013_01_04_14_46_45/JSPM_MAIN_1_01.LOG.

Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Search for OSS notes with the following search terms:

com.sap.sdt.jspm.phases.PhaseTypeJSPM

com.sap.sdt.jspm.gui.JspmUiException

Cannot initialize application data.

JSPM_MAIN

JSPMPhases

Java Support Package Manager

Thanks in advanced.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

I tried to put the 8 SP but I still have the same error.

Former Member
0 Kudos

Hi Sarah,

   Did you rename rdisp/msserv_internal to 3900??

Please confirm whether dispatcher, SDM and Server processes are running.

Secondly please try to open SDM and check whether you are able to open SDM without any problem.

Thanks and Regards,

Vimal

Former Member
0 Kudos

Hi,

No, I don't understand why I need to change this parameter because I get this error since the update JSPM.

Also i have SCS01 after what you said the message server port is 3901 :
Usually the Message server port is 39XY, Where XY is the SCS instance number.

Yes I have access to SDM because it is with him that I update the JSPM in EP8 despite my problem

Former Member
0 Kudos

Else in my file Default.pfl, I have rdisp/msserv_internal to 3900

Former Member
0 Kudos

Ok Sarah. The synatx should be 39XX where XX is the system number. Since your system is ABAP + JAVA, you need to use 3900.Anyways youhave it in Default.profile so no problem.

I faced the same issue years ago and i think I fixed it by moving the mulitple profiles in the sapmnt directly.

Please go to /sapmnt/SID/profile directory and ensure that you have only start , default and instance profile. Any old version of start or default or instance profile , please move them out of profile directory.

Sometimes, JSPM hangs if there are multple profiles. Please give a try and kindly share the feedback.

Thanks and Regards,

Vimal

Former Member
0 Kudos

HI,

Please check the above suggestion and check whether it works.

Thanks and Regards,

Vimal

Former Member
0 Kudos

I verify and I'am not a multiple file profile.

I restarted JSPM but still the same error soI restarted the machine and now I have another error:

TroubleTicket_01.txt :

Trouble Ticket Report

Java Support Package Manager for SAP NetWeaver'04s

SID................: $(/J2EE/StandardSystem/SAPSystemName)

Hostname...........: $(/J2EE/SAPGlobalHost)

Install directory..: $(/J2EE/StandardSystem/SAPSIDDirectory)

Database...........: $(/J2EE/DBSystem/DBInfoName)

Operating System...: $(/J2EE/StandardSystem/CentralInstance/J2EEEngineInstanceHost/OpSysType)

JDK version........: 1.4.2 IBM Corporation

JSPM version.......: 1.1.106

System release.....: $(/J2EE/StandardSystem/Version)

ABAP stack present.: $(/J2EE/StandardSystem/BCSystemPresent)

The execution ended in error.

java.lang.ClassCastException: com.sap.sdt.ucp.phases.PhaseContext incompatible with com.sap.sdt.j2ee.J2eePhaseContext

java.lang.ClassCastException: com.sap.sdt.ucp.phases.PhaseContext incompatible with com.sap.sdt.j2ee.J2eePhaseContext

More information can be found in the log file /usr/sap/SMS/DVEBMGS00/j2ee/JSPM/log/log_2013_01_08_15_48_44/JSPM_MAIN_1_01.LOG.

Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Search for OSS notes with the following search terms:

com.sap.sdt.jspm.phases.PhaseTypeJSPM

com.sap.sdt.util.diag.JavaException

java.lang.ClassCastException: com.sap.sdt.ucp.phases.PhaseContext incompatible with com.sap.sdt.j2ee.J2eePhaseContext

JSPM_MAIN

JSPMPhases

Java Support Package Manager

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

JSPM_MAIN_1_01.LOG :

<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[1.5.3.7185 - 630]/-->

<!--NAME[/usr/sap/SMS/DVEBMGS00/j2ee/JSPM/log/log_2013_01_08_15_48_44/JSPM_MAIN_1_01.LOG]/-->

<!--PATTERN[JSPM_MAIN_1_01.LOG]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %m)]/-->

<!--ENCODING[UTF8]/-->

<!--LOGHEADER[END]/-->

Jan 8, 2013 3:48:52 PM [Info]: Phase JSPM/JSPMPhases/JSPM_MAIN has been started.

Jan 8, 2013 3:48:52 PM [Info]: Phase type is com.sap.sdt.jspm.phases.PhaseTypeJSPM.

Jan 8, 2013 3:48:52 PM [Error]: Exception has occurred during the execution of the phase.

Jan 8, 2013 3:48:52 PM [Error]: java.lang.ClassCastException: com.sap.sdt.ucp.phases.PhaseContext incompatible with com.sap.sdt.j2ee.J2eePhaseContext

Jan 8, 2013 3:48:52 PM [Info]: Phase JSPM/JSPMPhases/JSPM_MAIN has been completed.

Jan 8, 2013 3:48:52 PM [Info]: Start time: 2013/01/08 15:48:52.

Jan 8, 2013 3:48:52 PM [Info]: End time: 2013/01/08 15:48:52.

Jan 8, 2013 3:48:52 PM [Info]: Duration: 0:00:00.006.

Jan 8, 2013 3:48:52 PM [Info]: Phase status is aborted.

Former Member
0 Kudos

Problem solved

I apply patch JSPM08P_2-20002796.SCA with SDM.

Thank.

Answers (2)

Answers (2)

Former Member
0 Kudos

is it possible to uninstall the new version of JSPM?

Former Member
0 Kudos

Hi Sarah,

   Did you rename rdisp/msserv_internal to 3900??

Please confirm whether dispatcher, SDM and Server processes are running.

Secondly please try to open SDM and check whether you are able to open SDM without any problem.

Thanks and Regards,

Vimal

Former Member
0 Kudos

Hi Sarah,

   Can you please attach the log /usr/sap/SMS/DVEBMGS00/j2ee/JSPM/log/log_2013_01_04_14_46_45/JSPM_MAIN_1_01.LOG ??

Please reivew the following notes for more reference and check whether it works.

Note 1765565 - JSPM fails to detect JAVA instances during update

Note 936916 - JSPM: Cannot detect system kernel

Note 914818 - JSPM: Could not detect database

Please attach the logs to analyze the issue further.

Thanks and Regards,

Vimal

Former Member
0 Kudos

I looked at the notes, but I did not find any that had the same error.


I have attached the file.

Thanks

Former Member
0 Kudos

Hi,

Can you please try to attach /usr/sap/SMS/DVEBMGS00/j2ee/JSPM/log/log_2013_01_04_14_46_45/DETECT_SYSTEM_PARAMETERS_01.LOG.file as well.??

Thanks and Regards,

Vimal

Former Member
0 Kudos

Hi,

As well as please confirm whether you are trying to start JSPM using sidadm as well as java env is set.

Please ensure above two checks are done.

Thanks and Regards,

Vimal

Former Member
0 Kudos

I log in smsadm.

how do I check java set ? I verified a java path and is good.

Former Member
0 Kudos

Hi,

   Lets give a try with this.

Check whether the following parameters are available in DEFAULT.PFL .

j2ee/dbtype =   <db type>             

j2ee/dbname = <db name>       

j2ee/dbhost =   <db host server>

perform the following actions.

Edit the start SCS profile START_SCS<instance number>_<SCS Host> by adding the rdisp/msserv_internal = 39<instance profile>

Example:

START_SCS01_SCShost - central service instance start profile

rdisp/msserv_internal = 3901

and add the parameter at the end of the START_SCS01_SCShost profile.

Usually the message server port is 39XY, where XY is the SCS instance

number.

Afterwards, repeat the failed step in JSPM.

Thanks and Regards,

Vimal

Former Member
0 Kudos

I check in default.pfl is goo.

I add entry rdisp/msserv_internal = 3901 in my file START_SCS01_devsmssa and i reboot but I have the same error....

Former Member
0 Kudos

Hi,

   It should be 3900 not 3901

Please change to 3900 and restart the server and check.

Thanks and Regards,

Vimal

Former Member
0 Kudos

Hi Sarah,

Please check whether any old process by name of JSPM, if its running kill the same and then try to launch the JSPM again.

Regards

Punit

Former Member
0 Kudos

I verify but i'm not other JSPM process.