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

Problem with debug mode of portal (EP6 SP2)

Hello,

I've searched here a long time now, but didn't find any soloution for my problem.

I want to start up the portal in debug mode.

I did it in the config tool: I set the server node to debug and selected a free port, then restarted the dispatcher with go.bat. It starts the server and the server element joines. But when I try to open the portal I only get the message "dispatcher running, but no server connected!".

When I disable debug mode everything works fine!

Can anyone help me?

Cheers,

Michael

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jan 10, 2005 at 04:16 PM

    Hi Michael,

    one way is to enhance the server go.bat with debug parameters. Under c:\usr\sap\<SID>\j2ee\<INSTANCE>\cluster\server\go.bat define the following params

    set DEBUG_PORT=5000

    set DEBUG_PARAMS=-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=

    and add both params to the java arguments (e.g. behind the -classpath): %DEBUG_PARAMS%%DEBUG_PORT%.

    Regards,

    Stefan

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 10, 2005 at 04:52 PM

    Thank you,

    I will try this. But the problem is, that our dispatcher automatically starts the server, "go.bat" is never used to start the server.

    So to use this tip, I have to reconfigure the dispatcher/server startup-settings.

    Cheers,

    Michael

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi,

      you can first start the server go.bat, wait some seconds till the server freezes and then start the dispatcher. The dispatcher will not launch the server again and the server resumes running after the dispatcher is up.

      Regards,

      Stefan

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.