Skip to Content
author's profile photo Former Member
Former Member

Problem during and after implementation of SPS09

We have applied SPS10 to our Portal box.

The deployment cancelled half way through. When I restarted it it continued. Few components have got Deployed with Warning status saying that the component was not deployed as it was already deployed before.

On the Deployed Tab I could see the right version for those components.

When I tried to rerun it the deployment was finishing with message:

ActionStateUpdater.getStateForFurtherSCAction: Couldn't find any of the known states in groupedStatesSet.

Each time Java went down and I had to restart it to continue.

When I try 'new deployment' most of the patches has got the DEPLOYED status. I go even the screen when I got DEPLOYED for all of them but after few minutes JSPM came back with the error. Now it fails each time as SDM goes down.

Now in std_server0.out I get the following error:

Jan 9, 2007 9:07:48 AM ...services.webdynpro.WebDynproContainer [SAPEngine_System_Thread[impl:5]_36] Fatal: Error occured du

ring preparation of application startup.

Has anyone have similar problem.

How did you apply the SPS10 for Portal.?

Did you apply Java components first and then the rest (EP components)? Or did you apply all components at the same time(this is how I did it and it worked fine

with SPS09)

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jan 09, 2007 at 06:01 AM

    Oooo ... one more question.Is there any way of redoing the patch for Java?

    Or do I have to restore the whole portal system?

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 09, 2007 at 06:32 AM

    Hi Robert

    Answer to your second question.Yes you can redeploy .You dont have to restore the whole portal box.There is a option in JSPM using which you can do so.But i would suggest you not to do it as it requires edit of few sap files.That is why i cant share it with you.

    Coming back to your problem:I will suggest you a work around

    1.Those sca's which gave error during the depoyment through JSPM, use sdm to deploy it.

    2.In SDM you have three options of deployment which you can see in the below region od SDM

    3.Choose the option update any version.I think its third option and continue the deployment.

    Your prob will be solved

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 10, 2007 at 07:29 AM

    Thanks for the feedback.

    How should I start SDM deployment. i am pretty new to Java and so far I used only JSPM.

    Since then I have performed some additional steps. Currenly component JAPJTECHS fails with

    errors shown below. I had already a lot of problems with this stack.

    The deployment stoped on CAF component with similar errors. I have

    downloaded patch 1 fror CAF and this allowed me to finish deployment of

    that component.

    Then I had a failure of SAPJTECHS and I downloaded the patch 5 for this

    component. Unfortunately it did not resolve the problem and now I am

    stuck.

    What should be a general approach of using patches of selected components. is it safe to use like in my example patched CAF and SAPJTECHS components?

    Jan 10, 2007 10:33:21... Info: Starting to save the repository

    Jan 10, 2007 10:33:22... Info: Finished saving the repository

    Jan 10, 2007 10:33:22... Info: Starting: Update: Selected development

    component 'com.sap.lcr'/'sap.com'/'SAP AG'/'7.0010.20061

    103143828.0000'/'0' updates currently deployed development

    component 'com.sap.lcr'/'sap.com'/'SAP AG'/'7.0010.20061002105823.0

    000'/'0'.

    Jan 10, 2007 10:33:22... Info: SDA to be

    deployed: /usr/sap/DPS/JC06/SDM/root/origin/sap.com/com.sap.lcr/SAP

    AG/0/7.0010.20061

    103143828.0000/lcrserver.ear

    Jan 10, 2007 10:33:22... Info: Software type of SDA: J2EE

    Jan 10, 2007 10:33:22... Info: ***** Begin of SAP J2EE Engine

    Deployment (J2EE Application) *****

    Jan 10, 2007 10:33:55... Info: Begin of log messages of the target

    system:

    07/01/10 10:33:22 -

    ***********************************************************

    07/01/10 10:33:24 - Start updating EAR file...

    07/01/10 10:33:24 - start-up mode is lazy

    07/01/10 10:33:25 - EAR file updated successfully for 894ms.

    07/01/10 10:33:25 - Start updating...

    07/01/10 10:33:28 - EAR file uploaded to server for 1303ms.

    07/01/10 10:33:55 - ERROR: NOT updated. The Deploy Service returned

    the following error:

    For detailed information see the log file of the

    Deploy Service.

    Exception is:

    com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected

    exception.Nested exception is:

    java.io.EOFException: End of stream is reached

    unexpectedly during input from Socket[addr=/10.6.4.114,

    port=50604,localport=51431]

    java.io.EOFException: End of stream is reached

    unexpectedly during input from Socket[addr=/10.6.4.114,por

    t=50604,localport=51431]

    at com.sap.engine.services.rmi_p4.Connection.run(Connection.java(Compiled Code))

    at java.lang.Thread.run(Thread.java:570)

    07/01/10 10:33:55 -

    ***********************************************************

    Jan 10, 2007 10:33:55... Info: End of log messages of the target system.Jan 10, 2007 10:33:55... Info: ***** End of SAP J2EE Engine Deployment

    (J2EE Application) *****

    Jan 10, 2007 10:33:55... Error: Aborted: development

    component 'com.sap.lcr'/'sap.com'/'SAP

    AG'/'7.0010.20061103143828.0000'/'

    0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP

    AG'/'1000.7.00.10.5.20070105101200''/'0':

    Caught exception during application deployment from SAP J2EE Engine's

    deploy API:

    com.sap.engine.deploy.manager.DeployManagerException: ERROR: NOT

    updated. The Deploy Service returned the following error: com

    .sap.engine.services.rmi_p4.P4RuntimeException: Unexpected

    exception.Nested exception is:

    java.io.EOFException: End of stream is reached unexpectedly

    during input from Socket[addr=/10.6.4.114,port=50604,local

    port=51431]

    Exception is:

    com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected

    exception.Nested exception is:

    java.io.EOFException: End of stream is reached unexpectedly

    during input from Socket[addr=/10.6.4.114,port=50604,local

    port=51431]

    java.io.EOFException: End of stream is reached unexpectedly during

    input from Socket[addr=/10.6.4.114,port=50604,localport=514

    31]

    at com.sap.engine.services.rmi_p4.Connection.run(Connection.java(Compiled Code))

    at java.lang.Thread.run(Thread.java:570)

    (message ID:

    com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).

    DMEXC)

    Jan 10, 2007 10:33:55... Info: Starting to save the repository

    Jan 10, 2007 10:33:56... Info: Finished saving the repository

    Jan 10, 2007 10:33:56... Info: Starting: Update: Selected software

    component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.10.5.2

    0070105101200''/'0' updates currently deployed software

    component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.9.0.2006081800510

    0''/'1'.

    Jan 10, 2007 10:33:56... Error: Aborted: software

    component 'SAP_JTECHS'/'sap.com'/'SAP

    AG'/'1000.7.00.10.5.20070105101200''/'

    0':

    Failed deployment of SDAs:

    development component 'com.sap.lcr'/'sap.com'/'SAP

    AG'/'7.0010.20061103143828.0000'/'0' : aborted

    Please, look at error logs above for more information!

    Jan 10, 2007 10:33:56... Info: Starting to save the repository

    Jan 10, 2007 10:33:57... Info: Finished saving the repository

    Jan 10, 2007 10:33:57... Info: Restoring the state of the instance

    (JC_ddrsap14_DPS_06) process dispatcher from Stopped to Run

    ning

    Jan 10, 2007 10:33:57... Info: ====================================

    Jan 10, 2007 10:33:57... Info: JControl is shutting SDM Server down

    Jan 10, 2007 10:33:57... Info: ====================================

    Jan 10, 2007 10:33:57... Info: Server finished sending back the answer

    of the ShutdownRequest.

    Jan 10, 2007 10:33:57... Info: Shutting dispatcher down

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.