[GLASSFISH-7229] java.lang.String entry for JNDI Created: 25/Feb/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: v2.1
Fix Version/s: not determined

Type: Improvement Priority: Blocker
Reporter: lsacco Assignee: Anissa Lam
Resolution: Unresolved Votes: 6
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 7,229

 Description   

Under JNDI custom resources you should have the ability to add a JNDI value for
java.lang.String similar to Tomcat or other JEE containers. This is essential
for us because we use commons-configuration in our application to look for that
value to be DEV, TEST, or PROD and then pick runtime attributes from our
internal config.



 Comments   
Comment by Amy Roh [ 26/Feb/09 ]

...

Comment by Amy Roh [ 26/Feb/09 ]

Can you elaborate? GlassFish already supports java.lang.String entry for JNDI
via Environment entry like tomcat.

<Environment name="..." type="java.lang.String" value="..."/>

Comment by lsacco [ 26/Feb/09 ]

This is what I do in Tomcat:

<Environment name="config/com/xxx/pds/env" override="false"
type="java.lang.String" value="DEV" />

Where in the Admin UI for Glassfish can I set this or do I have to update an XML
file somewhere on the server?

Thanks,
Lou

Comment by Amy Roh [ 26/Feb/09 ]

If you want to define environment entry that will be shared across the server,
you can create global context.xml in
glassfish/domains/domain1/config/context.xml and this will be loaded by all
webapps.

In your global context.xml, you can have the same Tomcat entry

<Environment name="config/com/xxx/pds/env" override="false"
type="java.lang.String" value="DEV" />

Different levels of context.xml support is described in my blog -
http://weblogs.java.net/blog/amyroh/archive/2007/05/context_webapp_1.html

This should suit your need, correct?

Comment by lsacco [ 02/Mar/09 ]

So I decided to do the first one similar to what we do in Tomcat and add this
appropriate entry in the context.xml file as follows:

<Environment name="config/com/xxx/pds/env" override="false"
type="java.lang.String" value="DEV" />

I restart the server, but fail with exception:
9471-4218-a69b-0bfb1400f1b8;|WebModule[/PCNRequestApprovalWeb]PWC1275: Exception
sending context initialized event to listener instance of class

This is the offending code (I assume I just need to remove java:comp/env for the
context look-up):

try {
InitialContext ctx = new InitialContext();
String env = (String)ctx.lookup("config/com/qualcomm/pds/env");
String config = "sm-security-config.xml";
if ("local".equalsIgnoreCase(env))

{ config = "local-security-config.xml"; }

configs.add(PREFIX + config);

} catch (NamingException ne)

{ throw new ApplicationContextException(ne.getMessage()); }

Also, when I browse the JNDI tree from the admin console I do not see this entry
in the tree. Any suggestions?

Comment by lsacco [ 03/Mar/09 ]

FYI...there's workarounds for this (the blog post didn't work) but I feel that
you should be able to set a String property from the admin console as a String
and have it bound to the JNDI tree. This is a request for enhancement to that end.

Comment by Amy Roh [ 03/Mar/09 ]

Yes, I agree that you should be able to edit environment entry using the admin
console. I believe admin gui folks are working on this already. Assigning the
enhancement request to admin gui team.

Comment by Amy Roh [ 03/Mar/09 ]

Assign the enhancement request to admin gui team.

Comment by athrawn17 [ 09/Mar/09 ]

Just wanted to link back to the forum discussion.

http://forums.java.net/jive/message.jspa?messageID=334354#334354

Comment by freddio [ 06/Apr/09 ]
      • Issue 7229 has been confirmed by votes. ***
Comment by kumara [ 01/Sep/09 ]

Changing version from 9.1.1 to v2.1 to reflect new name/version.

Comment by teenow [ 10/May/11 ]

Close this issue when done.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-4181] gfv3: OEM Pluggability: GUI Created: 15/Feb/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: New Feature Priority: Blocker
Reporter: msreddy Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 4,181
Status Whiteboard:

v3-prd-item


 Description   

This is a GUI pluggability dependent issue for the umbrella issue# 4176.

Provide necessary API so that the OEM modules can expose their configuration and
management thru GUI similar to application server modules.



 Comments   
Comment by msreddy [ 15/Feb/08 ]

this is a P1 reqt ...

Comment by msreddy [ 26/Feb/08 ]

v3-prd-item

Comment by Anissa Lam [ 28/Feb/08 ]

This is AdminConsole-012 in
http://wiki.glassfish.java.net/Wiki.jsp?page=V3AdminConsoleImprovements

Administration console should be extensible

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-16536] provide infrastructure to display progress bar in admin console Created: 03/May/11  Updated: 17/Oct/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: None
Fix Version/s: future release

Type: New Feature Priority: Blocker
Reporter: Anissa Lam Assignee: Jason Lee
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
depends on GLASSFISH-12033 DYREC-007: progress status implementa... Resolved
Tags: ee7ri_cleanup_deferred

 Description   

This is one of the requirement for 3.2 GUI. We need this to display status to user when setting up VM template or long deployment process.



 Comments   
Comment by Tom Mueller [ 17/Oct/12 ]

Marking the fix version field as "future-release". This is based on an evaluation by John, Michael, and Tom WRT to the PRD for the Java EE 7 RI/SDK. This issues was deemed to not be a P1 for that release. If this is in error or there are other reasons why this RFE should be targeted for the Java EE 7 RI/SDK release, then change the fix version field back to an appropriate build.





[GLASSFISH-7094] web administration ui for log configuration and viewing Created: 27/Jan/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: New Feature Priority: Critical
Reporter: kawazu Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 7,094

 Description   

Glassfish V2 web administration user interface used to have a fairly powerful
tooling for doing log level configuration and viewing / searching log files. In
current GFv3 builds, this features don't seem to be available. Having them
around in GFv2 seems crucial in my opinion as dealing with logging and log files
is everyday work in most environments and having the application server
administration ui easily supporting this, so, seems a sane and important thing.
Eventually this should include extended configurability of log levels and files
(see https://glassfish.dev.java.net/issues/show_bug.cgi?id=5683 ).



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5577] need to move appserver and registration node to plugin Created: 21/Aug/08  Updated: 11/Feb/13

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: future release

Type: Task Priority: Critical
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Macintosh


Issuezilla Id: 5,577

 Description   

In order that Admin Console can be used as 'basic, empty' shell so that other
group can develop a plugin and use the Admin console as their own console, GF
admin console should implement every function as a plugin.
The following tree node:
Application Server, registration needs to be moved to a plugin.
the doc. set in the common task page should be in a plug in as well.



 Comments   
Comment by kumara [ 24/Aug/08 ]

Change to status whiteboard for v3 bug tracking

Comment by Anissa Lam [ 29/Aug/08 ]

This should be a Task, not defect.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5453] decorate static data with links to edit pages Created: 09/Aug/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1peur2
Fix Version/s: not determined

Type: Improvement Priority: Critical
Reporter: vince kraemer Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 5,453

 Description   

In http://forums.java.net/jive/thread.jspa?threadID=45320&tstart=0 the user
suggested that it would be nice to have a link from the value of Ports,
displayed on the General page to the actual page the allows you to edit the value.

I am sure there are other static text "fields" in the Admin Console that
represent data that is editable on a different page in the GUI. So this is a
general enhancement request.



 Comments   
Comment by Anissa Lam [ 09/Aug/08 ]

thanks for filing this.
Will look in this for v3 final.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5418] Need better notification mechanism for important events Created: 01/Aug/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Critical
Reporter: Nazrul Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 5,418

 Description   

Currently, we have a bottom frame in admin gui that allows us to share
information with the GlassFish users. This does not always get noticed by the
users. We need a better mechanism where we could notify users with important
events. For example, when GlassFish has a new release, it may be useful to have
a "popup" (with something like "Tell me More" | "Ignore" | "Remind me Later")
that shows up as soon as one hits the admin page. Integration with advertisement
server may be considered for this as the information source.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5157] Add ability for user to identify deployment plan during deployment Created: 14/Jun/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Critical
Reporter: Tim Quinn Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Macintosh


Issue Links:
Duplicate
is duplicated by GLASSFISH-1363 Easy updation to runtime behaviour (... Resolved
Issuezilla Id: 5,157

 Description   

Java EE apps allow users to place vendor-specific descriptors into a deployment
plan with portable bits remaining in the application archive.

The v3 back-end now supports deployment plans. It would be a nice addition if
the GUI allowed users to choose a deployment plan archive to deploy along with
the main archive.



 Comments   
Comment by Anissa Lam [ 19/Aug/08 ]

This is nice to have feature.
A very basic support in GUI means just add a text box for user to specify the
deployment plan. Since GUI now uploads the app from client side to server side
if needed, we will do the upload of this plan as well.
For better experience, a file chooser should be presented so user can browse and
select the jar instead of having to type in the path.

Will look at this for v3 final.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5683] allow for adding custom logging handlers through the admin ui Created: 27/Aug/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Critical
Reporter: kawazu Assignee: Anissa Lam
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Linux


Issuezilla Id: 5,683

 Description   

So far, glassfish does offer a decent tooling for managing log levels and
reading log files through the web administration console. However some use cases
demands aren't met by these features:

  • In some situations, I am about to do debugging / tracing of exceptions
    across applications. In these situations, so far I use the gf web
    administration to raise the log level for packages / classes in question to
    non-production logging levels ("INFO" to "FINEST"). This generates bunches
    of output, which by then I have to cut off server.log, eventually strip out
    logging output dumped by classes not related to the problem, and hope in the
    end not to have missed anything. For these cases, I would like to, say, set
    up a "temporary" logger set to dump all its output to a
    "trace-<timestamp>.log" log file, set all the packages / classes I would
    want to monitor for that to dump their output to that very logger, get done
    what I need to do to reproduce the error, switch the classes logging back to
    the "normal" output and examine the "trace-<timestamp>.log" either online
    using the web administration console or scp'ing to some other machine,
    knowing it will just contain the output I wanted to catch.
  • In other situations, I would like to set up logging for cross-application
    issues (access to user data, in example) to go to a central logging file
    (say, "useraccess.log"). As I would on the fly select which packages should
    considered worth logging there, this should be something to be configurable
    at runtime.
  • Ideally, all these settings should be possible to accomplish by a
    designated "glassfish administrator" who has only access to the gf web
    administration panel but not to the machine glassfish is running on (no ssh
    login, no console access, ...). This generally leaves dealing with
    logging.properties out of the way here.
  • Likewise, I would like to have these settings in a consistent environment
    to ease maintaineance - the logging configuration should be backed up doing
    "asadmin backup-domain" and recovered the same way. And, there should be one
    place to do these settings, most favorably the glassfish administration
    console where by now there already is some of these stuff to be set up
    (logging levels) - I would prefer not having to explain to admins/devs to do
    "one half" of these configurations in glassfish web console and "the other
    half" using some text editor on logging.properties.

Overally, having the glassfish v3 web administration enhanced to allow for

  • configuration of arbitrary logging handlers to dump output to custom log files
    readable through the web administration console, and
  • asides from logging level having these handlers assigned to pre-defined or
    custom classes, packages or modules in the application server

greatly would help here.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5680] Visualize cluster health Created: 27/Aug/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: v2.1
Fix Version/s: not determined

Type: Improvement Priority: Critical
Reporter: barz26 Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 5,680

 Description   

Currently it is really hard to find out if a cluster using in memory replication
is operational or not. With that I mean:

  • No hints are given in the admin gui if the selected multicast address is
    working correctly
  • The replication scheme (which instance is replication partner of which other
    instance) is not visible at all

This RFE asks for:

  • an integrated multicast tester using the configured multicast heartbeat
    address for the GMS/availability service
  • a status display for the GMS and in memory replication
  • an ability to influence the replication scheme - meaning if I have a 4 node
    cluster with instance 1&2 on one box and 3&4 on the next box I want to avoid
    that 2 is replication partner of 1.


 Comments   
Comment by kumara [ 01/Sep/09 ]

Changing version from 9.1.1 to v2.1 to reflect new name/version.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-12541] config->JVM Settings ->General TAB Created: 06/Jul/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: not determined

Type: New Feature Priority: Critical
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Dependency
depends on GLASSFISH-12418 convert all property table related ha... Resolved
Issuezilla Id: 12,541

 Description   

Need to finishing up property table conversion



 Comments   
Comment by Anissa Lam [ 06/Jul/10 ]

MS3

Comment by Anissa Lam [ 24/Jul/10 ]

MS4

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-10644] Need to provide WebService Tester and wsdl link Created: 28/Oct/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: New Feature Priority: Critical
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 10,644

 Description   

Currently, we don't show the sub components of any module down to the servlet or
JSP level. We should provide the info the same as in CLI list-sub-component
command.

If the Servlet is a webservice, we also need to provide a tester link and allow
user to view the wsdl file if possible.



 Comments   
Comment by Nazrul [ 28/Oct/09 ]

Changing the issue type to FEATURE.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-543] add field fields to 'Configuration->Http Service: Access Log tab' Created: 05/Apr/06  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.0pe
Fix Version/s: not determined

Type: Improvement Priority: Critical
Reporter: vince kraemer Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: Text File OLH-http-service.tiff    
Issuezilla Id: 543

 Description   

See issue 541.

This seems like a good place to put fields to manipulate the accessLogBufferSize
and accessLogWriteInterval.

Folks want to manipulate these values, and they aren't available easily.



 Comments   
Comment by Anissa Lam [ 21/Feb/07 ]

I am ready to add this.
But i need input from Jan and JF whether this should be exposed to user as a
text field. In order word, do we prefer to hide this from user ?
If presenting this as a text field, what should be the default value for these 2
fields.
Please provide a one-sentence help to be put on the page for this field.

Comment by vince kraemer [ 11/Jul/07 ]

did this ever get commited?

Comment by Anissa Lam [ 11/Jul/07 ]

Sorry, this was put behind while waiting for the input from Jan & JF.
so, the answer is no.

Comment by vince kraemer [ 11/Jul/07 ]

Ok. one more thing for v3...

Comment by Anissa Lam [ 24/Jul/07 ]

Kedar also request the following. (refer to issue#3398)

provide a "check-box" at both the http-service config page and virtual-server
config page? It is not a good idea to make users key-in or delete the property
elements.

Anissa, I would request you to provide a check-box for these elements. The
internals remain the same. Checked => setProperty("accessLoggingEnabled", "true")
and Unchecked => setProperty("accessLoggingEnabled", "false") and vice versa.

Comment by jluehe [ 24/Jul/07 ]

accessLogBufferSize:
The access log buffer size (in bytes). A value <=0 disables buffering. Default: 4096

accessLogWriteInterval:
The interval (in seconds) between writing (updating) the access log. A value <=0
disables buffering. Default: 0

Comment by Anissa Lam [ 29/Jul/07 ]

The OLH of admin gui gives some default of the properties which doesn't match
with what Jan mentioned in previous comment.
Jan, if you press the 'Help' button on the upper right corner when looking at
the Http Service page, you will see that, please review it.
In case you don't have the GUI up, i have attached that table.
I have open up an issue for OLH change, it is issue# 3447.
You may want to update that issue instead to ensure the help content is correct.

Comment by Anissa Lam [ 29/Jul/07 ]

Created an attachment (id=1069)
OLH property table

Comment by jluehe [ 30/Jul/07 ]

Hi Anissa, the default values I mentioned are hard-coded in the code (more
specifically, in com.sun.enterprise.web.PEAccessLogValve in appserv-core), as
opposed to being exposed as default property values in domain.xml.

(This goes all the way back to a comment I made to June Parks, when I suggested
that we distinguish between default values and default settings in the admin
guides.)

So, if access logging has been disabled, any values for "accessLogBufferSize" or
"accessLogWriteInterval", whether they be hard-coded or specified as properties
in domain.xml, will be ignored.

However, once you enable access logging, and don't specify any
"accessLogBufferSize" or "accessLogWriteInterval" properties, the default values
I mentioned will be picked up.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-517] Always deconnected when using two GF Created: 31/Mar/06  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.0pe
Fix Version/s: not determined

Type: Improvement Priority: Critical
Reporter: bjb Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 517

 Description   

Say you got a domain running on your machine and you got a SSH to a server
running glassfish as well. You would have :

http://localhost:4848/
--> local admin

http://localhost:48/
--> SSH'ed access to the remote admin

The problem is that accessing one admin log out the other (and vice versa).
Workaound is to reauthenticate on each new request, this is working but very
painfull.

I am anticipating this has to do with the domain cookie ...

Fixing this would allow us to have a production remote monitoring and
development testing at the same time that is quite usual for today's applications.



 Comments   
Comment by Anissa Lam [ 31/Mar/06 ]

I believe this is a browser issue. If you can try this using 2 IE browser, you
will see that both domain can be accessed without logging ecah other out.
The problem exists in Netscape 7.1 on, but not 7.0
Mozilla 1.4/1.5 will have the same problem.

When you login to admin gui, the browser stores these cookies : JSESSIONID and
JSESSIONIDSSO.
In Netscape 7.1, the site for the cookie is stored as just the
hostname, but not the port number. In Netscape 7.0.2 the site name contains port
number as well. Hence this problem is seen in Netscape 7.1 onward but not on 7.0.2.

Cookies are not identified by port number by Mozilla/Netscape intentionally -
Following bugs have been filed on Mozilla asking for a change to this behaviour.
http://bugzilla.mozilla.org/show_bug.cgi?id=189784
http://bugzilla.mozilla.org/show_bug.cgi?id=227475
However, these bugs are not being fixed.

The following comments describe the decision of not storing port number :
http://bugzilla.mozilla.org/show_bug.cgi?id=142803#c28

Also look at http://sillydog.org/forum/viewtopic.php?t=6746

To work around this problem, try accessing by
http://localhost:4848
and
http://<IP-address>:48

Will continue to see how admin gui can fix this, marked as enhancement for now.

Comment by bjb [ 31/Mar/06 ]

It is having the same begaviour with IE7 latest beta as well on 2 tab.
I think other IE version should behave the same (I am stuck to IE latest beta at
this time and can not test on another IE version).

Tnx for the work around (localhost vs 127.0.0.1) it worked.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-1418] JSF: Enlarge Log level properties edit field Created: 03/Nov/06  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Critical
Reporter: phenderson Assignee: anac
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,418

 Description   

Please make the edit box for log level property name longer

On the admin web interface
Application Server->Logging->Log Levels

The space available to specify Additional Module Log Level Properties is way too
small.

For example.
Field contents
com.starjar.starjarenterprise5.domain.ContactListViewDAO

But only
com.starjar.starjarenterpri
is visible.

Also, should the value field really be a combo box of the various log levels?
(FINEST, FINE, ....., SEVERE)

Peter Henderson.



 Comments   
Comment by Anissa Lam [ 03/Nov/06 ]

change Summary to ensure this will be addressed in the JSF version of admin-gui.

Comment by Anissa Lam [ 09/Feb/07 ]

This should be fixed for 9.1 fcs for usability.
Raise Priority,

Comment by anac [ 09/Feb/07 ]

Need to extend the property field name.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-1129] Container should run IBM JDBC drivers in Type 4 instead of Type 2 Created: 11/Sep/06  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.0peur1
Fix Version/s: not determined

Type: Improvement Priority: Critical
Reporter: jdavidson Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,129

 Description   

The IBM jdbc drivers can be run in Type 2 (native) or Type 4 (pure Java). By
default, Type 2 seems to be used.

Type 2 is much more restrictive, since native libraries are required. Different
libraries are used for each platform, and certain platforms (e.g., MacOS) appear
not to be supported at all.

The IBM drivers are the only ones that are supported in Type 2.

Unless there are additional mitigating factors, the drivers should be used in
Type 4 by default.



 Comments   
Comment by lancea [ 20/Mar/07 ]

The problem with the type 4 driver is that it does not support XA.

However, that being said, the DataSource should be one of the following
(universal driver) and not com.ibm.db2.jdbc.DB2DataSource:

  • com.ibm.db2.jcc.DB2SimpleDataSource
  • com.ibm.db2.jcc.DB2DataSource
  • com.ibm.db2.jcc.DB2ConnectionPoolDataSource
  • com.ibm.db2.jcc.DB2XADataSource

The driverType property should also be specified and either defaulted to 2 or 4

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-4311] provide role based access control Created: 28/Feb/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Critical
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Dependency
depends on GLASSFISH-4312 provide role-based access control (RB... Open
Issuezilla Id: 4,311
Status Whiteboard:

v3-prd-item


 Description   

AdminConsole-025 in
http://wiki.glassfish.java.net/Wiki.jsp?page=V3AdminConsoleImprovements

Description:
Fine grained access control and configurable roles.



 Comments   
Comment by Anissa Lam [ 28/Feb/08 ]

add keyword and dependency.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-4305] standby msg when app is down for maintence Created: 28/Feb/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Critical
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Dependency
depends on GLASSFISH-4306 GUI needs help in placing a 'stand by... Open
Issuezilla Id: 4,305
Status Whiteboard:

as-prd-item


 Description   

This is AdminConsole-015 in
http://wiki.glassfish.java.net/Wiki.jsp?page=V3AdminConsoleImprovements

Placement of a configurable (with default) "stand by" message when an
application is down for maintenance or is in the process of being re-deployed



 Comments   
Comment by Anissa Lam [ 28/Feb/08 ]

add dependency and keyworod

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-4303] provide a link to file issue/enhancement Created: 28/Feb/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Critical
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 4,303
Status Whiteboard:

v3-prd-item


 Description   

This is AdminConsole-007 in
http://wiki.glassfish.java.net/Wiki.jsp?page=V3AdminConsoleImprovements

Provide a link to file a bug/enhancement on the product.

GUI is going to add such a link in common task page.



 Comments   
Comment by Anissa Lam [ 28/Feb/08 ]

change to 'enhancement' and add v3-prd-item keyword.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-3948] Treat JDBC and JNDI resources enablement the same Created: 27/Dec/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1peur1
Fix Version/s: not determined

Type: Improvement Priority: Critical
Reporter: Alexis MP Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 3,948

 Description   

Using the "cluster" profile, JDBC resources created on the DAS are enabled for
all instances while JNDI resources need to be explicitly enabled for a given set
of instances (at creation time or after). This doesn't sound right.

Either all resources should be enabled on all instances by default, or the
choice should be given to the user for both JDBC and JNDI resources as to which
instances are targets for those resources.

New users are left wondering why their JNDI resources are not enabled on their
cluster instances while JDBC pools are working fine.



 Comments   
Comment by Alexis MP [ 12/Jun/08 ]

Another user reporting this same issue.
Changing RFE to P2

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-3897] Download JDBC drivers when creating a connection pool Created: 05/Dec/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: New Feature Priority: Critical
Reporter: jpz Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 3,897

 Description   

When creating a JDBC connection pool, it would be great to:

  • automatically download the opensource JDBC drivers into the domain, or
  • provide a URL for the proprietary ones and be able to upload them.

Geronimo has a similar feature in the corresponding wizard.



 Comments   
Comment by Anissa Lam [ 09/Aug/08 ]

will consider this for V3.

Comment by Anissa Lam [ 27/Aug/08 ]

Change to Feature and up the priority.

Comment by Jason Lee [ 29/Aug/08 ]

cc'ing myself

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-3726] Resource Mapping enhancement Created: 04/Oct/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Critical
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 3,726

 Description   

This is requested by granat in the following thread:
http://forums.java.net/jive/thread.jspa?messageID=238409
ACTION: Feedback and Lessons learned for Glassfish v2

Resource Mapping:
----------------------------
The biggest problem I have right now is the fact that the mapping of the
resources, roles, etc cannot be done dynamically in the console. There are two
part to that.

  • At Deploy time: In IBM WS, It is very easy to see what an application need
    when deploying in the GUI because there is a part in the deployment wizard that
    ask for the mapping (giving the default mapping but giving the deployer the
    opportunity to change it). This is relevant for the resources if the scheme
    employed in the production is not the same as the one used in Test/Integration
    (security reason). It is especially useful for mapping the security roles to
    ldap (or other) concrete user container.
  • At Run time: Changing the mappings of installed applications is not something
    that is done a lot and we do it only for testing or fail-over scenarios, but
    when you have to do it, it's VERY cool to be able to do it in the GUI.

I know everything can be done before by editing the ear deployment descriptor
files. It's just a lot more convenient to be able to do it through the GUI.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-2378] Move the Additional Properties table "up" Created: 09/Feb/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Critical
Reporter: vince kraemer Assignee: locolobo
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Mac OS X
Platform: Macintosh


Issuezilla Id: 2,378

 Description   

I have a large screen (1200 pixel vertical) and the Additional Properties table
on the Create JDBC Connection Pool second page is below the bottom of my browser
window.

Since this table has some very important data for a user to verify/correct/enter
making it very visible would make the UX better.

See http://forums.java.net/jive/thread.jspa?messageID=202910&#202910 for an
example of the confusion that people may experience.

Is this the root cause of that confusion? Probably not. Does it contribute to
it? probably..



 Comments   
Comment by Anissa Lam [ 09/Feb/07 ]

I will have our HIE person to think about this. However, we are very restricted
by UIRB about layout.

Comment by locolobo [ 09/Feb/07 ]

Thanks - I will look into this.

Comment by vince kraemer [ 09/Feb/07 ]

added ...

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-16348] Support JVM-specific JVM options in console Created: 12/Apr/11  Updated: 19/Oct/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: None
Fix Version/s: future release

Type: New Feature Priority: Critical
Reporter: Tom Mueller Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
depends on GLASSFISH-16247 Improve support for JVM-specific JVM ... Open

 Description   

This is a companion RFE to issue GLASSFISH-16247 for implementing support for JVM-specific JVM options in the admin console.



 Comments   
Comment by Anissa Lam [ 19/Oct/12 ]

The backend support that this issue is depending on has been targeted for future release. So, console will have to target the same.





[GLASSFISH-16881] allow upgrading and removing packages from Admin Console Created: 20/Jun/11  Updated: 17/Oct/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: future release

Type: Improvement Priority: Critical
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: ee7ri_cleanup_deferred

 Description   

In 3.1, user is not allowed to upgrade or remove any package from Admin Console. They can only add additional packages.
The update tool java API has now the capability of just downloading the packages but not install the packages. With this capability, it is possible for the console to allow user to upgrade any existing packages.

Although it will be nice to add this feature for 3.1.1, discussion with Joe and Chris concludes that this feature should not be rushed to 3.1.1. But should be considered for the "next" release.
Reason being there is not enough testing yet, and adding this when soft code freeze is less than 4 days away is too risky. There will also be impact to documentation, QA and maybe localization.

So, this enhancement will be targeted for after 3.1.1 release.



 Comments   
Comment by Tom Mueller [ 17/Oct/12 ]

Marking the fix version field as "future-release". This is based on an evaluation by John, Michael, and Tom WRT to the PRD for the Java EE 7 RI/SDK. This issues was deemed to not be a P1 for that release. If this is in error or there are other reasons why this RFE should be targeted for the Java EE 7 RI/SDK release, then change the fix version field back to an appropriate build.





[GLASSFISH-17839] Applications page performance issues related to large number of deployments. Created: 28/Nov/11  Updated: 17/Oct/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1.1
Fix Version/s: future release

Type: Improvement Priority: Critical
Reporter: Anissa Lam Assignee: sirajg
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: ee7ri_cleanup_deferred

 Description   

This was brought up in the forum discussion: http://forums.java.net/node/867604
However, the following discussion in the email wasn't captured in the forum.

=========================
On 11/24/2011 05:56 PM, Anissa Lam wrote:
> Hi Bernhard,
> On 11/24/11 3:51 AM, Bernhard Thalmayr wrote:
>> A 'DAS' (domain administration server) corresponsds to one 'domain'
>>
>> The applications will be deployed into the domain repository (hosted
>> by the 'DAS') and an application reference will exist for every
>> instance the application should be available.
>>
>> The admin-console you become somewhat messy (nearly unusable) if you
>> have 100 web-apps deployed (you may need to use the CLI instead).
>>
> Can you elaborate on the above statement ? Is it performance, UI, layout
> of pages or workflow that makes you feel that way ? We strive to improve
> user experience on the console and your feedback and suggestion will be
> greatly appreciated.

Thanks for your attention Anissa.

For every application deployed the console tries to determine the state f it on every server. This can take a very long time.

You just get the hint 'long running process detected' (or similar).

Currently I have about 25 application deployed and IMHO it's already almost usable. Personally I don't mind to much because I'm using the CLI anyway, but the developers are always using the console and they are complaining a lot.

Although I'm using GF 3.1.1 I still have issues with 'running out of file handles' due to REST-calls not cleaning up the sockets correctly - similar (http://java.net/jira/browse/GLASSFISH-16672). This error is very nasty and makes the console almost unusable if you can not tweak the FD limits at the OS level.
(Of course I set the 'linger' stuff ... but this does not help at all)

Regards,
Bernhard

=================
Think this is probably due to the time for detecting the enabled status or each application and its application-ref.
May need to asynchronously update the status when they are available, instead of waiting for everything before displaying the page.



 Comments   
Comment by Anissa Lam [ 28/Nov/11 ]

target version set to 4.0 for now. Will try our best to address this in 3.1.2.

Comment by Tom Mueller [ 17/Oct/12 ]

Marking the fix version field as "future-release". This is based on an evaluation by John, Michael, and Tom WRT to the PRD for the Java EE 7 RI/SDK. This issues was deemed to not be a P1 for that release. If this is in error or there are other reasons why this RFE should be targeted for the Java EE 7 RI/SDK release, then change the fix version field back to an appropriate build.





[GLASSFISH-20993] cannot login into admin console using multi-level CA certificate Created: 24/Feb/14  Updated: 21/Aug/14

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 4.0
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: ChristianSch Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

GF generates a self-signed certificate and console works fine, but if you use a real certificate you cannot login anymore
"Authentication Failed! re-enter username and password"

A lot of CA have the following structure

  • Root Certificate
  • Issuing Certificate
  • Server Certificate

The Client (e.g. web-browser) usually only has the Root-Cert and
the server announces the remaining chain (server+issuing) during during SSL handshake
if you use such a setup for DAS, login to the AdminConsole is no longer possible

Steps to reproduce
1. create multi-level CA, for example http://pages.cs.wisc.edu/~zmiller/ca-howto/
2. import root cert into truststore.jks
3. import server-chain into keystore.jks
for example
3a. create chain.pem: cat servercert.pem issuingcert.pem > chain.pem
3b. create p12: openssl pkcs12 -export -in chain.pem -inkey serverkey.pem -out server.p12 -name p12-alias
3c. keytool -importkeystore -destkeystore keystore.jks -destalias s1as -srckeystore server.p12 -srcstoretype PKCS12 -alias p12-alias
4. enable secure admin and test console with self-signed certs
5. configure server-config/JVM options to use keystore.jks and truststore.jks; restart



 Comments   
Comment by ChristianSch [ 24/Feb/14 ]

only access to Admin Console is rejected.
Access to /management/domain is still possible.

Comment by ChristianSch [ 21/Aug/14 ]

according to new evidence this issue is most likely not related to the type of certificates used.

the certificates (from my internal CA) in my keystore have different owner attribute and this owner is not configured as secure-admin-principal. If I add the owner as secure-admin-principal the logging works. I don't want to add additional secure-admin-principals because I'm using secure-admin-internal-user.
so at the moment it looks as if 2-way-ssl is used between AdminConsole / GF-core and admin-internal-user is not working.
A similar setup used to work for GFv3





[GLASSFISH-19735] [PERF] Page to page navigation has slowed down and showing the long process popup Created: 27/Feb/13  Updated: 11/Sep/14

Status: In Progress
Project: glassfish
Component/s: admin_gui
Affects Version/s: 4.0_b77
Fix Version/s: future release

Type: Task Priority: Critical
Reporter: Anissa Lam Assignee: Jason Lee
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: devx_web

 Description   

I notice that starting about a week or 2 ago, the admin console page to page navigation has slowed down significantly. Very often, the 'long process is detected' popup also shows up.
The doc team also reports the same observation.

There isn't a particular way to reproduce the issue. But if you use the console by clicking around, creating or deleting some objects, you will for sure notice the poor performance.
I see this on my Mac and the issue shows up in all 3 browsers (chrome, firefox and safari) , so don't think this is a browser issue.



 Comments   
Comment by Jason Lee [ 28/Feb/13 ]

I think this is a performance regression in Jersey. Here are some rough timings taken from revisions before and after the latest integration:

r59530
GET http://localhost:4848/common/appServer/serverInstGeneralPe.jsf?instanceName=server&bare=true 200 OK 1.1s
GET http://localhost:4848/cluster/standalone/standaloneInstances.jsf?bare=true 200 OK 240ms
GET http://localhost:4848/common/appServer/serverInstGeneralPe.jsf?instanceName=server&bare=true 200 OK 855m
GET http://localhost:4848/cluster/cluster/clusters.jsf?bare=true 200 OK 259m
GET http://localhost:4848/common/appServer/serverInstGeneralPe.jsf?instanceName=server&bare=true 200 OK 875m

r59545 <- This is the 2.0m12-1 integration
GET http://localhost:4848/common/appServer/serverInstGeneralPe.jsf?instanceName=server&bare=true 200 OK 2.28s
GET http://localhost:4848/cluster/standalone/standaloneInstances.jsf?bare=true 200 OK 1.72s
GET http://localhost:4848/common/appServer/serverInstGeneralPe.jsf?instanceName=server&bare=true 200 OK 2.61s
GET http://localhost:4848/cluster/cluster/clusters.jsf?bare=true 200 OK 1.04s
GET http://localhost:4848/common/appServer/serverInstGeneralPe.jsf?instanceName=server&bare=true 200 OK 2.11s

I'll email the Jersey team to get their take.

Comment by Jason Lee [ 05/Mar/13 ]

The numbers listed above were pretty rough, page-level timings; that is, how long it takes from the click of the mouse to the response from the server. I added some logging on the server side that measures ONLY the Jersey calls (i.e., target.request()). Prior to the integration, here are the timings we see for requests on a single page:

r59530:

***** GET request for http://localhost:4848/management/domain/servers/server/server finished in 31 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/uptime finished in 8 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/servers/server/server finished in 24 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/configs/config/server-config/network-config/network-listeners/network-listener finished in 37 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/configs/config/server-config/network-config/network-listeners/network-listener finished in 36 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/configs/config/server-config/network-config/network-listeners/network-listener/admin-listener.json finished in 42 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/configs/config/server-config/network-config/network-listeners/network-listener/http-listener-1.json finished in 53 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/configs/config/server-config/network-config/network-listeners/network-listener/http-listener-2.json finished in 41 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/servers/server/server finished in 23 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/configs/config/server-config/iiop-service/iiop-listener finished in 31 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/configs/config/server-config/iiop-service/iiop-listener finished in 31 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/configs/config/server-config/iiop-service/iiop-listener/SSL.json finished in 37 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/configs/config/server-config/iiop-service/iiop-listener/SSL_MUTUALAUTH.json finished in 37 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/configs/config/server-config/iiop-service/iiop-listener/orb-listener-1.json finished in 44 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/_get-restart-required finished in 7 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/anonymous-user-enabled finished in 10 milliseconds|#]

After the integration, this is what we see for the exact same page:

r59545:

***** GET request for http://localhost:4848/management/domain/servers/server/server finished in 82 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/uptime finished in 29 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/servers/server/server finished in 70 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/configs/config/server-config/network-config/network-listeners/network-listener finished in 135 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/configs/config/server-config/network-config/network-listeners/network-listener finished in 123 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/configs/config/server-config/network-config/network-listeners/network-listener/admin-listener.json finished in 140 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/configs/config/server-config/network-config/network-listeners/network-listener/http-listener-1.json finished in 181 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/configs/config/server-config/network-config/network-listeners/network-listener/http-listener-2.json finished in 143 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/servers/server/server finished in 76 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/configs/config/server-config/iiop-service/iiop-listener finished in 114 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/configs/config/server-config/iiop-service/iiop-listener finished in 103 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/configs/config/server-config/iiop-service/iiop-listener/SSL.json finished in 125 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/configs/config/server-config/iiop-service/iiop-listener/SSL_MUTUALAUTH.json finished in 138 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/configs/config/server-config/iiop-service/iiop-listener/orb-listener-1.json finished in 185 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/_get-restart-required finished in 32 milliseconds|#]
***** GET request for http://localhost:4848/management/domain/anonymous-user-enabled finished in 44 milliseconds|#]

For reference, here are the lines of code in question:

long start = System.currentTimeMillis();
Response resp = target
    .request(RESPONSE_TYPE)
    .cookie(new Cookie(REST_TOKEN_COOKIE, getRestToken()))
    .get(Response.class);
GuiUtil.getLogger().log(Level.INFO, "\n\n***** GET request for {1} finished in {0} milliseconds", 
    new Object[] {
        (System.currentTimeMillis() - start), 
        address
    });

That's about as slimmed down, Jersey-only as you can get, and clearly after the integration, things get slower. If there are no objections, I will transfer this issue to the Jersey team (or perhaps file an issue on their tracker for this).

Comment by Jakub Podlesak [ 05/Mar/13 ]

I am not 100 % sure about the measurement method above, but the fact we do not have Jersey client side covered by performance tests is awful.
Please feel free to file a task in the Jersey JIRA to cover client side performance testing. Once implemented, we should be able to get some numbers also for previous Jersey releases and compare.

Comment by Jason Lee [ 05/Mar/13 ]

It is a pretty simple measure, but we get a pretty accurate timing, I think, on the processing time for the client request. At any rate, I have filed a task for the client-side performance testing coverage: http://java.net/jira/browse/JERSEY-1767

How quickly do you think this will be addressed? The performance in the console is raising eyebrows. Can we use the older version of the client in the meantime?

Comment by Jakub Podlesak [ 08/Mar/13 ]

To better understand where the regression is, it would be useful to have some numbers also with using a non Jersey client (e.g. curl) for the above tests.
Given that http://localhost:4848/management/domain application does not use Jersey client internally, of course.

Jason, would you have some cycles for it?

Comment by Anissa Lam [ 09/Apr/13 ]

I see that the performance has improved some after I filed this issue, although it still hasn't got back to the same level of performance like in 3.1.2.
There is lots of discussions regarding this, and i don't think Jason is planning to do anything specifically to address this issues in the console code.
I am changing this to Task and target that for the next release to see what console can do to improve the paga to page navigation.

One thing i notice is that, when refreshing the tree node, even though we called the ajax to just refresh a particular node, eg. Applications, the entire tree is refreshed, thus sending lots of requests to the backend to update the tree. We may want to look into why this is happening. But since its done asynchronously, the main page on the left isn't really waiting for the tree to completely refreshed before displaying the right side, thus not directly impacted by this whole tree update.

I am changing this to Task and target that for the next release to see what console can do to improve the paga to page navigation.





[GLASSFISH-19209] Add console support for WebSocket for EE7 Created: 22/Oct/12  Updated: 19/Sep/14

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: None
Fix Version/s: 4.1

Type: New Feature Priority: Critical
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
depends on GLASSFISH-19520 provide an API for listing web socket... Open
depends on GLASSFISH-19521 provide API for listing the mappings... Open

 Description   

WebSocket is added in EE7, console will need to provide support for configuration relating to websocket.
Waiting for more info from web socket team.



 Comments   
Comment by Anissa Lam [ 11/Jan/13 ]

Currently, a war that has web socket inside them works exactly as any other webapp in the console, ie, it can be deployed, listing the jsp/servlet, dd, etc.

The Web Socket team would like to have more information to the user for a web socket app, just like the endpoints details thats displayed for a JAXWS app.
To do this, the following 2 RFE from the web socket team needs to be available for console's consumption.

GLASSFISH-19520 provide an API for listing web socket applications
GLASSFISH-19521 provide API for listing the mappings between the classname and URI.

Comment by Anissa Lam [ 16/Jan/13 ]

Since both RFEs that the console is depending on is now targeted for 4.0.1, this console RFE is changing to reflect that.





[GLASSFISH-18594] jsftemplating optionally depend on dataprovider packages Created: 04/Apr/12  Updated: 23/Apr/15

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1.2
Fix Version/s: future release

Type: Bug Priority: Critical
Reporter: Sanjeeb Sahoo Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: javaee_ri_target, spo

 Description   

jsftemplating has badly setup its OSGi metadata. Although it requires dataprovider packages,
it optionally imports them. So, it breaks any kind of automatic deployment that does not deploy optional modules. This should be fixed. When you do fix this issue, please remove the dead module called appserver/admingui/jsftemplating because jsftemplating is built in a separate workspace called https://svn.java.net/svn/jsftemplating~svn/trunk



 Comments   
Comment by TangYong [ 22/Jun/12 ]

Dear Anissa,Sahoo,

In the current gfv4 trunk, appserver\admingui\jsftemplating still exists, and in admingui's pom.xml,
the jsftemplating module is not put in build process. So, the appserver\admingui\jsftemplating is indeedly
a dead module. It should be removed from appserver\admingui.





[GLASSFISH-4419] prefill redeploy data page Created: 13/Mar/08  Updated: 23/Apr/15

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Critical
Reporter: vince kraemer Assignee: mukesh.kumawat
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 4,419
Tags: javaee_ri_target

 Description   

Consider the following situation:

The user has directory deployed a module or app.

When they click the Redeploy link, they are brought to a page that asks them to
enter the path of the object that they want to redeploy...

In the 90% case, the data that the user will enter is the same data that they
entered on the page that they used to deploy the module or app.... AND that same
data is stored in the domain.xml (so the admin gui has access to it).

It would be nice to prefill the entry field with the data that we already have
that is almost surely going to be correct.

Another choice would be to have the Redeploy link skip asking the user to enter
and/or confirm data in the situation where the object is directory deployed..
That change is not as nice to users that may need to change the value of the
directory, since they would need to undeploy A and then deploy A-prime....



 Comments   
Comment by Jason Lee [ 12/Jan/09 ]

Changing target version

Comment by Jason Lee [ 12/Jan/09 ]

Updating version

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-6937] Editing default-web.xml via Administration UI Created: 16/Dec/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1peur2
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: klichong Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 6,937

 Description   

One performance recommendation involves editing of the default-web.xml so that
the changes apply to all deployed applications. Users should have the
capability to edit the default-web.xml via the admin UI instead of editing this
file directly.



 Comments   
Comment by Jason Lee [ 12/Jan/09 ]

Updating version

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-6829] Admin GUI needs to allow config JRuby based frameworks (Rails, Merb...) Created: 21/Nov/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: New Feature Priority: Major
Reporter: vivekp Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Linux


Issuezilla Id: 6,829

 Description   

GlassFish v3 is capable of running Ruby based frameworks, such as Rails, Merb,
Campsite etc. With GlassFish v3 Prelude Rails support is available and currently
Merb and other are in works.

Admin Gui needs to support admin and configuration of jruby based frameworks.



 Comments   
Comment by vivekp [ 21/Nov/08 ]
      • Issue 6768 has been marked as a duplicate of this issue. ***
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-6727] admin console: provide details of asadmin deployment Created: 06/Nov/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: New Feature Priority: Major
Reporter: suedonne123 Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Linux


Issuezilla Id: 6,727

 Description   

Is there some way in glassfish admin console to find the equivalent "asadmin"
command details to accomplish the same task you are doing in the admin console?

I am not familiar with the internals of glassfish, but is there a way to either:

1) print in log files what the asadmin config settings would be when
"Save"/configuration change is done in admin console. I am not sure how Sun has
coded the webapp admin console but I was hoping that they are using "asadmin"
behind the scenes and this would be available via logging or some such fairly
easily in this case.

2) even better would be to have a "Show ASADMIN" button alongside the "Save"
button that would show popup with asadmin details (make this tunable, default
could be off...)



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-6119] provide status during update components Created: 15/Sep/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: yifeng1 Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Windows XP
Platform: PC


Issuezilla Id: 6,119

 Description   

b24

donwload add-ons componments takes a lot of time. For example, within swan, it
took about 6-7 mins to download jruby and Grails. It will be a nice-to-have
feature to implement a pop up window, which indicates the download status.



 Comments   
Comment by Kim Haase [ 06/Aug/09 ]

I'm wondering if this shouldn't be considered a bug. When I install jruby, the
download appears to have completed within a few minutes (fewer than 6), but the
success message does not appear until 9 minutes after I began the installation.

I'm within Swan too, and in the same country but 3000 miles from where I am
guessing the bundles are stored.

If I get impatient and hit the Back button in my browser before I get the
success message, I generally find that the installation has in fact completed –
jruby is no longer shown as an available add-on, and it is in the Installed
Components list. When I use it, everything works.

So what is causing the apparent hang? If it cannot be fixed, users need to be
warned to be patient.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-6117] be able to unable listener from the admin like jk-connector Created: 15/Sep/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: survivant Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 6,117

 Description   

Jeanfrancois Arcand wrote:

Salut,

Kedar Mhaswade wrote:

I hope the name has no bearing here, but I am not sure. I should be able
to name the JK connector as "foo", right JF?

We don't have any way to tell GF that a specific connector is mod_jk
enabled. Hence Amy cames with the idea (or Jan?) to have a special name. For
sure jdk-connector is not correct It should be jk-connector.

Now using the name attribute might not be a good idea. I would instead
propose adding a property under <http-listener> with:

<property name="jkSupport" value="true"/>

so it follow our normal convention. Jan/Amy/Kedar, what do you think?

I am fine with this. Maybe you should file an RFE on the admin console
plugin to provide a check-box which says: < > Is this a JK Connector?
Please document this if you intend to do it.

This will make adding a JK connector easier and user does not have to
remember the property name in its case.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-6095] value not validated for customize deployment descriptor Created: 12/Sep/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: yifeng1 Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Windows XP
Platform: PC


Issuezilla Id: 6,095
Status Whiteboard:

gfv3-prelude-included


 Description   

b24 IE7

it has been observed that customized value field is not getting validated. For
example, if the env-entry-type is java.lang.Integer, user can actually overwrite
with a string. when it is java.lang.Boolean, I can overwrite with Integer value.

To reproduce:

1. applications-->web applications
deploy webapps-simple.war

2. after deployment, go to descriptor tab and enter value, you will see those
values are not validated.

not sure if it is a bug, but
1. the text field should be validated based on env-entry-type
2. if not implemented, will be a nice to have RFE



 Comments   
Comment by yifeng1 [ 12/Sep/08 ]

add cc

Comment by Anissa Lam [ 12/Sep/08 ]

When implementing this feature, its understood that GUI will not do any client
side validation because there may be different env-entry-type.
I think the deployment end should validate the value and reject it by throwing
an exception. GUI will be able to display this error to user and they can fix it.
I don't know if type mismatch will result in failure when loading the
application. If thats the case, deployment should definitely validate the value
before saving.

Comment by kumara [ 12/Sep/08 ]

v3 defect tracking

Comment by Tim Quinn [ 13/Sep/08 ]

The valid env-entry-type values are

  • java.lang.Boolean
  • java.lang.Byte
  • java.lang.Character
  • java.lang.Double
  • java.lang.Float
  • java.lang.Integer
  • java.lang.Long
  • java.lang.Short
  • java.lang.String

The server must do its own validation anyway because users could edit the
customized config manually, outside of the admin console. This is not yet in
place in the server but will be added as part of the changes to how we record
the customized application config.

Even so, the user experience would be better if the console also validated the
env-entry-value using the corresponding env-entry-type.

Comment by Tim Quinn [ 15/Sep/08 ]

Part of my recent check-in for app management takes care of server-side
validation of env-entry-value against the env-entry-type. Note that the
WebAppliation class will log warnings about these problems to server.log but
will not abort a deployment or a load operation.

As Anissa pointed out earlier, in the absence of GUI validation a user could
deploy the app, then customize the app config in a way that will not pass the
validation, then redeploy the app. The deployment will not fail.

I implemented the validation logic on the EnvEntry admin/config-api interface
itself (a method on an inner class defined on the interface) so it would be
available to both the server and the GUI plug-in.

Comment by Tim Quinn [ 15/Sep/08 ]

I am shifting this to the admin_gui component because the server-side validation
is now in place.

Comment by Anissa Lam [ 15/Sep/08 ]

Marking client side validation as enhancement since server is doing the validation.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-7154] Allow testing Web Services that take objects as parameters Created: 08/Feb/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: agoncal Assignee: Anissa Lam
Resolution: Unresolved Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 7,154

 Description   

Testing a webservice with the admin console (by clicking on the test button)
works fine if the webservice takes basic java types as parameters. But when you
have a WS that takes objects, that doesn't work. It would be good to be able to
pass SOAP requests like SOAPUI, or maybe integrate SOAP UI directly in the admin
console.

http://markmail.org/thread/nevp6qgn6lu3qcei



 Comments   
Comment by gdx [ 25/Mar/09 ]
      • Issue 7154 has been confirmed by votes. ***
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-7116] Title of login page Created: 02/Feb/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1peur2
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: dobes Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 7,116

 Description   

It would be great if the login page for the admin application would have a more
specific title than just "Login". For example "Glassfish Login" or something.

This would allow me to use KeePass to auto-type the password.



 Comments   
Comment by km [ 02/Feb/09 ]

...

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-7110] 3.0-b04 contains fix: OLH add info regarding JavaMail Session properties Created: 30/Jan/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Dependency
depends on GLASSFISH-7107 JavaMail Session - Additional propert... Resolved
Issuezilla Id: 7,110

 Description   

We should add the info regarding the behavior of properties set for JavaMail
Resource.

As described in the developer's manual:
http://docs.sun.com/app/docs/doc/819-3672/beaoz?a=view

"Every property name must start with a mail- prefix. The Application Server
changes the dash character to a period (.) in the name of the property and
saves the property to the MailConfiguration and JavaMail Session objects."

refer to issue# 7107 for more details.

For inline help, maybe we should add this to the page help.



 Comments   
Comment by Paul Davies [ 25/Feb/09 ]

Reassigned to owner of OLH. If issue 7107 is fixed, this issue should be
resolved as wither INVALID or WONTFIX.

Comment by Kim Haase [ 27/Mar/09 ]

No indication that 7107 is being fixed, so accepting for V3.

Comment by Kim Haase [ 05/Oct/09 ]

Fixed in OLH, though not in builds yet.

Comment by Kim Haase [ 21/Oct/09 ]

Fix published in build 3.0-b04 to the Maven repository at:
http://download.java.net/maven/glassfish/org/glassfish/admingui/

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-6588] we should implement delete profiler Created: 20/Oct/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: yifeng1 Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 6,588

 Description   

from admin console, we can only add profiler, but not delete it. It will be nice
to implement this in console.

BTW, CLI command has create-profiler as well as delete-profiler command.



 Comments   
Comment by yifeng1 [ 20/Oct/08 ]

change priority so that it will be investigated in next planning cycle.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-6508] EclipseLink clustering configuration with Glassfish Created: 11/Oct/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: New Feature Priority: Major
Reporter: ijuma Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 6,508

 Description   

Hi,

EclipseLink supports cache coordination through JMS (recommended for the general
case), RMI or CORBA allowing it to be clustered across many machines. Since
Glassfish v3 will include EclipseLink as the JPA 2.0 implementation and it
supports clustering, it would be interesting to explore ways to provide a more
integrated configuration experience.

As an example, for the JMS case one needs to create a topic and a connection
factory in OpenMQ and then configure EclipseLink to use these. It would be nicer
if one could just select a checkbox when creating a cluster and have this done
automatically with decent defaults.

The documentation for cache coordination is here:

http://wiki.eclipse.org/Introduction_to_Cache_(ELUG)#Cache_Coordination

I am not sure if I selected the right Subcomponent, so please change it if not.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5653] view domain.xml from admin console Created: 26/Aug/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: New Feature Priority: Major
Reporter: chilak Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 5,653

 Description   

Request for the domain.xml to be viewed from the admin console - a read-only
version of the file. Skimming thro' the domain.xml is much easier sometimes than
navigating thro' the menus.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5395] Display EJBs contained inside an EAR in console Created: 29/Jul/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1peur2
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: ib93gass Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: GIF File netbeans_ear.gif    
Issuezilla Id: 5,395

 Description   

Today, it is possible to see which EJBs are contained within an EAR (enterprise
application) in two ways.

1. Use the Jndi Browser that the console provide.
Go to the Application Server node, there is the button thats labeled JNDI
browser. Press this button will popup the browser. You can then expand the
tree and look for he beans under ejb node.

2. look at the Deployment Descriptor file
To do this, go to the descriptor tab of the deployed application. It
will show the sub-component of the ear. Then there is the link of the DD file.
Just click on that and it will show you the DD file. So you can examine the
file to see the beans.

Problem is, both options are not very intuitive and user friendly.

the NetBeans 6 Glassfish Plugin provides an easy and intuitive display. Please
add something similar to the Glassfish console.



 Comments   
Comment by ib93gass [ 29/Jul/08 ]

Created an attachment (id=1626)
Expanded EAR node in NetBeans showing EJBs within EAR

Comment by Anissa Lam [ 29/Jul/08 ]

We will need the deployment backend to provide the list of Beans in the jar.
CC'ing Hong and Tim on this.
for now, i just leave this in the admingui category until i actually work on this.

Comment by Alexis MP [ 29/Jul/08 ]

Adding myself to CC list

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5314] Admin console doesn't handle large numbers of pools and administrative resources well Created: 16/Jul/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: v2.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: fkieviet Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 5,314

 Description   

When GlassFish is used for integration applications, we typically end up with
over a hundred different connection pools, and hundreds of JMS destinations
bound in JNDI. The UI displays pools and admin objects in lists, which doesn't
scale well wrt usability.

For JNDI, a hierarchical view would increase usability.

The pools might need to be removed from the tree-view on the left of the screen
altogether, and a larger list box with search capabilities might need to be
added on the screen on the right.



 Comments   
Comment by harpreet [ 04/Sep/08 ]

Marking target milestone as 9.1.1

Comment by Anissa Lam [ 16/Oct/08 ]

This is an RFE. Marking as such.

Comment by kumara [ 01/Sep/09 ]

Changing version from 9.1.1 to v2.1 to reflect new name/version.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5216] Show state of beans Created: 26/Jun/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1peur1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: mkarg Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 5,216

 Description   

Currently I just can see whether a bean was part of an EJB-JAR. But I cannot see
the deployment problems that could have been occured. Example: Sometimes it
happens that a @Resource was not bound correctly, so I have to go to server.log.

It woule be great if there would be a green check mark for "deployed OK" or a
red cross for "not deployed" / yellow warning sign for "deployed, but with
warnings". Then I click on the symbol and get well-formatted information on the
error / warnings that happened.

This is very useful in development.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5215] Content of modules shall be listed even when modules is part of EAR Created: 26/Jun/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1peur1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: mkarg Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 5,215

 Description   

Currently the admin gui lists the content of standalone modules. I can see all
beans found in an EJB-JAR.

But when the module is not standalone but instead part of an EAR, I cannot see
the beans found in an EJB-JAR.

My proposal is that it shall make no difference whether a module is standalone
or not. I want to be able to see the content of an EJB-JAR, even when it is part
of an EAR.

That is sometimes necessary in developing situations, where you need to assure
that a bean was correctly deployed, but you cannot deploy it standalone since it
needs utility libraries from the EAR.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5070] Provide PREV / NEXT Buttons in log detail view Created: 28/May/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1peur1
Fix Version/s: not determined

Type: New Feature Priority: Major
Reporter: mkarg Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 5,070

 Description   

The admin gui lists all log entries in tabulary form, with only brief message
text. If the admin wants to see the complete message text, he must select one
log entry and press "(details)". Another window will open showing the details of
the log entry with verbose message text. There is only one button: CLOSE.

Often it is the case that there is a row of messages to read, so the admin has
to manually open and close that log entry details. This is very annoying.

For efficient work, it would be very beneficial to have not only a CLOSE button
on the details window, but also a set of PREV and NEXT buttons. With those
buttons, the admins could step through the log entries within the details view.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5863] Monitoring/Managing Of Multpile Non-Clustered Instances From One Console Created: 04/Sep/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: New Feature Priority: Major
Reporter: abien Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: other
Platform: All


Issuezilla Id: 5,863

 Description   

Server: GF V3

I had multiple requests from my clients, whether it is possible to manage
independent, non-clustered instances from one admin console. This was especially
true for highly available applications. In that particular case it was required
to deploy and test different versions of the same modules (EJB-JARs, WARs), shut
them down and start again, into different instances.

Further the applications weren't evenly distributed. Some modules were
singletons and were only deployed to one specific node. In some cases we build
our own communication infrastructure (hessian based).

Managing independent instances from one admin console would fit well into the
dynamic / OSGI nature of Glassfish.

We discussed the topic during the JavaONE 08 as well. It seems to be a common need.



 Comments   
Comment by ijuma [ 19/Oct/08 ]

Adding myself to cc list.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5842] Lack Of JNDI Browser In Admin UI Created: 03/Sep/08  Updated: 17/Apr/14

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: future release

Type: New Feature Priority: Major
Reporter: abien Assignee: andriy.zhdanov
Resolution: Unresolved Votes: 23
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified
Environment:

Operating System: other
Platform: All


Sub-Tasks:
Key
Summary
Type
Status
Assignee
GLASSFISH-17928 OLH for Jndi Browser Sub-task Open Paul Davies  
Issuezilla Id: 5,842

 Description   

Server: GF v3 b22

GF v2 (and actually all other application servers like JBoss or WLS) come with a
visual JNDI browser. This is essential for debugging pursposes - even for
operations.

I would expect to have at least rudimentary functionality to dump the JNDI tree
from the admin UI.

Porting already existing functionality from GF v2 would be fine as well -
although it thrown from time to time exceptions .



 Comments   
Comment by Anissa Lam [ 03/Sep/08 ]

yes, this is on our to-do list for v3 final. Up the priority to ensure that.

Comment by Anissa Lam [ 28/Oct/09 ]

Sorry that even though we do have want to provide this feature for v3, we are
not able to get to this for this release.
We will look into this for v3.1.
thanks

Comment by Tom Mueller [ 27/Jul/10 ]
      • Issue 11793 has been marked as a duplicate of this issue. ***
Comment by Anissa Lam [ 04/Nov/11 ]

Suma, please give estimate of how long it will take to implement this feature. Want to see if this can be fit into 3.1.2 schedule.

Comment by Anissa Lam [ 18/Nov/11 ]

Requesting help from Andriy.

Comment by andriy.zhdanov [ 08/Dec/11 ]

Committed revision 51362 - draft

Comment by Rebecca Parks [ 12/Dec/11 ]

Will there be DHQA for this? Or has there already been one? Do you know which build will have this in it?

Comment by Rebecca Parks [ 13/Dec/11 ]

Just heard from Mike Fitch that this is deferred, changing fix version to future release.

Comment by Anissa Lam [ 14/Dec/11 ]

We missed this feature for 3.1.2. Target this for 4.0

Comment by Anissa Lam [ 09/Jan/13 ]

retarget to after 4.0

Comment by TangYong [ 23/Aug/13 ]

Hi Anissa,

Whether this feature has been in process?

For an ejb with multi-interfaces view, once deploying it, some portable JNDI names(not only one jndi name) will be created by container.

So, for an developer, we'd better browser these names for debugging and etc.by using admin gui.

Pl. let me know whether you are doing or we can help.

Thanks
Tang

Comment by Anissa Lam [ 23/Aug/13 ]

Implementing JNDI browser is not in our plan in the near feature. We may look into this in the next major release.

Comment by Rebecca Parks [ 23/Aug/13 ]

I've stopped watching this issue but can't figure out how to remove myself from the Participants list. If someone else knows, how, please remove me.

Comment by kithouna [ 26/Sep/13 ]

Implementing JNDI browser is not in our plan in the near feature. We may look into this in the next major release.

It's still targeted at 4.0.1...

Comment by Anissa Lam [ 17/Apr/14 ]

change fix version from 4.0.1 to future release as this is for new feature.
4.0.1 is a bug fixing release.





[GLASSFISH-6975] Admin console should show deployed web services Created: 28/Dec/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: dwschulze Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 6,975

 Description   

The Admin console should show which web services are deployed and give Endpoint
names and URLs. JBoss 5 has this functionality and it is useful.



 Comments   
Comment by Jason Lee [ 12/Jan/09 ]

Updating version

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-6966] admin-gui should be insulated from JSF (potentially others as well) library changes Created: 22/Dec/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Ryan Lubke Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Linux


Issuezilla Id: 6,966

 Description   

In the past, I've tried to globally replace the default JSF implementation with
MyFaces 1.2.x. Due to bugs in MyFaces, the admin-gui would no longer work.

Another case where this would be useful is for those testing the alpha releases
of Mojarra 2.0.0. There are times where an issue will sneak through in Mojarra
that has a negative impact on the admin-gui.

In either situation, it would be nice of the admin-gui could rely on it's own
JSF library so that changes to the server's library has no impact on the gui's
operation.



 Comments   
Comment by Jason Lee [ 12/Jan/09 ]

Updating version

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5994] When creating new http-listener, bypass ssl configuration page unless new http-listener is security-enabled Created: 08/Sep/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: jluehe Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 5,994

 Description   

When I create a new http-listener, and don't check the security-enabled box, I
am still being put through the ssl configuration page.

The ssl configuration page should be bypassed in this case.



 Comments   
Comment by Anissa Lam [ 08/Sep/08 ]

good suggestion.
As this is the same in V2, this is more like an enhancement. changing as such.
We may fix this after we are done with bugs.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-13335] Bring focus to top of page after save for long pages Created: 08/Sep/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: lidiam Assignee: lidiam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 13,335

 Description   

build: glassfish-3.1-b19-09_08_2010.zip

When making changes on pages that are long and need scrolling, there is a Save
button on the bottom. After hitting save, user has to know to scroll to the top
of the page to see the success/failure message. GUI should automatically bring
the focus to the top of page after each save or display message at the bottom as
well. Otherwise, inexperienced user may be hitting Save many times, since it is
not clear if the action took place or not, other than by checking top of the page.



 Comments   
Comment by Anissa Lam [ 05/Oct/10 ]

We will need to do this in case by case basis. There isn't a 'general' way to
do that.
Please specify the page you have the problem. (Better yet, file separate issue
for each page). thanks

Comment by Anissa Lam [ 06/Oct/10 ]

reassign to Lidia for which page this occurs.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-13446] Develop a test for txn recovery Created: 14/Sep/10  Updated: 06/Oct/10

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: future release

Type: Improvement Priority: Major
Reporter: Jason Lee Assignee: Jason Lee
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 13,446
Tags: 3_1-exclude

 Description   

A test needs to be developer that will test the transaction recovery page. For details on how this might be
done, see v2/appserv-tests/devtests/transaction/ee/cli.



 Comments   
Comment by Jason Lee [ 15/Sep/10 ]

-> MS6

Comment by Anissa Lam [ 22/Sep/10 ]

-> jdlee





[GLASSFISH-13897] Deleting a running instance - prompt to stop instance instead of failing Created: 08/Oct/10  Updated: 19/Oct/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: future release

Type: Improvement Priority: Major
Reporter: lidiam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 13,897

 Description   

build: glassfish-3.1-b23-10_07_2010.zip

Currently, when user attempts to delete a running instance, on the Standalone
Server Instances page, the following happens:

1. user selects checkbox next to the instance name
2. user clicks delete
3. user clicks OK on "are you sure" prompt
4. an error message is displayed telling user that instance needs to be stopped
first...

We should not have users go through all these actions just to tell them that
they needed to stop the instance first. We could instead prompt the user asking
if they want to stop instance before deleting (in step 3 above). Perhaps there
is an even better solution to the flow here, not sure.



 Comments   
Comment by Anissa Lam [ 08/Oct/10 ]

It is very clear on the table that the instance they select is running.
I am thinking maybe to always stop the instance before deletion. In v2, i don't
think there is this limitation, ie they can always delete a running instance.

So, in the Title Help, we tell user that all instance will be stopped before
deletion.
And in the confirmation dialog, say something like:
"All selected instance will be stopped first before deletion, do you want to
continue ?"
So they can continue or reject then reselect the instance again.





[GLASSFISH-13663] Resource Adapter Config: change delete to load defaults Created: 28/Sep/10  Updated: 17/Oct/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: future release

Type: Improvement Priority: Major
Reporter: lidiam Assignee: sumasri
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 13,663
Status Whiteboard:

3_1-exclude

Tags: ee7ri_cleanup_deferred

 Description   

build: glassfish-3.1-b22-09_27_2010.zip

It would be nice to have "Load defaults" for a Resource Adapter Config. It
seems that currently to achieve this, user needs to delete a specific config and
then create "a new one" again, specifying the same adapter - it will have all
the defaults in case of the built in jmsra. Thus it would make sense to change
"Delete" button to "Load defaults" button on the edit page. It seems that the
resource config should only be truly deleted, if the adapter is being removed.



 Comments   
Comment by Anissa Lam [ 28/Sep/10 ]

Thanks for the suggestion.

The resource adapter config screen is based on input from the backend team. I
would like Jagadish to comment on this, give suggestion on what should be done.
We may or may not get to this for 3.1

Comment by lidiam [ 28/Sep/10 ]

Please see issue https://glassfish.dev.java.net/issues/show_bug.cgi?id=13659 as
well, as it also needs input from backend team, I think.

Comment by Jagadish [ 28/Sep/10 ]

Yes, this can be an enhancement.
Instead of removing "delete", we can keep it as such and introduce "load
defaults" in the edit page of the resource-adapter-config.

Comment by sumasri [ 07/Oct/10 ]

Added the target milestone.

Comment by sumasri [ 12/Dec/10 ]

As this is an enhancement, transferring it to MS8.

Comment by Anissa Lam [ 12/Dec/10 ]

Only critical bug fix will be allowed for MS8. You have till MS7 code freeze to fix this. If you won't get to that, then mark this for 3.2.

Comment by sumasri [ 13/Dec/10 ]

If we insert load defaults button in resource adapter config edit page, it can happen in any of the below cases.
case 1: If we click on the button, It erases all the existing properties and add jmsra(default) properties. If it happens this way, all existing props will be lost.
case 2: If we click on the button, If one of the default property is removed, What should we do in this case?
case 3: If we click on the button, Only replace the default values if it exists. or add the property if it is not already there.

Discussed with the backend team to work on this. It will take some more time decide on this. As it is an enhancement, transferring it to 3.2.

Comment by Tom Mueller [ 17/Oct/12 ]

Marking the fix version field as "future-release". This is based on an evaluation by John, Michael, and Tom WRT to the PRD for the Java EE 7 RI/SDK. This issues was deemed to not be a P1 for that release. If this is in error or there are other reasons why this RFE should be targeted for the Java EE 7 RI/SDK release, then change the fix version field back to an appropriate build.





[GLASSFISH-12628] Disable buttons on screen during long operation Created: 12/Jul/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: HTML File sample.html    
Issuezilla Id: 12,628

 Description   

When there is a long operation, eg, starting a cluster with many instance,
deploy/upload a large files, we should try to disable other buttons on screen
instead of just disable the one user just pressed.

Ken and Jason briefly looked into this and provide the attached html file as a
way that can be done.
Will still need to style it, provide localized message etc.
This will be a nice enhancement.



 Comments   
Comment by Anissa Lam [ 12/Jul/10 ]

Created an attachment (id=4565)
sample.html

Comment by Anissa Lam [ 12/Jul/10 ]

target ms6.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-13987] [508] The focus is first on OK Or SAVE button in right windows Created: 14/Oct/10  Updated: 22/Feb/13

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: future release

Type: Bug Priority: Major
Reporter: shaline Assignee: andriy.zhdanov
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 13,987
Tags: 3_1-508, 3_1-exclude, 3_1_2-508, 3_1_2-exclude

 Description   

Build Used: GF V3.1 promoted b23.
Browser: Firefox : 3.6

Using the TAB keys, when we navigate to the right window, the Focus is always on
the OK, or the SAVE button first, and then goes to the text fields and others.
Ex: In the New Standalone server instance window the focus is first on the OK,
button, and after entering values to create a new instance,if we hit TAB, the
focus is shifted to main page, and one has to tab all the way through left tree
nodes, to come back to OK button.
Workaround is to use the SHIFT+TAB to go back to OK button after the last field
entry in the right window, but after the last field entry if TAB is pressed
accidentally, then we have to start from beginning, which seems annoying.



 Comments   
Comment by Anissa Lam [ 14/Oct/10 ]

This is not 508 accessibility issue since you are able to get to the button and perform what you want.
Its true that It may be better if you didn't get there as the first item in the page, so, we see this as
usability enhancement. We will look at this as time permits.

Comment by Nazrul [ 11/Nov/10 ]

Changing target milestone from 3.1_ms08 to not determined

Comment by shaline [ 12/Jan/12 ]

I see this issue in all the new features screens of the Admin Console in GF 3.1.2. This is the new VPAT requirement that using keyboards one should be able to navigate sequentially.

1194.21(a): Focus order: If a page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

Comment by sb110099 [ 12/Jan/12 ]

Bumping up this bug to get some attention for 3.1.2.
It seems that this is a hard requirement in new VPAT.

Thanks,
Sudipa

Comment by Anissa Lam [ 12/Jan/12 ]

I change this to BUG from RFE as this seems to be the case according to previous comment.
However bumping this to P2 AFTER HCF does not help. It seems to late to address this for 3.1.2 now.

Comment by Anissa Lam [ 13/Jan/12 ]

Set this back to its original priority. Exclude from 3.1.2 release.
This will be listed in VPAT as open issue.

Comment by sb110099 [ 19/Jan/12 ]

This is just to clarify that 508 testing had to be delayed in 3.1.2 to accommodate the new features that came in much after SCF.
This risk was already discussed .

Comment by andriy.zhdanov [ 24/Jan/12 ]

On some pages buttons are both on top and at bottom (e.g. Domain - Application Configuration), if this is a solution, it can be done the same on all pages.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Comment by Anissa Lam [ 12/Feb/13 ]

Issues need to be addressed before 4.0 HCF (3/25)

Comment by Anissa Lam [ 22/Feb/13 ]

This is regarding the page layout, and its designed that the Save/Cancel buttons be on the upper right corner of the page, before the form that has all the fields.
We won't be able to fix this in this release unless we redesign the entire console page layout, and we are not in a position to do that now.
The team decided to revisit this issue in later release.





[GLASSFISH-9378] Browse button next to JRuby Home in Admin Console Created: 04/Sep/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: arungupta Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Macintosh


Issuezilla Id: 9,378

 Description   

Please add a browse button next to "JRuby Home" in admin console.



 Comments   
Comment by vivekp [ 04/Sep/09 ]

Assigning to admingui team. Since it is a local file system path having a browse
button is logical and helpful.

Comment by Anissa Lam [ 04/Sep/09 ]

This should be an RFE.
For the browse button, I guess you mean server-side browsing, instead of browsing the client machine.

Comment by arungupta [ 04/Sep/09 ]

Yep, enhancement and server-side browsing.

It'll be nice if there is an option to upload a pre-configured JRuby zip as well.

Comment by vivekp [ 04/Sep/09 ]

Thats right. It has to be server side browsing. Can admingui make a
determination that the client and server are running on the same machine and in
that case enable browsing? This can be quite handy during development where both
client and server run on the same machine.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-7646] [SJSU] Enhancement in HTTP Service of Admin GUI Created: 13/Apr/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: ayanshah999 Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Windows Vista
Platform: PC


Issuezilla Id: 7,646

 Description   

In Admin GUI,
1)Go to Configuration>HTTP Service.
2)Go to the connection pool tab.
3)Then, remove all the values OR keep any one value, and then click Save. The
error says that "value: does not represent an Integer".
This doesnt explain where the error is encountered. Instead the name of the
field should be displayed where the value is incorrect or missing.
Browser: Mozilla Firefox
Glassfish Build : 44



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-7370] Refine Page Layout Created: 17/Mar/09  Updated: 07/Dec/10

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: future release

Type: New Feature Priority: Major
Reporter: kenpaulsen Assignee: Jason Lee
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 7,370
Tags: 3_1-exclude

 Description   

The current prototype page layout is not quite there.

  • When the tree slides out of the way, it should be completely out of the way
    (see Google Maps).
  • We should evaluate the masthead to see if we can reduce its size.
  • Evaluate/optimize spacing between panels





[GLASSFISH-8966] 3.0-b04 contains fix: Add support for access-logging of session attributes Created: 31/Jul/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: jluehe Assignee: Anissa Lam
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 8,966

 Description   

See http://forums.java.net/jive/thread.jspa?messageID=358412 for motivation



 Comments   
Comment by jluehe [ 31/Jul/09 ]

Fixed in b58:

Sending
web-glue/src/main/java/com/sun/enterprise/web/accesslog/DefaultAccessLogFormatterImpl.java
Transmitting file data .
Committed revision 29995.

Kim,

I've introduced a new access-log pattern element "%session.<name>%", which will
log the value of the session attribute with name <name>, or
NULL-SESSION-ATTRIBUTE-<name> if the named attribute does
not exist in the session, or NULL-SESSION if no session exists.

Could you please add this info to the online docs? Thanks!

Comment by Kim Haase [ 31/Jul/09 ]

Thanks, I'll add the element to the list.

Comment by Kim Haase [ 05/Oct/09 ]

Fix is in V3 OLH, though not yet in builds.

Comment by Kim Haase [ 21/Oct/09 ]

Fix published in build 3.0-b04 to the Maven repository at:
http://download.java.net/maven/glassfish/org/glassfish/admingui/

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-10770] Physical Destinations Should Be Suggested Created: 03/Nov/09  Updated: 06/Oct/10

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: future release

Type: Improvement Priority: Major
Reporter: abien Assignee: Jason Lee
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: File resource_creation.tiff    
Issuezilla Id: 10,770
Tags: 3_1-exclude

 Description   

Glassfish v3b70:

If you create a new Topic / Queue (New JMS Destination Resource) you have to enter a physical destination
(see screenshot). You have to know the name and copy+paste it into the text box. This is confusing for
new GF users.

Suggestion: a combo box, already populated with existing physical destinations would do a much better
job.



 Comments   
Comment by abien [ 03/Nov/09 ]

Created an attachment (id=3734)
Glassfish v3 b70 admin console screenshot

Comment by Kim Haase [ 03/Nov/09 ]

You don't actually have to specify the name of an existing physical destination.
If you specify one that doesn't exist, JMS creates it on the fly when you first
access the destination resource. Normally, you'll specify a new physical
destination when you create the destination resource.

I have added this information (in brief form) to the inline help (it's already
in the online help).

Comment by abien [ 03/Nov/09 ]

You are right. However then I would pre-fill the physical destination textbox with the JNDI-name of the
logical.

The problem is: the names of logical destinations often look like jms/xyz, what is not possible for
physical. Either the prefix jms/ should be removed, or converted in something like "jms.".

So a combo box with a possibility to enter a new physical destination would be a superb solution .

Comment by Anissa Lam [ 03/Nov/09 ]

-> jdlee

Comment by Jason Lee [ 03/Nov/09 ]

We're past the feature freeze date (with HCF only 6 days away), so will this
have to wait until 3.1.

Comment by Jason Lee [ 18/Aug/10 ]

This should be pretty easy to do. Targeting for MS5.

Comment by Jason Lee [ 09/Sep/10 ]

In theory, this sounded easy, but in practice it's not. A destination resource can target multiple targets,
so creating the list of valid physical destinations isn't as straightforward as I thought it might be. I'm
going to move this to MS6, where i hope I'll have the time to think it through and get it implemented
correctly.

Comment by Jason Lee [ 06/Oct/10 ]

I hate to keep deferring this, but given the massive amount of work that has popped up for MS6, I'm going
to have to.





[GLASSFISH-10709] GUI should inform the user to save the changes Created: 30/Oct/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: sankarpn Assignee: nityad
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: PC


Issuezilla Id: 10,709

 Description   

Under Configuration->Monitoring I select some modules to change the monitoring
level, the change level button is activated and I click the button to change the
levels. But the values are not actually changed in domain.xml it is simply
changed in the GUI screen. The user still needs to hit the save button to
actually save it in domain.xml.

the user needs to be informed to hit the save button otherwise it creates a
impression that the levels are already saved.



 Comments   
Comment by Anissa Lam [ 30/Oct/09 ]

We can add the reminder in the title help, however, this is how all edit pages
work. You need to press the SAVE button to save anything you are editing.

Nazrul has requested the dropdown to be able to change the level without having
to press the 'Change Level' button. Request Nitya to do that.
Same change will apply to the logger level page.

Comment by Anissa Lam [ 30/Oct/09 ]

This isn't a bug, more like enhancement.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-11136] Deploying a EJB with missing jndi does not show a proper error on web admin Created: 22/Nov/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: rjdkolb Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Linux


Attachments: JPEG File deployerror.jpg     Java Archive File testschedule-0.0.1-SNAPSHOT.jar     File testschedule.tgz    
Issuezilla Id: 11,136

 Description   

This may be a known issue.

When deploying a EJB on the admin gui, with a missing database jndi fails to
deploy - This is correct.
A error is not displayed to the user, Type is merely made red.

An error at the top needs to be displayed as well.



 Comments   
Comment by rjdkolb [ 22/Nov/09 ]

Created an attachment (id=3973)
Pic os admin gui after failed deploy

Comment by Anissa Lam [ 22/Nov/09 ]

GUI looks at the deployment status and display that to the user at the top if
that status comes back as unsuccessful.
Is it possible for you to attach your ejb jar ? if not, server.log will help too.

thanks

Comment by rjdkolb [ 22/Nov/09 ]

Created an attachment (id=3974)
example EJB that does not deploy

Comment by rjdkolb [ 22/Nov/09 ]

Created an attachment (id=3975)
example project that does not deploy

Comment by Anissa Lam [ 22/Nov/09 ]

I am running promoted build 73 on my Mac.
If i specify the Type to be "EJB jar", I can deploy the attached
testchedule-0.1.1-SNAPSHOT.jar without problem.

[#|2009-11-22T21:40:21.838-0800|INFO|glassfishv3.0|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=32;_ThreadName=http-thread-pool-4848-(2);|testschedule-0.0.1-SNAPSHOT
was successfully deployed in 5,628 milliseconds.|#]

What do i need to do so that deployment fails ?

I know that if I don't select anything in the Type dropdown, then i will get
the dployerror.jpg as you attached here. Is this what you did ?
Please specify "EJB jar". We have many JS in that page to detect for error, we
will need to add one more to enforce the dropdown is selected with an non-empty
value.
If thats why you are seeing the error, I will mark this as RFE and fix in the
update release.
thanks

Comment by rjdkolb [ 22/Nov/09 ]

> I am running promoted build 73 on my Mac.
> If i specify the Type to be "EJB jar", I can deploy the attached
> testchedule-0.1.1-SNAPSHOT.jar without problem.

yes, you are correct. In build 72 I did not need to specify a type.
On my B73 is deploys when I spec a type, so I think that's why I was confused.

> What do i need to do so that deployment fails ?

There is a testschedule/src/main/resources/META-INF/persistence.xml
Just guessing, but is that not supposed to block the deployment because there is
a missing jdbc JNDI ?
This was the issue I was trying to recreate.

> I know that if I don't select anything in the Type dropdown, then i will get
> the dployerror.jpg as you attached here. Is this what you did ?

Yes, you are correct.

> Please specify "EJB jar". We have many JS in that page to detect for error, we
> will need to add one more to enforce the dropdown is selected with an non-empty
> value.

Ah, ok. I understand

> If thats why you are seeing the error, I will mark this as RFE and fix in the
> update release.

Yes, this is the reason and you can.

regards
Richard

Comment by Anissa Lam [ 22/Nov/09 ]

Thanks for clarifying.
I just tried b72, GUI is showing the exact same behavior.
You need to specify 'Type', otherwise, GUI will not upload/submit the file for
deployment.
To be consistent with the rest of GUI, if any required field is not filled in,
we will popup an alert box, telling you exactly which field is missing value,
instead of just mark that field with a 'RED star', as we are doing here.

Mark this as RFE and will be fixed in the next release.
thanks

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-10206] show restart activity Created: 13/Oct/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: survivant Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 10,206

 Description   

I was in the Applications tab and I click on restart Hudson. Hudson take a
little time to restart.. and when it's completed.. we see a message at the top
of the page..

that's fine.. but I have few applications installed, and I know idea if I click
on the right restart link.

We should have a icon beside the Enabled check.. like a round icon telling us
that this application is restarting.. and when it's completed.. we remove the icon.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-10084] add a link to the log when error deploying war Created: 07/Oct/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: survivant Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: PNG File Error-deploy-examples.png    
Issuezilla Id: 10,084

 Description   

we should have a link to see the error log.



 Comments   
Comment by survivant [ 07/Oct/09 ]

Created an attachment (id=3457)
image

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-10077] add a link to the log when error deploying war Created: 07/Oct/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.0pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: survivant Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 10,077

 Description   

Try to deploy a war.. got an error.. but I should have a link to the deploy log
error directly into the deploy screen.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-10618] datasource classname is not refreshed if user edit resource type Created: 27/Oct/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: yifeng1 Assignee: nityad
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: SunOS
Platform: Sun


Issuezilla Id: 10,618

 Description   

build : 10/27 nightly

glassfish-v3-b70-10_27_2009.zip

browser: firefox 3

platform: solaris

when user edit the resource type, datasource classname field should refresh to
show related classname.

to reproduce:

1. create a new jdbc connection pool
2. on the first wizard,select java.sql.Driver, select derby database
3. on the step 2 screen, driver classname is filled for user, click finish to
create the pool
4. now edit this pool, select java.sql.DataSource, notice the Datasource
classname is not refreshed to show the classname--> bug

5. we should show user the classname automatically if driver is in the
classpath. this behavior should be consistant with jdbc connection pool creation
time.(which console automatically fill the classname for user



 Comments   
Comment by Anissa Lam [ 27/Oct/09 ]

Request Nitya to investigate.

Comment by nityad [ 29/Oct/09 ]

This might not be possible currently. The admin console uses the following API
that requires a 'database vendor name' and 'resource type' to obtain the
datasource classname.
V3AMX.getInstance().getConnectorRuntime().getJdbcDriverClassNames(dbVendor, resType)

But in the edit page, the admin console knows the 'resource type' of the pool
but has no way of knowing the 'database vendor name' and hence cannot identify
the classname.

Comment by nityad [ 30/Oct/09 ]

After discussion with Anissa, converting to Enhancement.
GUI can add the database vendor name to the pool properties and then use that in
edit mode to get the datasource classname.

If we have time.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-10461] No progress is given to user for update tool Created: 20/Oct/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: rjdkolb Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Linux


Issuezilla Id: 10,461

 Description   

Build 67. Web profile

I have very slow bandwidth at work...
when I click on the updates 'Update tool' in the tree or any of the tabs in the
tree the page takes a long time to load. It may seem to the user something has
broken,
No progress is given to the user when they click on update, the page just takes
a long time to load. A progress bar or loading message would be nice.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-10419] It seems the update tool has a proxy host and port but no user name and password. (b67 web profile) Created: 20/Oct/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: New Feature Priority: Major
Reporter: rjdkolb Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Linux


Issuezilla Id: 10,419

 Description   

Our corp Lan only has access to proxy with a username and password.
Perhaps storing the user name and password is insecure, but now I can't update
Glassfish v3.

Is this something that will be fixed ?



 Comments   
Comment by rjdkolb [ 20/Oct/09 ]

A work around is to specify the $http_proxy in the un*x environment.
Please document this.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-11639] Provision to specify a jaas-context property for CertificateRealm Created: 03/Mar/10  Updated: 09/Jul/13

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: nasradu8 Assignee: Anissa Lam
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 11,639

 Description   

From Glassfish v3.1, there will be a provision for users to specify a (optional) jaas-context for
CertificateRealm. Using this property, users can specify an optional LoginModule to perform custom
authentication on the certificates provided by the client.

This requires a modification to the certificate realm configuration page to add the said property. This
property would be optional.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-11584] Request to free up the space occupied by the admin gui header Created: 17/Feb/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: jajalvipul Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Windows XP
Platform: PC


Issuezilla Id: 11,584

 Description   

Request to free up the space occupied by the admin gui header.

The header in Admin GUI is occupying more space (vertical) than is acutally
required. It unnecessarily introduces the vertical scrolling on other pages.

I strongely recommend to consider freeing up the valuable header space and
humbly present following options. There may be better options, for which I'm
open to receive the comments.

Option-1: Introduce Expand/Collapse option to header.
-----------------------------------------------------

Similar to Tree structure, present on the left hand side of the screen, where
user can expand/collapse the tree by clicking on the icon. I find this option
really useful. After selecting the common task, I usually collapse the tree,
freeing the space for the main frame to take over space on the screen.

On similar note, I would request to have such option for the header too.
With this option, user can expand or collapse the header as needed.

The advantages:
a. Freeing up the valuable space on collapsing.
b. If need be, more useful information can be added to the header without
worrying about its growing size as user can always collapse the header, when
not needed.

Option-2: Align the header title, buttons and other information on single line
------------------------------------------------------------------------------
Currently, the header title, buttons (Home, Version, Logout, help), logged in
user name, domain name, server name are appearing on 3/4 different lines.

With litle adjustments, I would say, all the above information can easily be
accomoated on single line, freeing up the space.

I would say, option-1 is ideal but if its not feasible, then only we should
consider option-2.



 Comments   
Comment by Anissa Lam [ 18/Feb/10 ]

Thanks for the suggestion. Will consider this on the next major release.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-11585] specifying "properties" during deployment of an application Created: 17/Feb/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Jagadish Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 11,585

 Description   

It is possible to specify --properties (or --property) using CLI during
deployment of an application archive. (asadmin deploy).

For a specific connector container requirement, specifying this property after
deployment of the archive is not feasible as it is needed during deployment to
provide appropriate resource-adapters (classloaders) accessibility.

Similar functionality is needed from GUI.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-11434] use of message viewer pane in admin console Created: 14/Jan/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Dies Koper Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: PNG File GFv3-with-message-viewer.PNG    
Issuezilla Id: 11,434

 Description   

When updating a value in settings screens and clicking Save, a "new values
successfully saved" message is displayed after the values have been saved.
When updating a value again and clicking on Save, as the old message is still
there it is not clear whether/when the new value has been saved.

Also, when doing a lot of operations on the admin console, get interrupted and
get back to work, not sure where I was.

I'd like to suggest introducing a message pane where these message would be
logged, with a timestamp, to that a bit of 'history' is left on the screen.
See attachment.

Note the following additional suggestions:

  • Error messages stand out in red.
  • All messages have a timestamp. The timestamp includes date and time, but is
    targeted at GUI users (i.e. no timezone info, no higher precision than seconds).
  • All messages have a message ID so they can be communicated easily over the
    phone or to your colleagues in the next cubicle, or looked up in the manual or
    on the Internet. As message IDs are not localized, this allows users of all
    locales to find and share information on the Internet (as googling a localised
    message of course gives fewer hits).
  • Button or link to delete messages in message pane.
  • Slider to view older messages.
  • Height of pane can be increased/decreased, only 4-7 lines high by default to
    allow most space to main pane.
  • Clicking on message IDs could open a JavaScript window with the message's
    cause and diag info (like the log viewer's).
  • Messages include some details about the operation that was completed so that
    after a few operations old messages still reveal what was done: include
    configuration parameter or tab name when values were updated, application name
    and target(s) when deploying an app, cluster name when creating/starting a
    cluster, etc.
  • Error messages from backend are generally included for reference, but ideally
    they would have their own message IDs with diag info to give the user more
    specific instructions on what went wrong and how to recover.


 Comments   
Comment by Dies Koper [ 14/Jan/10 ]

Created an attachment (id=4160)
image of what I meant

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-11869] Missing property in JDBCRealm configuration screen Created: 07/May/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: stijn_de_witt Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 11,869

 Description   

The JDBCRealm clas has a parameter to specify the column name of the username
column in the group table, that allows users to specify what column in their
group (memberships) table contains the foreign key to the user in the users
table:

PARAM_GROUP_TABLE_USER_NAME_COLUMN = "group-table-user-name-column";

However, this parameter is not reflected in the JDBCRealm configuration screen
in the Admin Console, so users have to know the long name and enter it in the
generic list of "Additional Properties" that is at the bottom of that screen.

Please add one extra input field below the existing "Group Name Column" field
and above the existing "Assign Groups" field, labeled "Group Table Username
Column", not mandatory and with hint text "Username column in group table.
Defaults to value of 'User Name Column'."



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-11725] Restarting an application should be more verbose Created: 24/Mar/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.0pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: timmattison Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Macintosh


Issuezilla Id: 11,725

 Description   

When restarting an application in the admin GUI a message is displayed after the operation is
successful:

"The application has been successfully restarted"

It would be convenient for this text to read:

"[01:53:22 AM] The YourApplicationName application has been successfully restarted"

This way when restarting multiple applications you can be sure that the application has finished
restarting before clicking on the next. Also, the time would assist you when you're restarting the same
application multiple times over a long time period. As it works right now the page uses a bit of AJAX or
refreshes very cleanly and it's hard to tell when it's done if you restart multiple applications in a row.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-10975] Log viewer page lacks a help button Created: 11/Nov/09  Updated: 19/Oct/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: future release

Type: Improvement Priority: Major
Reporter: Kim Haase Assignee: sirajg
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 10,975
Status Whiteboard:

3.1-exclude

Tags: 3_1-exclude

 Description   

There's an online help topic for the Log Viewer page, and a link to it in
common/src/main/resources/org/glassfish/common/admingui/Helplinks.properties:

logViewer=ref-logviewer.html

However, there is no way to view this link from the Log Viewer page itself. The
page can be reached only from the TOC in the help window. This should be fixed
in the next release if possible.



 Comments   
Comment by Anissa Lam [ 12/Nov/09 ]

We don't have a Help button for logviewer in v2 either.
So, not a regression. Will address this after v3.

thanks.

Comment by kumara [ 07/Dec/09 ]

Setting target release for unresolved issues submitted on v3 release to the next release. Not changing
issues submitted on v2.x release because they might not apply to v3.next release.

Comment by Anissa Lam [ 25/Jul/10 ]

Assign to Ken. Doc team will be affected as i don't know if there is any OLH
for logviewer now.

Comment by Kim Haase [ 26/Jul/10 ]

There is an OLH topic for the log viewer, as stated in the issue description.
There just isn't a link to it from the viewer itself. So the doc team doesn't
have to do anything unless the content of the viewer changes.

Comment by Mike Fitch [ 27/Jul/10 ]

For the log viewer page, the online help key is ref-logviewer and, as indicated
in the initial description, the entry

logViewer=ref-logviewer.html

is already in
common/src/main/resources/org/glassfish/common/admingui/Helplinks.properties.

Comment by Anissa Lam [ 29/Jul/10 ]

whoever works on the logviewer will need to add this help button.

Comment by kenpaulsen [ 07/Oct/10 ]

Updating MS

Comment by sirajg [ 10/Nov/10 ]

This is not a high priority and was not available in previous release.

Comment by Chris Kasso [ 08/Dec/10 ]

Clearing Fix Version (3.1_ms7) since the issue has been excluded from 3.1.





[GLASSFISH-11995] Automatic pre-population of default jaas-contexts for new realms Created: 24/May/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Nithya Ramakrishnan Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 11,995

 Description   

Currently while adding new security realms by choosing from the dropdown list for the pre-defined
realms like SolarisRealm, JDBCRealm, the Jaas-Context property appears with its value unfilled to let
the user populate the value. Since the jaas-context properties of pre-defined realms are fixed, this
could be pre-populated with default values. The user should be allowed to change this if required.This
would improve user experience.

The pre-defined valued for jaas-context values from login.conf are:

Classname - jaas-context
FileRealm - fileRealm
LDAPRealm - ldapRealm
SolarisRealm - solarisRealm
JDBCRealm - jdbcRealm
PamRealm (newly added) - pamRealm



 Comments   
Comment by Kim Haase [ 02/Dec/10 ]

I'd like to generalize this issue to request populating all the default property values for new realms. The jdbcRealm, for instance, has 7 required properties. I have to go to the online help and laboriously copy the default values into the fields in order to create the realm with these values.

I think that in general for the admin console the policy is to prepopulate required fields with default values, which can then be changed.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-14243] Admin console should not open outgoing network connections by default Created: 27/Oct/10  Updated: 19/Oct/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: future release

Type: Improvement Priority: Major
Reporter: Harald Wellmann Assignee: Anissa Lam
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Linux


Issuezilla Id: 14,243
Tags: 3_1-fishcat

 Description   

Glassfish admin console should not open any outgoing network connections by
default. It should do so only on an opt-in basis.

In production environments, outgoing network connections are typically blocked
by firewalls. Starting the admin console in a controlled environment may cause
error messages or inacceptable delays. The user is currently left without a clue
how to stop Glassfish from opening connections.

AFAIK the current workaround for this problem is to set
com.sun.enterprise.tools.admingui.NO_NETWORK and to delete the console update
plug-in (see #12432).

This is not acceptable from a usability point of view. Besides, NO_NETWORK is a
bit of a misnomer: if you set it to true, the update plugin will still try to
open a network connection.

Proposal:

Admin console opens with a startup screen:

Would you like to see community news on this screen? ( ) Yes (X) No
(Requires network connectivity to http://.....)

Would you like to check for updates on startup? ( ) Yes (X) No
(Requires network connectivity to http://.....)

Show this message on startup. (X) Yes ( ) No

In addition, there should be a new entry in the navigation menu for controlling
outgoing network connections.



 Comments   
Comment by Anissa Lam [ 27/Oct/10 ]

Thanks for the suggestion.
We will at least ensure that if NO_NETWORK is specified, that the console will not check for any
update.
Will try to implement the rest for 3.1 if time permits.
thanks.

Comment by Anissa Lam [ 19/Oct/12 ]

The NO_NETWORK variable has been honored in couple release.
Target the rest for future-release.





[GLASSFISH-3355] Allow JDBC driver upload Created: 16/Jul/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.0pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: hani Assignee: Anissa Lam
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 3,355

 Description   

It would greatly help new users if when creating a new database pool they have the option of uploading a
driver jar file. This would save users from having to drop to the command line and/or hunt through docs
to find out where it should be placed.

Alongside this, the error detection for jdbc connection testing should also use this facility, if the server
catches a class not found on test, then it should pop up a helpful message saying so, and offer the user
the chance to upload a driver.



 Comments   
Comment by Jason Lee [ 12/Jan/09 ]

Changing target version.

This may require a server restart due to ClassLoader issues, etc. We'll follow
up with that side of the house and see what we can do.

Comment by Jason Lee [ 12/Jan/09 ]

Updating version

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-3333] Ease of use : automatic installation of jdbc-drivers, detection of datasource classnames Created: 12/Jul/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: New Feature Priority: Major
Reporter: Jagadish Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Dependency
depends on GLASSFISH-4313 avoid overwriting domain.xml Open
Issuezilla Id: 3,333
Status Whiteboard:

v3-prd-item


 Description   

a) Competitive appservers provide a feature by which jdbc drivers (selected
ones) are
downloaded & installed during connection pool configuration in GUI.

b) Selection of jdbc-driver files can be done during con. pool
configuration.

c) We can also introspect the jar files and get the implementation
classes of datasource (javax.sql.DataSource/CPDS/XADS) and let the user
select appropriate ones.



 Comments   
Comment by Shalini [ 08/Feb/08 ]

added v3-prd-item

Comment by Anissa Lam [ 29/Feb/08 ]


add dependency to issue#4313

Comment by Jason Lee [ 29/Aug/08 ]

CC'ing myself

Comment by llc [ 07/Jan/10 ]

If there is an internal API available, AMX could expose this capability, it might even makes sense in an
existing MBean.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-3322] provision to display driver properties of arbitrary database-drivers Created: 11/Jul/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Jagadish Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Dependency
depends on GLASSFISH-4314 download and introspect jdbc driver Resolved
Issuezilla Id: 3,322
Status Whiteboard:

v3-prd-item


 Description   

During jdbc connection pool creation, when the user selects a database type from
the list of standard databases, datasource classname and the properties of
datasource are shown in admin-gui.

Same behavior can be extended for arbitrary jdbc drivers (drivers not shown in
the select list).
Once the user provides datasource-classname, we can introspect the datasource
class to provide the list of properties/attributes that the datasource will accept.



 Comments   
Comment by Shalini [ 08/Feb/08 ]

added v3-prd-item

Comment by Anissa Lam [ 29/Feb/08 ]

set target and dependency.

need backend to provide API to get the list of properties for gui to display

Comment by llc [ 07/Jan/10 ]

This should already be possible if the @Configured class annotates its getProperty() method appropriately
with @PropertyDesc. AMX exposes all such annotations in the MBean metadata.

But if it's not in an @Configured, some other mechanism will be required.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-3298] Add domain name to login screen of admin gui Created: 06/Jul/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: phenderson Assignee: anac
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 3,298

 Description   

Minor extra feature.

Add the name of the domain when displaying the login screen
(http://127.0.0.1:4848)

When multiple domains are configured. It is not obvious which domain the login
is for.



 Comments   
Comment by Anissa Lam [ 06/Jul/07 ]

Good suggestion, thanks.
Will look into it.

Comment by anac [ 09/Jul/07 ]

We could add the domain to the login. The domain name is already displayed in
the header when the user logs in so the user is aware which domain they are
administering. However, knowing the domain name at login might avoid some
confusion for some users so I'll work on adding to login screen as well.

Comment by Jason Lee [ 12/Jan/09 ]

Updating version

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-3299] Color scheme domains to help distinguish them. Created: 06/Jul/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: phenderson Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 3,299

 Description   

Perhaps pie in the sky feature.

When multiple domains are configured. For example production, testing and
development. It would be nice if the color scheme in the admin gui could be
configured for each domain.

Say red for the production domain, something else for the others.

Could possibly prevent accidental actions on the production domain, when the
user though they were using the testing domain.

Peter.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-3207] Admin GUI should display the complete (un)deployment status message to the user Created: 15/Jun/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: marina vatkina Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 3,207

 Description   

See issue https://glassfish.dev.java.net/issues/show_bug.cgi?id=3021 for the
initial problem that has been resolved only partially. This RFE is to make the
complete fix. The original issue has suggestions about the fix.



 Comments   
Comment by Jason Lee [ 12/Jan/09 ]

Updating target version

Comment by Jason Lee [ 12/Jan/09 ]

Updating version

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-3195] BC environment variable editor should allow create, edit and delete... Created: 14/Jun/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: slweng Assignee: yokelee
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 3,195

 Description   

Currently, the BC configuration editor only allows the user to edit an existing
environment variable. There are a couple of enhancement requests:
1. The "EnvironmentVariable" editor should always be available for users to
create new entries
2. Users should be able to delete any existing entries in the "environment
variable" list.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk change to set fix version to "not determined" where the issue is open but the value is for a released version.





[GLASSFISH-3133] Admin needs to ensure it starts applications in different threads from those being used to service a request in the admin-gui Created: 06/Jun/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Ryan Lubke Assignee: kenpaulsen
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 3,133

 Description   

See issue 3022. I've integrated a version of JSF that works around this
problem, but the admin server should be enhanced to provide a 'clean'
environment to an application that is being started via the admin-gui.



 Comments   
Comment by Tom Mueller [ 17/May/10 ]

-> Tom

Comment by Tom Mueller [ 27/Jul/10 ]

Here "admin" is actually the admin GUI. Reassigning this to admin_gui.

Comment by Anissa Lam [ 27/Jul/10 ]

->Ken.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-3062] log viewer Advanced->Basic switching loses logger filter info Created: 24/May/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: locolobo Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 3,062

 Description   

Scenario:

  • User enters Log Viewer
  • Search results are displayed for the default logger and default log detail level.
  • User clicks the "Advanced" link and enters the advanced search and changes the
    logger.
  • User clicks the "Basic" link and returns to the basic page.

Now the search results presented are filtered on the logger selected in the
Advanced page but context is no longer displayed to the user.

This is a usability issue that can be corrected by providing the user textual
context of what filter is being applied to the search results.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-3593] RFE: Provide a way for web admin console user to see asadmin commands being generated Created: 10/Sep/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1peur1
Fix Version/s: not determined

Type: New Feature Priority: Major
Reporter: rdelaplante Assignee: Anissa Lam
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 3,593

 Description   

The web console is useful for configuring everything without having to learn the
asadmin commands. Sometimes I might want to create a script for use by asadmin
to make production deployment quicker. It would be nice if I could configure
one server using the web admin GUI and see which asadmin commands I would use
for the last operation I completed. Maybe show me all of the asadmin commands I
have done since logging in.

I realize that the web admin console probably uses JMX to communicate with the
app server instead of asadmin.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-3518] Display domain.xml in Console Created: 21/Aug/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1peur1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Anissa Lam Assignee: cchidamb
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 3,518

 Description   

We should display domain.xml as read only text like other descriptor files so
user can view that from Admin Console.
This is requested by Sreeram.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-3475] Lots of default MySQL properties, some of them harmful Created: 08/Aug/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1peur1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: sepphugo Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Macintosh


Issuezilla Id: 3,475

 Description   

In build b58-rc1, when I create a new MySQL connection pool, I'm asked to enter or at least revise about
50 MySQL connection properties. Normally four of them (user, databaseName, serverName, password) are
important.

Its very hard to pick the relevant four from the list and, what is worse, there's normally no use in setting
all of the properties as some of them interfere with each other. In my case, the defaults for the URL or Url
properties confusingly kept my connection from working.

So, what about going back to the policy of showing just the relevant properties when creating a
connection pool or, at least, make sure that only non-conflicting properties are on display?



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-3448] Load Balancer Target page should show Applications & Targets LB Status Created: 29/Jul/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 3,448

 Description   

The Target of Load Balancer shows the target and allows user to edit the Health
Checker. If the target is a standalone instance, it also allows you to change
lb-enabled attribute of this target.
However, if the target is a cluster, there is no way to change lb-enable of
this cluster's instance. We should add a link in this table to the instances
tab of this cluster so user can change that easily.

Also, a link to the deployed applications page for the target will be very
helpful to find out or change the lb-enabled flag of the deployed applications.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-1846] Change the ui for the option of call flow 'enabled' Created: 21/Dec/06  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.0pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: jj156416 Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,846

 Description   

It is about UI improvement for the function 'Monitor'-> 'Call Flow'
Since the Call Flow is automatically disabled when the application server is
restarted, suggested to change the UI for 'Call Flow Monitoring' from checkbox
to an action button.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-490] Display the list of virtual servers a webapp has been deployed to Created: 28/Mar/06  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.0pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: jluehe Assignee: Anissa Lam
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 490

 Description   

Application Server > Applications > Web Applications:

In addition to displaying a web application's context root, in would be useful
to list all the virtual servers to which a given webapp has been deployed to
(with the given context root).

Application Server > Configuration > HTTP Service > Virtual Servers:

Add a column that shows all the context roots currently "occupied" for each
virtual server. This will show, amongst other things, if a request with no
context path will be mapped to a virtual server's docroot or to a web
application deployed to the virtual server's root context ("/").

This feature would allow users to troubleshoot why certain requests are not
getting mapped as expected, without having to resort to their domain.xml (where
all this info is already available).

See http://forums.java.net/jive/thread.jspa?messageID=97906 for details.



 Comments   
Comment by Jason Lee [ 12/Jan/09 ]

Changing target

Comment by Jason Lee [ 12/Jan/09 ]

Updating version

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-232] Link to Glassfish forum should be shown on error log pages Created: 07/Feb/06  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: sg112326 Assignee: kenpaulsen
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: Java Archive File CacheProblemTestCase.jar    
Issuezilla Id: 232

 Description   

When customers see SEVERE log messages or an error page from the appserver in
the admin GUI, the details page should include a link to the GlassFish forum.
This should be captioned with the message encouraging the user to find out from
the forum if a topic connected with the exception condition already exists or to
raise a new topic on these lines.
This would help the customer easily access the location to find more help while
also helping bring more participation in the forums.



 Comments   
Comment by Anissa Lam [ 27/Feb/06 ]

We will try to see if we can construct a search URL of the GlassFish forum.
If not, maybe we can link to the GlassFish forum so user at least has a place to
start.

Comment by Anissa Lam [ 27/Feb/06 ]

assign to kenpaulsen.

Comment by kenpaulsen [ 12/Sep/06 ]

Created an attachment (id=433)
Servlet that demonstrates the problem.

Comment by kenpaulsen [ 12/Sep/06 ]

Setting as P2 b/c all admin GUI developers see this problem every day and have
to work around it.

Comment by kenpaulsen [ 12/Sep/06 ]

The attachment is not related to this bug... I modified and attached it to the
wrong issue.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-807] JSF: need checkbox to enable/disable access logging Created: 06/Jul/06  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: jfarcand Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 807

 Description   

Currently, GlassFish add by default the Single Sign On Valve and the Acess
Logging Valve. Those two valves affect performance and might now be enabled by
default. Other Application Server aren't enabling by default SSO and Access
Logging so when comparing out-of-the-box performace, GlassFish is always
impacted by those two features.



 Comments   
Comment by jfarcand [ 06/Jul/06 ]

Change the title.

Comment by jfarcand [ 17/Jul/06 ]

See also:

https://glassfish.dev.java.net/issues/show_bug.cgi?id=836

Comment by jfarcand [ 20/Jul/06 ]

Remove SSO handling from this issue (Will open another one).

Access Logging will be turned off. But Before, we need to be able to turn the
feature on/off, at the virtual-server level. Assigning to admin-gui so they can
add support graphically for property:

<property name="accessLoggingEnabled" value="true|false"/>

Re-assign to me once this property is exposed at the virtual-server screen.

Comment by km105526 [ 20/Jul/06 ]

I have a suggestion – it is better if we don't make the user type in the
"exact" name of the property in the generic property sheet editor. Can we have
a check-box instead that the user either checks or unchecks when the access
logging is to be enabled/disabled?

Comment by jfarcand [ 20/Jul/06 ]

Kedar,

this is a very good recommendation.

+1

Comment by Anissa Lam [ 20/Jul/06 ]

Admin GUI is already showing the properties of the virtual server. It is
showing whatever is in the domain.xml. I think you should modify the
domain.xml template, add this property and its default value. Once its in
domain.xml, it will show up in GUI, and user can change if they don't like the
default. We have to display whatever is in domain.xml. Currently, there is
the property "docroot" and "accessLog".
This issue should be assigned to whoever modify the domain.xml template.

Comment by Anissa Lam [ 20/Jul/06 ]

If this is handled as property, it will be shown in the property table, and yes,
user will have to be careful with the spelling of th property name.
If it is desired to be a boolean attribute, presented as a checkbox, then you
may need to modify the dtd to introduce this as an attribute of virtual server.
btw, what is the default if user doesn't specify this property ?

Comment by jfarcand [ 20/Jul/06 ]

The accessLoggingEnabled property is not documented and was never exposed. So
you will not find it in any domain.xml|dtd and documentation. Instead of
introducing the property in domain.xml, I would prefer the admin-gui add the
property in domain.xml (under virtual-server) only when people enable it. Right
not it is enabled by default programmatically (not exposed).

If not added to domain.xml, the default will be false.

Comment by Anissa Lam [ 03/Nov/06 ]

change Summary to ensure this will be addressed in the JSF version of admin-gui.
Assign to Ana.

Comment by km105526 [ 03/Nov/06 ]

Just to be clear, this bug should pertain to showing a check-box on the GUI.
The motivation is to make users' lives easier. They would not have to write the
property "accessLoggingEnabled" in the text-box.

The GUI components should just set the appropriate value to the property in
response to user action.

Setting of the property accessLoggingEnabled to "false" out-of-the-box
for developer profile is already taken care of. Please see one pager on profiles
for GlassFish V2.

If the above is acceptable, I'd recommend changing the value of "Summary" field
of this issue.

Comment by km105526 [ 03/Nov/06 ]

accidentally closed, reopening.

Comment by km105526 [ 03/Nov/06 ]

accepted.

Comment by Anissa Lam [ 03/Nov/06 ]

change summary to better reflect the issue.

Comment by Anissa Lam [ 29/Jul/07 ]

-> anilam
UI will be added before FCS

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-741] request for https redirect Created: 15/Jun/06  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 741

 Description   

This RFE is created to keep track of the effort for http redirecting. Admin GUI
hopes to have the feature where http://<host>:4848 can be redirected to
https://<host>:4848
Not sure if CLI will be able to use this feature.

From jeanfrancois:
Mainly, Grizzly will send HTTP redirect when the wrong protocol is used (Browser
can handle this) but I'm not sure if CLI handle redirect. Since this affect
performance, we gonna need to make it configurable (via System properties or by
adding admin support). Internally it will be implemented as Grizzly's Handler,
so we can easily cover more than one scenario.



 Comments   
Comment by jfarcand [ 25/Aug/06 ]

Started working on this feature since SSL non blocking has been implemented.

Comment by jfarcand [ 06/Oct/06 ]

OK the feature is now ready. The scenario covered are:

http://...:4848 will be redirected to https://...:4848
http://...:4849 will be redirected to https://...:4848
https://...:4849 will be redirected to https://...:4848

Since we are sniffing the request line, their will be a small performance
regression (very small). Next step is to decide how we enable|disable this
feature. The feature needs to be added to virtual-server and we need to allow
the user to configure the external port that will be redirected (in the example
above, port 4849).

Comment by km105526 [ 06/Oct/06 ]

We need to think more about the redirects, however.
Are you suggesting that in a developer scenario, both ports (4848, 4849) be
occupied, if enable this?

Comment by jfarcand [ 09/Oct/06 ]

FTI, I will soon make a proposal on the dev list explaning how this feature will
works to make sure I've collected all the scenarios (This feature is asked since
8.0 so I need to remember all the requirements ). But if you want to redirect
one port to another (4849->4848), then yes you must opens two ports. On the
contrary, changing the protocol doesn't requires an extra port (http->https).

The mechanism is also supportting unique port, meaning all protocols can ping
port 8080 and an internal redirection will occurs. If properly implemented,
GlassFish will be able to start with a single port and redirect the protocol to
the proper container. But I doubt we will have the time to implement this for v2.

Comment by jfarcand [ 16/Oct/06 ]

Prepare Grizzly for unique port|redirection implementation. The functionality is
not yet committed|enabled.

Checking in DefaultReadTask.java;
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/connector/grizzly/DefaultReadTask.java,v
<-- DefaultReadTask.java
new revision: 1.6; previous revision: 1.5
done
Checking in GrizzlyHttpProtocol.java;
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/connector/grizzly/GrizzlyHttpProtocol.java,v
<-- GrizzlyHttpProtocol.java
new revision: 1.30; previous revision: 1.29
done
Checking in SecureSelector.java;
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/connector/grizzly/SecureSelector.java,v
<-- SecureSelector.java
new revision: 1.2; previous revision: 1.1
done
Checking in SelectorThread.java;
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/connector/grizzly/SelectorThread.java,v
<-- SelectorThread.java
new revision: 1.85; previous revision: 1.84
done
Checking in async/DefaultAsyncExecutor.java;
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/connector/grizzly/async/DefaultAsyncExecutor.java,v
<-- DefaultAsyncExecutor.java
new revision: 1.9; previous revision: 1.8
done
Checking in blocking/SelectorBlockingThread.java;
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/connector/grizzly/blocking/SelectorBlockingThread.java,v
<-- SelectorBlockingThread.java
new revision: 1.6; previous revision: 1.5
done
Checking in ssl/SSLReadTask.java;
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/connector/grizzly/ssl/SSLReadTask.java,v
<-- SSLReadTask.java
new revision: 1.9; previous revision: 1.8
done
Checking in ssl/SSLSelectorThread.java;
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/connector/grizzly/ssl/SSLSelectorThread.java,v
<-- SSLSelectorThread.java
new revision: 1.12; previous revision: 1.11
done
Checking in ssl/SSLUtils.java;
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/connector/grizzly/ssl/SSLUtils.java,v
<-- SSLUtils.java
new revision: 1.8; previous revision: 1.7
done
Checking in ssl/SSLWorkerThread.java;
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/connector/grizzly/ssl/SSLWorkerThread.java,v
<-- SSLWorkerThread.java
new revision: 1.2; previous revision: 1.1
done

Comment by jfarcand [ 24/Oct/06 ]

Added unique port support in Grizzly:

RCS file:
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/portunif/PortUnificationPipeline.java,v
done
Checking in PortUnificationPipeline.java;
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/portunif/PortUnificationPipeline.java,v
<-- PortUnificationPipeline.java
initial revision: 1.1
done
RCS file:
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/portunif/ProtocolFinder.java,v
done
Checking in ProtocolFinder.java;
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/portunif/ProtocolFinder.java,v
<-- ProtocolFinder.java
initial revision: 1.1
done
RCS file:
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/portunif/ProtocolHandler.java,v
done
Checking in ProtocolHandler.java;
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/portunif/ProtocolHandler.java,v
<-- ProtocolHandler.java
initial revision: 1.1
done
RCS file:
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/portunif/protocols/http/HttpProtocolFinder.java,v
done
Checking in protocols/http/HttpProtocolFinder.java;
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/portunif/protocols/http/HttpProtocolFinder.java,v
<-- HttpProtocolFinder.java
initial revision: 1.1
done
RCS file:
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/portunif/protocols/http/HttpProtocolHandler.java,v
done
Checking in protocols/http/HttpProtocolHandler.java;
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/portunif/protocols/http/HttpProtocolHandler.java,v
<-- HttpProtocolHandler.java
initial revision: 1.1
done
RCS file:
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/portunif/protocols/http/HttpsProtocolFinder.java,v
done
Checking in protocols/http/HttpsProtocolFinder.java;
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/portunif/protocols/http/HttpsProtocolFinder.java,v
<-- HttpsProtocolFinder.java
initial revision: 1.1
done
RCS file:
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/portunif/util/ProtocolInfo.java,v
done
Checking in util/ProtocolInfo.java;
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/portunif/util/ProtocolInfo.java,v
<-- ProtocolInfo.java
initial revision: 1.1
done
RCS file:
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/portunif/util/Redirector.java,v
done
Checking in util/Redirector.java;
/cvs/glassfish/appserv-http-engine/src/java/com/sun/enterprise/web/portunif/util/Redirector.java,v
<-- Redirector.java
initial revision: 1.1
done

By default, this is disabled. Will soon add the property to enable it.

Comment by jfarcand [ 05/Dec/06 ]

Re-assign to the admin team for more information. Mainly, I need to know when
Grizzly will listen to port 4849 and redirect all request to port 4848. The is
two possible use case:

case 1
------
In domain.xml, we add by default an http-listener that listen to port 4849.

<http-listener acceptor-threads="1" address="0.0.0.0" blocking-enabled="false"
default-virtual-server="__asadmin" enabled="true" family="inet"
id="admin-listener" port="4849" security-enabled="false" server-name=""
xpowered-by="true">

and enable port unification:

<property name="proxiedProtocol" value="redirect"/>

case 2
------
We don't define any new http-listener in domain.xml, but Grizzly internaly
listen to port 4849 and do the redirection to the admin port (doesn't need to be
4848, any port).

case 3
------
Do nothing like right now.

Please re-assign with the answer

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-4486] Use descriptive information found in deployment descriptor Created: 24/Mar/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1peur1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: mkarg Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 4,486

 Description   

It would be very beneficial for the administrator, if the web based admin GUI
would use all the optional but nice information found in the deployment
descriptor, like <description>, <small-icon> and <large-icon>.

Currently neither the description not the icons are getting used anywhere.

It would be good if GlassFish would show this description and icons in the admin
GUI:

  • Administrator better identify the applications visually.
  • Developers can check whether their provided icons are correctly detected.
  • It is a good proof of concept for the specification.
  • It just would look cool.


 Comments   
Comment by Jason Lee [ 12/Jan/09 ]

Updating version

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-4941] log4j: DEBUG entries not shown in admin gui log viewer Created: 27/Apr/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: v2.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: kawazu Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Linux


Issuezilla Id: 4,941

 Description   

We're in the process of migrating our applications (so far tomcat-based, using
commons-logging + log4j) to glassfish v2u1. Making extensive use of the admin
gui log viewer, unfortunately this doesn't correctly deal with log4j DEBUG
entries as it obviously is limited to the JDK logging default levels. Having
support for log4j and/or a "wildcard" loglevel selection rather than the
predefined list would be helpful.



 Comments   
Comment by kumara [ 01/Sep/09 ]

Changing version from 9.1.1 to v2.1 to reflect new name/version.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-4673] Clicking on reboot should reboot but not shut down Created: 08/Apr/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1peur1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: mkarg Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 4,673

 Description   

Sometimes admin gui says that I shall reboot GlassFish. So I click on reboot,
and virtually anybody would expect that it DOES reboot. But in fact it just
shuts down. So people wait and wait and wait (since virtually nobody reads the
message that says, you have to boot on your own).

It would be great if a click on reboot would really do a reboot.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-1565] Unable to access the web admin interface via Opera Created: 22/Nov/06  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Ryan Lubke Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,565

 Description   

When attempting to connect to the web administration interface via Opera,
the user gets stuck in a continual redirect loop.



 Comments   
Comment by Anissa Lam [ 08/Jan/07 ]

Admin Console depends on a set of jsf components, and Opera is not an officially
supported browser.
Will work with the other to get the support in, marking this as Enhancement.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-1275] RFE : Segregation of mandatory & db-driver specific properties in jdbc connection pool Created: 10/Oct/06  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: New Feature Priority: Major
Reporter: Jagadish Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,275

 Description   

Creating a connection pool for various database vendors.
Eg: While creating a con. pool for MySQL, more than 100 properties are shown to
user. Please see issue "IT 549 - configuring MySql datasource uses invalid
property names" which has the screenshots.

1) It would be better if mandatory properties and db-driver specific properties
are segregated in two different tabs.
2) Further, all the 100+ properties are persisted to domain.xml even if they are
not modified/used by the user. It would be nice if only the
user-modified/selected properties are persisted to domain.xml. When user is
editing the connection pool, all properties can be shown again.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-4313] avoid overwriting domain.xml Created: 28/Feb/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Dependency
blocks GLASSFISH-3333 Ease of use : automatic installation ... Open
Issuezilla Id: 4,313
Status Whiteboard:

v3-prd-item


 Description   

AdminConsole-017 in
http://wiki.glassfish.java.net/Wiki.jsp?page=V3AdminConsoleImprovements

An administrator cannot overwrite modifications created by another administrator
while making simultaneous modifications to DAS settings.

Configuration has transactional semantics. Will throw exception when there is a
conflict at a fine grained level. No top level "lock" button will be shown to
the user.



 Comments   
Comment by Anissa Lam [ 28/Feb/08 ]

add keyword

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-4310] improve charting, use pie chart when appropriate Created: 28/Feb/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 4,310
Status Whiteboard:

v3-prd-item


 Description   

AdminConle-027 in
http://wiki.glassfish.java.net/Wiki.jsp?page=V3AdminConsoleImprovements.

integrate newer version of charting library, use pie chart when appropriate eg.



 Comments   
Comment by Anissa Lam [ 28/Feb/08 ]

add keyword

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-4309] strong tie to community, link to forum etc. Created: 28/Feb/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 4,309
Status Whiteboard:

v3-prd-item


 Description   

This is AdminConsole-030 in
http://wiki.glassfish.java.net/Edit.jsp?page=V3AdminConsoleImprovements

Description says:

link to trouble shooting guide, link to forum, etc. help with root cause
analysis for any error



 Comments   
Comment by Anissa Lam [ 28/Feb/08 ]


add keyword

Comment by Anissa Lam [ 28/Feb/08 ]

AdminConsoe-023 will be addressed by this issue

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-4308] live update for monitoring statistics Created: 28/Feb/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 4,308
Status Whiteboard:

v3-prd-item


 Description   

This is AdminConsole-016 in
http://wiki.glassfish.java.net/Wiki.jsp?page=V3AdminConsoleImprovements

Live update of monitoring statistics from within admin UI



 Comments   
Comment by Anissa Lam [ 28/Feb/08 ]


add keyword

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-4304] provide dashboard view of clusters/instances Created: 28/Feb/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 4,304
Status Whiteboard:

v3-prd-item


 Description   

This is AdminConsole-008 specified in the requirement:
http://wiki.glassfish.java.net/Wiki.jsp?page=V3AdminConsoleImprovements

Provide a 'dashboard' view of application clusters and/or instances.



 Comments   
Comment by Anissa Lam [ 28/Feb/08 ]

add v3-prd-item

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-4207] Admin GUI should show the type of config-properties Created: 16/Feb/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 9.1peur1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: mkarg Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 4,207

 Description   

When deploying a .rar file, the adming GUI currently shows two columns. The
first column contains the name of the property. The second column allows the
user to edit the type of the property. To better support the user, a third
column should be added showing the expected data type (java.lang.String,
java.lang.Integer etc.).



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-4206] Admin GUI allows to modify the name of a config-property Created: 16/Feb/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui