<< Back to previous view

[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
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 13,335
Tags:
Participants: Anissa Lam, lidiam and Tom Mueller

 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 01:53 PM ]

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 02:18 PM ]

reassign to Lidia for which page this occurs.

Comment by Tom Mueller [ 06/Mar/12 09:56 PM ]

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





[GLASSFISH-18121] Intermittent: cannot start instance on a remote node: server requires a password Created: 05/Jan/12  Updated: 10/Jan/12

Status: Open
Project: glassfish
Component/s: distributed management
Affects Version/s: 3.1.2_b16
Fix Version/s: None

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

ogs-3.1.2-b16.zip, DAS on solaris, node on WinXP


File Attachments: Text File server.log     Text File server.log.clusteredinstance.txt    
Tags: 312_gui_new 312_qa 3_1_2-exclude
Participants: Byron Nevins and lidiam

 Description   

This is an intermittent issue but it happened twice already. I create a standalone instance on a DCOM node and cannot start it with the following in the server.log of the instance:

[#|2012-01-04T15:44:32.265-0800|SEVERE|glassfish3.1.2|javax.enterprise.system.to
ols.admin.com.sun.enterprise.container.common|_ThreadID=10;_ThreadName=Thread-2;

The server requires a valid admin password to be set before it can start. Pleas
e set a password using the change-admin-password command.
#]

I have a cluster with two instances on the same node running fine. I also created another standalone instance and it started fine. I'm accessing Admin Console on solaris from the windows box, so secure admin and domain password are both set. I'll attach server.log.



 Comments   
Comment by lidiam [ 05/Jan/12 06:37 AM ]

I just got this error for the 3rd time but this time with an SSH node. I had a cluster with two instances, one on localhost one on an ssh node (solaris). The cluster was running fine. I stopped it and added another instance on the ssh node. When I tried to start cluster the newly added server instance failed to start with the following error in Admin Console:

Command succeeded with Warning
clt2: Could not start instance clt2 on node tuppy (tuppy). Command failed on node tuppy (tuppy): Warning: Synchronization with DAS failed, continuing startup... Waiting for clt2 to start .....................................Command start-local-instance failed. Error starting instance clt2. The server exited prematurely with exit code 0. Before it died, it produced the following output: Launching GlassFish on Felix platform Jan 4, 2012 10:31:54 PM com.sun.common.util.logging.LoggingConfigImpl copyLoggingPropertiesFile WARNING: Logging.properties file not found, creating new file using DAS logging.properties [#|2012-01-04T22:31:55.037-0800|INFO|glassfish3.1.2|com.sun.enterprise.server.logging.GFFileHandler|_ThreadID=1;_ThreadName=main;|Running GlassFish Version: GlassFish Server Open Source Edition 3.1.2-b16 (build 16)|#] [#|2012-01-04T22:31:57.647-0800|INFO|glassfish3.1.2|javax.enterprise.system.core.transaction.com.sun.jts.CosTransactions|_ThreadID=10;_ThreadName=main;|JTS5014: Reco .... msg.seeServerLog

Instance's server.log contained the same error and exception:

[#|2012-01-04T22:31:59.029-0800|SEVERE|glassfish3.1.2|javax.enterprise.system.to
ols.admin.com.sun.enterprise.container.common|_ThreadID=10;_ThreadName=Thread-2;

The server requires a valid admin password to be set before it can start. Pleas
e set a password using the change-admin-password command.
#]

[#|2012-01-04T22:31:59.031-0800|SEVERE|glassfish3.1.2|javax.enterprise.system.co
re.com.sun.enterprise.v3.services.impl|_ThreadID=10;_ThreadName=Thread-2;|Unable
to start v3. Closing all ports
org.jvnet.hk2.component.ComponentException: injection failed on com.sun.enterpri
se.v3.admin.AdminAdapter.authenticator with interface org.glassfish.internal.api
.AdminAccessController
at org.jvnet.hk2.component.InjectionManager.error_injectionException(Inj
ectionManager.java:284)
at org.jvnet.hk2.component.InjectionManager.inject(InjectionManager.java
:165)
at org.jvnet.hk2.component.InjectionManager.inject(InjectionManager.java
:93)
at com.sun.hk2.component.AbstractCreatorImpl.inject(AbstractCreatorImpl.
java:126)
at com.sun.hk2.component.ConstructorCreator.initialize(ConstructorCreato
r.java:91)

Comment by lidiam [ 05/Jan/12 06:41 AM ]

Attaching log file for clustered instance on an ssh node that fails to start.

Comment by Byron Nevins [ 09/Jan/12 08:51 AM ]

This will take more time to hunt-down than is available before HCF for 3.1.2.

Comment by Byron Nevins [ 10/Jan/12 07:25 PM ]

I can't reproduce this. Please do the following. We need to make sure it's a Dcom issue.

When it happens again simply run start-local-instance directly on the remote machine. Use the --verbose option

What does it say?





Generated at Fri Apr 18 10:18:56 UTC 2014 using JIRA 4.0.2#472.