cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with debug mode of portal (EP6 SP2)

Former Member
0 Kudos

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

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

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

Former Member
0 Kudos

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

Former Member
0 Kudos

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