search

eclipse-ee4j / glassfish

Eclipse GlassFish
https://eclipse-ee4j.github.io/glassfish/
386 stars 144 forks source link

[Blocking] no monitoring stats is displayed for clustered instance #14382

Closed glassfishrobot closed 13 years ago

glassfishrobot commented 14 years ago

Steps:

Note: When the same app is deployed on DAS - monitoring on DAS does work. Using B26 Promoted.

Environment

Operating System: All Platform: Sun

Affected Versions

[3.1_dev]

glassfishrobot commented 6 years ago
glassfishrobot commented 14 years ago

@glassfishrobot Commented hvilekar said: This may not be just GUI specific issue.

1. I'm unable to see monitoring data through REST API: http://localhost:4848/monitoring/domain/in1/

2. The CLI also doesn't return the app name when the app is deployed on cluster.

On standalone instance, where EJB is deployed with no "--target" specified, I see the EJB listed ( OrbFailOver-ejb) through CLI:

2.1. DAS only:

asadmin list -m server.applications.*

server.applications.OrbFailOver-ejb server.applications.OrbFailOver-ejb.LocationBean server.applications.OrbFailOver-ejb.LocationBean.bean-methods server.applications.OrbFailOver-ejb.LocationBean.bean-methods.getHostName server.applications.OrbFailOver-ejb.LocationBean.bean-methods.getLocation server.applications.OrbFailOver-ejb.LocationBean.bean-methods.printSystemProperties server.applications.OrbFailOver-ejb.LocationBean.bean-pool server.applications.admingui server.applications.admingui.asadmin server.applications.admingui.asadmin.FacesServlet server.applications.admingui.asadmin.ThemeServlet server.applications.admingui.asadmin.default server.applications.admingui.asadmin.jMaki XmlHttpProxy Servlet server.applications.admingui.asadmin.jsp server.applications.default-web-module server.applications.default-web-module.server server.applications.default-web-module.server.default server.applications.__default-web-module.server.jsp

Command list executed successfully.

When the same EJB is deployed on the cluster setup - "asadmin deploy --target c1" - I don't see the EJB listed.

2.2. Three instance cluster setup:

asadmin> list -m server.applications.*

server.applications.admingui server.applications.admingui.asadmin server.applications.admingui.asadmin.FacesServlet server.applications.admingui.asadmin.ThemeServlet server.applications.admingui.asadmin.default server.applications.admingui.asadmin.jMaki XmlHttpProxy Servlet server.applications.admingui.asadmin.jsp server.applications.default-web-module server.applications.default-web-module.server server.applications.default-web-module.server.default server.applications.__default-web-module.server.jsp

Command list executed successfully.

No OrbFailOver-ejb is listed in #2.2 above.

glassfishrobot commented 14 years ago

@glassfishrobot Commented anilam said: Can you see the stats using CLI ? If you cannot see that either , then thats not a GUI issue. Can you give it a try ? thanks

glassfishrobot commented 14 years ago

@glassfishrobot Commented anilam said: Can you see the stats using CLI ? If you cannot see that either , then thats not a GUI issue. Can you give it a try ? thanks

glassfishrobot commented 14 years ago

@glassfishrobot Commented anilam said: Something is not quite right with issue tracker. I didn't see the 2nd comment from Harshad, and when i add mine, it appears as 2 comments. Anyway, thanks for checking the result using CLI and REST. I am reassigning to the 'monitoring'. If thats not the correct subcomponent, please reassign.

glassfishrobot commented 14 years ago

@glassfishrobot Commented bnevins said: Attach the file you mentioned please. OrbFailOver-ejb.jar

glassfishrobot commented 14 years ago

@glassfishrobot Commented hvilekar said: Created an attachment (id=5324) OrbFailOver-ejb.jar

glassfishrobot commented 14 years ago

@glassfishrobot Commented hvilekar said: Attached OrbFailOver-ejb.jar

glassfishrobot commented 14 years ago

@glassfishrobot Commented bnevins said: Under Steps in the very first comment i ASSUME that you started the Cluster after creating it. Why do I have to assume? Why not post ALL of the steps?

glassfishrobot commented 14 years ago

@glassfishrobot Commented bnevins said: Created an attachment (id=5334) screen dump of the monitoring data for locationbean

glassfishrobot commented 14 years ago

@glassfishrobot Commented bnevins said: I repeated and it worked fine. I attached a screen dump that shows the monitoring data for an instance in the cluster.

Here are the ACTUAL commands I ran, copied from the terminal:

C:\apps>asadmin get -m "*"

C:\apps>asadmin list-clusters Nothing to list Command list-clusters executed successfully.

C:\apps>asadmin create-cluster c1 Command create-cluster executed successfully.

C:\apps>asadmin create-local-instance --cluster c1 i1 Rendezvoused with DAS on localhost:4848. Port Assignments for server instance i1: JMX_SYSTEM_CONNECTOR_PORT=28686 JMS_PROVIDER_PORT=27676 HTTP_LISTENER_PORT=28080 ASADMIN_LISTENER_PORT=24848 JAVA_DEBUGGER_PORT=29009 IIOP_SSL_LISTENER_PORT=23820 IIOP_LISTENER_PORT=23700 OSGI_SHELL_TELNET_PORT=26666 HTTP_SSL_LISTENER_PORT=28181 IIOP_SSL_MUTUALAUTH_PORT=23920 Command create-local-instance executed successfully.

C:\apps>asadmin deploy --target c1 /apps/OrbFailOver-ejb.jar Application deployed with name OrbFailOver-ejb. WARNING : Instance i1 seems to be offline; Command was not replicated to that instance Command deploy completed with warnings.

C:\apps>asadmin start-cluster c1 Command start-cluster executed successfully.

C:\apps>asadmin list-application-refs c1 OrbFailOver-ejb Command list-application-refs executed successfully.

glassfishrobot commented 14 years ago

@glassfishrobot Commented hvilekar said: I followed exact same steps on my machine (Solaris 10, X64), with 3.1 build 27, and still see the blank monitoring screen (attached). Steps pasted from my Console. Screen shot attached. I see you have Server set to "localhost", whereas, I have actual host name. Call me if you need more details. Thanks.

==================== csh% unzip /java/re/glassfish/3.1/promoted/latest/archive/bundles/latest-ogs.zip

Archive: /java/re/glassfish/3.1/promoted/latest/archive/bundles/latest-ogs.zip creating: glassfish3/ :

csh% asadmin version Version string could not be obtained from Server [localhost:4848] for some reason. (Turn debugging on e.g. by setting AS_DEBUG=true in your environment, to see the details). Using locally retrieved version string from version class. Version = Oracle GlassFish Server 3.1 (build 27) Command version executed successfully. csh% asadmin start-domain Waiting for domain1 to start ................... Successfully started the domain : domain1 domain Location: /net/quickmind.us.oracle.com/export/install/gf31/glassfish3/glassfish/domains/domain1 Log File: /net/quickmind.us.oracle.com/export/install/gf31/glassfish3/glassfish/domains/domain1/logs/server.log Admin Port: 4848 Command start-domain executed successfully. csh% asadmin get -m "*" WARNING : Instance instance1 seems to be offline; Command was not replicated to that instance Command get executed successfully. csh% asadmin list-clusters Nothing to list Command list-clusters executed successfully. csh% asadmin create-cluster c1 Command create-cluster executed successfully. csh% asadmin create-local-instance --cluster c1 i1 Using DAS host localhost and port 4848 from existing das.properties for node localhost. To use a different DAS, create a new node using create-node-ssh or create-node-config. Create the instance with the new node and correct host and port: asadmin --host das_host --port das_port create-local-instance --node node_name instance_name. Ignoring unrecognized element schedules at Line number = 48 Column number = 18 System Id = file:/net/quickmind.us.oracle.com/export/install/gf31/glassfish3/glassfish/nodes/localhost/i1/config/domain.xmlPublic Id = null Location Uri= file:/net/quickmind.us.oracle.com/export/install/gf31/glassfish3/glassfish/nodes/localhost/i1/config/domain.xml CharacterOffset = 2792

Ignoring unrecognized element backup-configs at Line number = 53 Column number = 23 System Id = file:/net/quickmind.us.oracle.com/export/install/gf31/glassfish3/glassfish/nodes/localhost/i1/config/domain.xmlPublic Id = null Location Uri= file:/net/quickmind.us.oracle.com/export/install/gf31/glassfish3/glassfish/nodes/localhost/i1/config/domain.xml CharacterOffset = 3001

Rendezvoused with DAS on localhost:4848. Port Assignments for server instance i1: JMX_SYSTEM_CONNECTOR_PORT=28687 JMS_PROVIDER_PORT=27677 HTTP_LISTENER_PORT=28081 ASADMIN_LISTENER_PORT=24849 JAVA_DEBUGGER_PORT=29010 IIOP_SSL_LISTENER_PORT=23821 IIOP_LISTENER_PORT=23701 OSGI_SHELL_TELNET_PORT=26667 HTTP_SSL_LISTENER_PORT=28182 IIOP_SSL_MUTUALAUTH_PORT=23921 Command create-local-instance executed successfully. csh% asadmin deploy --target c1 /apps/OrbFailOver-ejb.jar org.glassfish.api.admin.CommandException: remote failure: A supplemental command failed; cannot proceed further /apps/OrbFailOver-ejb.jar Command deploy failed. csh% asadmin deploy --target c1 ~/tmp/OrbFailOver-ejb.jar Application deployed with name OrbFailOver-ejb. WARNING : Instance i1 seems to be offline; Command was not replicated to that instance Command deploy completed with warnings. csh% asadmin start-cluster c1 Command start-cluster executed successfully. csh% asadmin list-application-refs c1 OrbFailOver-ejb Command list-application-refs executed successfully

====================

On Admin Console, Configurations Menu:

Set Monitoring Level to HIGH for c1-config, instance1-config, server-config (click Save in each case)

glassfishrobot commented 14 years ago

@glassfishrobot Commented hvilekar said: Created an attachment (id=5341) Monitoring screen shot on qm2.us.oracle.com

glassfishrobot commented 14 years ago

@glassfishrobot Commented hvilekar said: Update: Monitoring data started showing up after the instance is restarted: asadmin stop-local-instance i1 ; asadmin start-local-instance i1.

glassfishrobot commented 14 years ago

@glassfishrobot Commented jc129909 said: I have an older workspace (~Nov 1?) where I can see the Monitoring page and reproduce the problem. It looks like the monitoring framework is not receiving the property change event when changing the module monitoring level of a cluster config through the Admin Console. The events do get received when using asadmin. The workaround is to use asadmin to change the levels. There's no need to restart the server.

asadmin set configs.config.c1-config.monitoring-service.module-monitoring-levels.ejb-container=HIGH

glassfishrobot commented 14 years ago

@glassfishrobot Commented hvilekar said: Fix is needed - hence reopening the issue. Removed [Blocking] Tag - workaround is available.

glassfishrobot commented 13 years ago

@glassfishrobot Commented jc129909 said: Created a new bug which describes the real problem is when using REST (Console also is using REST) and closing this one as DUP so it's less confusing: https://glassfish.dev.java.net/issues/show_bug.cgi?id=14460

glassfishrobot commented 13 years ago

@glassfishrobot Commented hvilekar said: Now that 14460 is fixed, clustered instance monitoring data is displayed by REST: http://hostname.us.oracle.com:4848/monitoring/domain/in2/applications/OrbFailOver-ejb/LocationBean

Still, no data is displayed on Admin Console. See description for steps.

Cluster - c1 - in2 - monitoring. All three tabs (Application, Server, Resources) display blank.

Tested 3.1 b35 nightly.

glassfishrobot commented 13 years ago

@glassfishrobot Commented anilam said: Jennifer last looked at this issue. Request her to take a look again.

glassfishrobot commented 13 years ago

@glassfishrobot Commented jc129909 said: The issue is in the Admin Console. Looks like the monitoring REST url is not formed properly in MonitoringHandlers.java getInstanceMonitorURL.

There seems to be an extra '/server' at the end of the URL. monitorURL = "http://"nodeHost":"+ port + "/monitoring/domain/" + instanceName +"/server";

Also, looks like you can get the data through DAS itself - no need to go to the instance directly like above. And going to the instance directly may not work when secure is enabled and authentication is required.

http://localhost:4848/monitoring/domain/in1

glassfishrobot commented 13 years ago

@glassfishrobot Commented jc129909 said: How bad is its impact? (Severity)

How often does it happen? Will many users see this problem? (Frequency)

How much effort is required to fix it? (Cost)

What is the risk of fixing it and how will the risk be mitigated? (Risk)

glassfishrobot commented 13 years ago

@glassfishrobot Commented ai109478 said: Approved for checkin

glassfishrobot commented 13 years ago

@glassfishrobot Commented anilam said: Code change reviewed, looks good to me. Please go ahead and commit. Thanks for helping out on this.

glassfishrobot commented 13 years ago

@glassfishrobot Commented jc129909 said: Project: glassfish Repository: svn Revision: 44170 Author: jc129909 Date: 2010-12-30 23:50:19 UTC Link:

Log Message:

14382 no monitoring stats is displayed for clustered instance

Fix monitoring url:

Code Reviewer: Anissa Lam Approved by: Nazrul Islam

Revisions:

44170

Modified Paths:

trunk/v3/admingui/common/src/main/java/org/glassfish/admingui/common/handlers/MonitoringHandlers.java

glassfishrobot commented 13 years ago

@glassfishrobot Commented hvilekar said: Verified: 3.1 build41

glassfishrobot commented 14 years ago

@glassfishrobot Commented File: 14382.JPG Attached By: bnevins

glassfishrobot commented 13 years ago

@glassfishrobot Commented File: diff.txt Attached By: jc129909

glassfishrobot commented 14 years ago

@glassfishrobot Commented File: monitoring-blank-screen-shot-qm2.jpg Attached By: hvilekar

glassfishrobot commented 14 years ago

@glassfishrobot Commented File: OrbFailOver-ejb.jar Attached By: hvilekar

glassfishrobot commented 14 years ago

@glassfishrobot Commented Was assigned to jc129909

glassfishrobot commented 7 years ago

@glassfishrobot Commented This issue was imported from java.net JIRA GLASSFISH-14382