Bug 778192 (SOA-697) - Tomcat status not available
Summary: Tomcat status not available
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-697
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: EAP
Version: 4.3 IR2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 IR3
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-21 12:44 UTC by Julian Coleman
Modified: 2008-11-23 17:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
4.3.0 IR2 standalone and embedded.
Last Closed: 2008-10-02 14:56:47 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 778582 0 high CLOSED Tomcat status not available 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-697 0 None None None Never

Internal Links: 778582

Description Julian Coleman 2008-08-21 12:44:29 UTC 
Date of First Response: 2008-08-27 11:55:38
project_key: SOA

The Tomcat status links from the JBoss SOA Welcome page (http://<hostname:8080/status)
return a 404 not found error.
Comment 1 Julian Coleman 2008-08-22 13:29:46 UTC 
The EAP tomcat status page has moved to:

  http://<hostname>:8080/web-console/status

The SOA Welcome page needs to be updated to follow suit.
Comment 2 Julian Coleman 2008-08-22 13:31:36 UTC 
The `/web-console/status' URL does not use the SOA integrated console,
but it does use the same username/password.  Should it be changed to
look more like the other SOA consoles?
Comment 3 Julian Coleman 2008-08-26 15:35:00 UTC 
Fixed in revision 1745 of:
  build-tools/builders/soa/p-consoles/ROOT.war/index.html

Log message:
  Catch up with EAP moving the tomcat status under web-console/
Comment 4 Julian Coleman 2008-08-26 15:39:12 UTC 
The logo at the top of the page (URL http://localhost:8080/web-console/logo.gif)
returns a 404 (not found) error.

This could be a EAP bug, introduced in 4.3.0 CP02, when the secured console was
introduced.
Comment 5 trev 2008-08-27 15:55:38 UTC 
closing this jira will raise an EAP one and an new SOA jira to monitor
Comment 6 Julian Coleman 2008-10-02 14:49:33 UTC 
Link: Added: This issue depends JBPAPP-1146
Comment 7 Len DiMaggio 2008-10-02 14:56:47 UTC 
Verified fixed in IR5
Comment 8 Julian Coleman 2008-11-23 17:36:22 UTC 
Link: Added: This issue is related to SOA-1054
Note You need to log in before you can comment on or make changes to this bug.