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

Unable to logon to J2EE Server+Dispatcher running,but no server connected!

Hello Everybody!

I opened my J2EE Config Tool & I turned on the Server DEBUG MODE to "YES" via my J2EE Config Tool and then restarted my J2EE Server Instance via SAPMMC.I could see my J2EE server running.I didnot change anything else via the Config Tool.

When i try to access it via the URL "http://10.1.1.13:50000/index.html", i get the following error.

503 Service Unavailable.

Dispatcher running, but no server connected!

Then i tried to logon to the J2EE Visual Administrator and i get the following error.

Unable to Logon to Local Host

"End of Stream is reached unexpectedly during input from socket[addr=/10.1.1.13,port=50004,localport=3764].

Details: No details available

Any kind of help is greatly appreciated.

I Will assign you with the right rewards 😊

Thanks

Gisk

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on Oct 14, 2005 at 07:41 PM

    Hello Gisk,

    an interesting one, but logical. I asume you have a workplace installation, that means a single node. With Debug mode on, your server gets restarted and comes up in debug mode, which takes it out of normal dispatching. Only a specialy signed URL is now accepted and forwarded to this node.

    Because there is only one node in your system you get this message. You should be able to connect from the debug mode of devloper studio, as designed.

    Please use the debug mode only from there and switch it on and off from the server view.

    To manipulate via config tool makes sense only in larger systems, for example a central development system used by several developers or a productive system that you want to debug.

    Regards,

    Benny

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Sivakumar,

      to do this in your central system you use the same environment as with the local system. You have to configure your NWDS to connect to central system and then start debugging. It works as usual. Just go to the server view and restart a node in debug mode. The only difference is that you have to tell the debugger which node to connect to (in the debugger wizard they appear in a list).

      and bang, you are there.

      regards,

      Benny

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.