Issue Details (XML | Word | Printable)

Key: GLASSFISH-6238
Type: Bug Bug
Status: Open Open
Priority: Minor Minor
Assignee: Jennifer Chou
Reporter: yifeng1
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
glassfish

[UB] [Release Note] monitoring:after change virtual server for app, monitoring page shows old value

Created: 22/Sep/08 11:43 PM   Updated: 02/Dec/11 07:24 PM
Component/s: monitoring
Affects Version/s: V3
Fix Version/s: 4.0

Time Tracking:
Not Specified

Environment:

Operating System: Solaris
Platform: PC


Issuezilla Id: 6,238
Status Whiteboard:

gfv3-prelude-excluded

Tags: 3_1-exclude
Participants: abbagani, Anissa Lam, Byron Nevins, Gail Risdal, Jennifer Chou, kumara, Nazrul, Tom Mueller and yifeng1


 Description  « Hide

platform: open solaris
b25

to reproduce:
1. configuration -> monitoring->set value to high and save
2. applications->web applications->deploy, deploy webapps-simple.war and point
to server1
3. configuration->virutal servers->create new called myvs1, provide id,
hosts,and save
4. configuration->http listeners->create new http listeners,provide name,
network address, listener ort, default virtual server point to myvs1
5. applications->web applications-->click webapps-simple and change virtual
server to myvs1 , save
6.application server->monitoring->web container,
select application webapps-simple, notice that after page refresh, virtual
server shows server --> bug



Anissa Lam added a comment - 23/Sep/08 07:52 AM

not sure if this is gui issue or monitoring.
Jennifer please take a look


kumara added a comment - 23/Sep/08 11:23 AM

v3 defect tracking


Jennifer Chou added a comment - 23/Sep/08 01:37 PM

I also see this issue on CLI: asadmin get --monitor=true "server.applications.*"

When I restart the appserver, then both the gui (Web Container tab) and CLI
(asadmin get --monitor=true "server.applications.*") show the newly changed
virtual-server, myvs1.

Seems to be a dynamic reconfig issue.
------------------------
There is a second problem I see though. After I restarted the appserver, the
HTTP Service tab (in gui) and the 'server.http-service.<virtual-server>.request
nodes from CLI get --monitor=true "request" still shows the old 'server' name:

C:\gfv3_0922\v3\distributions\web\target\glassfish\bin>asadmin get --monitor=tr
e "request"
server.http-service.__asadmin.request.count5xx-count = 0
server.http-service.__asadmin.request.count503-count = 0
server.http-service.myvs1.request.count5xx-count = 0
server.http-service.__asadmin.request.requestCount = 0
server.http-service.server.request.count302-count = 0
server.http-service.server.request.countother-count = 0
server.http-service.server.request.requestCount = 0
server.http-service.server.request.count400-count = 0
server.http-service.__asadmin.request.count401-count = 0
server.http-service.myvs1.request.count4xx-count = 0
server.http-service.__asadmin.request.countother-count = 0
server.http-service.__asadmin.request.count400-count = 0
server.http-service.server.request.errorCount = 0
server.web.request.processingTime = 149.55345911949686
server.web.request.maxTime = 14375
server.http-service.myvs1.request.count302-count = 0
server.http-service.__asadmin.request.count3xx-count = 0
server.http-service.myvs1.request.count401-count = 0
server.http-service.myvs1.request.count400-count = 0
server.http-service.myvs1.request.errorCount = 0
server.web.request.errorCount = 0
server.http-service.__asadmin.request.count200-count = 0
server.http-service.myvs1.request.maxTime = 0
server.http-service.__asadmin.request.count304-count = 0
server.http-service.server.request.count403-count = 0
server.http-service.__asadmin.request.maxTime = 0
server.http-service.myvs1.request.count403-count = 0
server.http-service.server.request.count404-count = 0
server.http-service.myvs1.request.countother-count = 0
server.http-service.__asadmin.request.processingTime = NaN
server.http-service.server.request.count200-count = 0
server.http-service.server.request.count2xx-count = 0
server.http-service.server.request.count4xx-count = 0
server.web.request.requestCount = 159
server.http-service.myvs1.request.count2xx-count = 0
server.http-service.server.request.maxTime = 0
server.http-service.__asadmin.request.count403-count = 0
server.http-service.myvs1.request.count200-count = 0
server.http-service.__asadmin.request.count302-count = 0
server.http-service.myvs1.request.processingTime = NaN
server.http-service.server.request.count5xx-count = 0
server.http-service.myvs1.request.count3xx-count = 0
server.http-service.__asadmin.request.count2xx-count = 0
server.http-service.myvs1.request.count503-count = 0
server.http-service.__asadmin.request.count4xx-count = 0
server.http-service.__asadmin.request.errorCount = 0
server.http-service.server.request.count503-count = 0
server.http-service.server.request.count3xx-count = 0
server.http-service.server.request.count401-count = 0
server.http-service.myvs1.request.requestCount = 0
server.http-service.server.request.processingTime = NaN
server.http-service.myvs1.request.count304-count = 0
server.http-service.myvs1.request.count404-count = 0
server.applications.hello.server.requestCount = 159
server.http-service.__asadmin.request.count404-count = 0
server.http-service.server.request.count304-count = 0


abbagani added a comment - 23/Sep/08 04:13 PM

Looking into the problem


kumara added a comment - 24/Sep/08 01:38 AM

Not a must have for Prelude release.


Nazrul added a comment - 15/Oct/08 12:43 AM

Release note that user will need to restart the server to see virtual server
changes in monitoring tier.


kumara added a comment - 24/Oct/08 07:23 PM

Prashanth: Please be sure get this recorded in the release note. Exclude from the prelude release.


kumara added a comment - 24/Oct/08 08:14 PM

Reclassifying as P4 because these issues are not must fix for prelude release.
This issue will be scrubbed after prelude release and will be given the right
priority for v3 final release.


Gail Risdal added a comment - 08/Dec/09 06:51 PM

Added to v3 Release Notes.


Tom Mueller added a comment - 06/Jan/11 11:55 AM

User is no longer on the project. Reassigning to default assignee for monitoring.


Byron Nevins added a comment - 07/Feb/11 01:00 PM

Jennifer - can you verify that this still exists?

I'm setting it to 3.2 so it doesn't get lost...


Jennifer Chou added a comment - 07/Feb/11 02:55 PM

This issue still exists in 3.1. It's now called Network Listeners, instead of HTTP Listeners.
Turn on monitoring for http-service.