Issue Details (XML | Word | Printable)

Key: GLASSFISH-18361
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Sanjeeb Sahoo
Reporter: dkroot
Votes: 1
Watchers: 2
Operations

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

GlassFish OSGI Web Console is not available when GlassFish is installed on custom ports

Created: 14/Feb/12 06:32 PM   Updated: 12/Feb/13 12:02 AM
Component/s: OSGi
Affects Version/s: 3.1.1
Fix Version/s: None

Time Tracking:
Not Specified

Environment:

GlassFish 3.1.1, Java EE SDK 6 u3 running on JDK 6, Mac OS X 10.6.8 or Windows Server 2003 R2 SP2


Tags: admin-gui osgi 3_1_2-exclude 3_1_2-next
Participants: Anissa Lam, dkroot, Joe Di Pol and Sanjeeb Sahoo


 Description  « Hide

Test case:
1. Install either 3.1.1 standalone or Java EE SDK.
2. Select custom ports for HTTP service and Admin service. For example: 1234 and 1235.
3. Run an update tool, install:
glassfish-osgi-gui Application Servers 3.1.1-12
glassfish-osgi-feature-pack Application Servers 3.1.1-12
glassfish-osgi-incorporation Application Servers 3.1.1-12

4. Start the domain

Expected:
OSGi Web Console is available either via Admin Console > server > OSGi Console or via http://localhost:1234/osgi/system/console/ per the documentation.

Actual:
Admin console displays "can't contact server at localhost:8080" in Firefox. The direct OSGi Web Console link displays 404.

Workaround:
Applied workaround from http://java.net/jira/browse/GLASSFISH-18228. The direct link is functional now. However, the Admin console still displays the same error message.



Anissa Lam added a comment - 12/Feb/13 12:02 AM

Request Sahoo to do the evaluation. I am not sure if this need to be addressed for 4.0, and what needs to be done in the console side. thanks.


Joe Di Pol added a comment - 17/Feb/12 07:51 PM

Too late to address in 3.1.2. Tagging for consideration in next release.