How to monitor Java Web Dynpro running sessions?

[Former Member]

A Java Web Dynpro application goes into a never-ending loop?

How the system administrator can monitor the running sessions of a pure J2EE engine (R6.40 SP12)?

In ABAP this is available via transaction SM50/SM51.

I tried but the shell command "PS" does not display Web Dynpro sessions.

Via "/nwa" there are several reports but I'm not able to find out running sessions.

Any idea? Thanks a lot.

[Former Member · Accepted solution]

Hello Sergio,

The question looks similar to this topic:

In case of a looping java application the best way to debug the problem is to create several thread dumps (note 710154) and analyze the running threads.

Best Regards

Vyara

[SergioFerrari · Accepted solution]

Thanks Vyara,

this question just looks similar to the other.

A user could be connected into a system (logged in) and at times she will be running (querying for orders) and then just "thinking" (she is reading the web page).

JCMon (710154) is an interesting tool but it just reports the status of the dispatcher, server0 and SDM process.

Ok from the dump I could find who is really active but it requires a big effort.

766598 contains the powerfull tool perfviewer.

I'm generating nice html reports but they seem oriented to statistics.

Even if now I have more tools in my bag I'm really not able to say which USER is "running" which of my WebDynpro application in each moment.

Are you?

Sergio

[Former Member · Accepted solution]

Hi Sergio,

did you have a look at the Web Dynpro Console? The <a href="http://help.sap.com/saphelp_nw04/helpdata/en/03/10b540e4c5782ae10000000a155106/frameset.htm">documentation</a> (the very bottom of the page) says you can get info about web dynpro applications status and sessions that execute.

Does that help in your case?

[SergioFerrari · Accepted solution]

Thanks you Ivaylo,

as the documentation states just counters are reported.

After several clicks (About Session - Local host - Client/User id:4 - ServerSession id: 3 - ClientSession id: 6 - ClientWindow id: 7 - Application id: id77) I can see the active Application Name.

About users, selecting Local host, I can just discover:

ClientUsers # 5

Destroyed by a logoff 0

Destroyed by a Timeout 2

and so on...

Sergio

(uhm, probably the active sessions will end in the meantime you drill-down to the right node)