Debugging EP6, WAS 6.20 with different Servernodes

[Former Member]

Hi,

has anybody out there an idea how to debug an EP6 on WAS 6.20 with 2 or more servernodes?

Status: Connecton WAS<->eclipse (as remote Java app) is OK but the programm won't stop at the breakpoint.

Any ideas??

Yours Walter

[darrell_merryweather · Accepted solution]

Walter

I have just been facing a similar issue today. From what I can tell, when you set the server node to run in debug mode (through the config tool), the dispatcher doesn't include the requests to this node as part of the load balancing, and the servers are not therefore included when making a standard request to the portal. However, if you include the http://<server>:<port>/irj;sapj2ee_*=<clusterElementId>; as part of the URL, the dispatcher will dispatch the request to the relevant server node. This also enables you to be able to debug a single server node, leaving the cluster still able to serve end users.

I found that without including the ;sapj2ee_* directive to the end of the URL on a single server node machine, that the dispatcher gives the message 'Dispatcher running but no server node connected', which was actually incorrect. As soon as I included the ;sapj2ee_* thingy it worked fine.

I hope this helps

Darrell

[Former Member · Accepted solution]

Dear Darrell,

thank You very much for Your fast reply.

Unfortunately I couldn't change the node usong the URL-extension.....

As far as I can see there is a configuration problem....

Yours Walter

[darrell_merryweather · Accepted solution]

Are you connecting to the correct port number. After you have configured the J2EE server to start in debug mode there should have been a line added to the service.ini file. There it should show you the port number that the server is waiting for debugging requests on. Make sure that this is the port that you are trying to connect to through your eclipse project. (Personally I use NWDS 2.10). Then, have your project code open, and create a breakpoint by double clicking on the line. Click Run-->Debug, set the connection properties and then click the debug butting. You should then open a browser window and use the URL that I mentioned before to direct you to the relevant server node. (You can check this by putting javascript:alert(document.cookie) and checking that the browser is connected to the correct server node.

If this doesn't work, then I am unsure as to what the problem may be

I hope this helps

Darrell

[Former Member · Accepted solution]

Darrel, thanks for your tips, they helped me solve a similar problem.

PS: Is it just me or do many of you feel that:

1. Documentation of NWDS is very 'flowery' (Read lots of colorful pdf files) but quite inadequate and widely dispersed.

2. Some very basic errors especially with PDE, for instance the wizard generates an incorrect portalapp.xml file for a JSPDynPage so that NONE of its important methods like doProcessBeforeOutput get executed!! see the post for topic "JSPDynPage does not work in EP6.0" for details.

[darrell_merryweather · Accepted solution]

Sanjeev

Some of the documentation can be difficult to find I must admin, however, the documentation is generally there deep deep down

As for the wizards, these work fine for me to be honest. Which environment are you using. I am currently using NWDS (Netweaver Developer Studio) 2.10 and it has all of the wizards in there and they work fine for me. The only one in this version that is a bit flaky is the Webservice wizard, but this may be resolved in the 2.11 version. Try using NWDS if you can

I hope this helps

Darrell