From: Ankush Kanungo <ankushkanungo_at_gmail.com>
Date: Tue, 21 Apr 2009 20:35:36 -0700

Hi,

I am an SJSU student and we are testing GlassFish Application Server for one
of the curriculum project.

According to Judy's email(Please see below) . I am sending this to quality
alias first.

Please lets us know, if it is ok to file this as a bug on Sun's site or
not.
--------------------------------------------------------------------------------
Bugs#1

1. Reporter: ankushkanungo
2. Component: GlassFish Application Server V3
3. Found in Version(build): glassfish-v3-web-ea-b44
4. Subcomponent: Installer.
5. Platform: Linux
6. OS: Ubuntu 8.04
7. Priority: P2
8. Summary: Installation on Linux with .sh file. Admin console access
problem when providing different port other than default(4848).
9. Description:

Steps to reproduce:

a. In the Administrating Settings for Installation.
b. When providing admin port(4849) other than default(4848).
c. Installation completion status says completed successfully.
d. One can access the server successfully by entering http://localhost:8080/
e. After this, one can access the admin console by clicking on go to the
Administration Console .link.
f. But here, link to the admin console is hard coded as "
http://localhost:4848/".
g. Therefore after clinking on go to the Administration Console .link, a
user gets an error page "Failed to connect" because
    admin console is running on port 4849.
h. A user can directly access the admin console by entering URL "
http://localhost:4849/"

See the attached screen shots for further details.

a. Bug #1- Screen Shot #1:- Providing 4849 port number.
b. Bug #1- Screen Shot #2:- Accessing the server at http://localhost:8080/ and
then clicking on <http://localhost:8080/> <http://localhost:8080/>go to the
Administration Console .link.
c. Bug #1- Screen Shot #3:- Failed to connect the server at 4848 port
d. Bug #1- Screen Shot #4:- Directly accessing the server at port 4849

Thank you,

Ankush


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


---------- Forwarded message ----------
From: Judy Tang <Judy.J.Tang_at_sun.com>
Date: Thu, Apr 16, 2009 at 3:56 PM
Subject: please hold on for filing negative test bugs, thanks :-)
To: sjsu-glassfish-students_at_sun.com


Hi Everyon,

I got input from developer on too many invalid/dup bugs. Here is what we
should do. Please
give your support. Also please let us know if you have question/suggestion.

(1) Please do not file negative test bugs in Admin GUI, Installer, Update
tool since most cases are
already reported and when developer fix one place, they most likely will
take care of the
same situation for other places, some time the fix in one place will address
other cases. Just to give
you an example last night and this morning Yifeng and Anissa processed more
than 70 dup/invalid
bugs. This need to stop !

(2) Please try more main functional/positive end to end testing, when you
see any issue, please send
email to quality alias first, SQE and developer will evaluate the issue and
let you know a bug
is needed or not.

It is first time we have so many students testing GlassFish, we are very
happy to have
you here to learn and to help, because this is first time, we also have a
lot lesson to learn together on how
to handle dup/invalid bugs. We will keep improving. With your help we will
:-)

Thanks,
Judy