Skip to Content
author's profile photo
Former Member

J2EE Server doesn't start

I was doing a deployment from a WebDynpro application which stopped responding and stayed there forever.

To get around this I shut down dev studio and then stopped the J2EE server using the MMC.

Now when I try to restart, the server doesn't start again.

Any pointers appreciated,

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

4 Answers

  • Best Answer
    author's profile photo
    Former Member
    Oct 04, 2005 at 08:20 PM

    to do a troubshoting, you can do a manual start of J2EE server. Please refer to the note: 604080 for more information.

    Jason

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Rakshit,

      I think that your Database Log or Data is 100% (full).

      Please check the size of your database. In MMC, click on the database(Blue Color Icon). If it shows 100%, from the left hand side menu, click on Volumes under Configuration category. Then add another Data/Log volume depending on what is full. Change the MAXDATAVOLUMES or MAXLOGVOLUMES if required and then Click on Add Log/Data Volume.

      Then click on Offline Button. Wait till Online button is active. Now click on Online. Now restart your complete Server.

      This should work.

      Regards,

      Shubham

  • author's profile photo
    Former Member
    Oct 04, 2005 at 07:12 AM

    Hi,

    any log outputs available ?

    Without any further information it's difficult to guess about the cause of the problem.

    Regards, Astrid

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Oct 05, 2005 at 03:02 AM

    Hi Rakshit,

    Open MMC, expand the tree, right click start. Select process list

    If it is not started, you can find some process either with grey or yellow(red also). Right click on the process list select developer trace. This is the log Can.copy and paste in this message.

    the same logs you can find \usr\sap\<SID>\Jc00\work

    regards

    Anand.M

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Oct 06, 2005 at 12:18 PM

    We had the same issue with root cause full data log, and we solved it the following ( extract from a document created after we found the solution):

    <b>Applies to</b>

    SAP WAS 6.40 SP 13 including

    J2EE Engine 6.40 PatchLevel 95420. 313 on

    Microsoft Windows 2003 Server with SP 2 using / connected to

    SAP DB.

    <b>Issue</b>

    The J2E engine doesn't complete the startup process successfully.

    In SAP MMC status is "Some processes running..."

    <b>Indication</b>

    The instance is marked yellow. The application server therefore can't be accessed, deploying of applications via SAP Netweaver Developer Studio is not possible.

    <b>Possible problem</b>

    It seems that the underlying databases' full log-table/-file is causing the problem,

    while the options are set as below:

    auto-log : on

    log overwrite : on

    <b>Solution</b>

    Possible solution to this is to clear log table by backup the existing data and log data. It was found out that the system obviously clears the log automatically afterwards.

    <b>How-To</b>

    To get this to work, do the following:

    On server-side start the Database Manager and

    log on to you database by

    selecting the instance and the connect to button

    and providing username and password for logon.

    Select Backup Wizard from the left pane and choose the Backup-Wizard. on the Welcome screen click "next".

    Now select "Log Backup" and select a backup medium on the following screen (you have to create one if no exists).

    Click "next" and "Start". The backup will be started.

    If you get an error message such as “error 24998 “, you have to switch off

    the “log overwrite” mode via Configuration -Configuration Wizard.

    The Log Backup will be performed and then the log-table will be cleared.

    Now you can restart the server - instance as usual via SAP MMC.

    <b>Conclusion</b>

    It worked for us with the limitation that we switched off log afterwards.

    Add comment
    10|10000 characters needed characters exceeded