Skip to Content
author's profile photo
Former Member

WebAS problem

Posted on Jan 24, 2005 at 10:25 AM 4 Views

Hi,

I have WebAS 6.4 SP9 and EP6 SP9. I have problem with WeAS, sometimes it works normaly but sometimes not. I get errors:

Dispatcher running, but no server connected!

Details: No details available

or

Application stopped!

Details: You have requested an application that is currently stopped

After few minutes it works normaly for a while. This repeats all the time. Any solution?

SAP NetWeaver Application Server
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • author's profile photo
    Former Member
    Posted on Jan 24, 2005 at 03:36 PM

    Hi Mrkvicka,

    after restarting the server it is possible that these Messages appear:

    The server is already "green" in the mmc but not ready starting yet.

    The startup of j2ee server can take a few minutes.

    Regards,

    André

    Add comment
    10|10000 characters needed characters exceeded

    • Abdul Razack
      Jan 25, 2005 at 04:59 PM

      Hello,

      If you continue to have problem accessing your application, it could be that your application has not been started. To resolve this open the visual admin and go to the deploy service under the server node. on the right hand pane you will see a list of application and just start your application.

      Regards

      Abdul

  • author's profile photo
    Former Member
    Posted on Jan 26, 2005 at 05:32 AM

    This message:

    Dispatcher running, but no server connected!

    indicates that your server process is NOT in the "Running" state.

    Are you sure your server process is not restarting?

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Posted on Feb 01, 2005 at 03:17 PM

    Yes, it is restarting but why it`s always restarting after a few minutes of normal work?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member
      Feb 01, 2005 at 06:38 PM

      In order to find it you can use Log viewer from Visual Admin tool.

      The most common problem is memorry setting, WAS is very sensetive to it. Just look for "WAS memory settings" in OSS and you will find a message on how you should set it for your hardware.

      Hope it helps.

      Victor.