Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 724666 (BRMS-567)

Summary: WAS 7 ignores index.jsp as a welcome page
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Jiri Locker <jlocker>
Component: ConfigurationAssignee: Julian Coleman <jcoleman>
Status: CLOSED UPSTREAM QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.1.0 GA, BRMS 5.2.0.GACC: ajuricic, manstis, rzhang
Target Milestone: ---   
Target Release: BRMS 5.2.0.GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/BRMS-567
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
IBM WebSphere Application Server returned a '404 page not found' error message when users attempted to access http://localhost:8080/jboss-brms/. The Drools component has been upgraded to 5.2 and the bug no longer presents.
Story Points: ---
Clone Of: Environment:
IBM WebSphere Application Server - ND, 7.0.0.0
Last Closed: 2025-02-10 03:13:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jiri Locker 2011-03-11 12:52:27 UTC
securitylevel_name: Public

When opening http://hostname:9080/jboss-brms/ server response is:
{noformat}Error 404: SRVE0190E: File not found: {0} {noformat}
Can be worked around by explicitly specifying index.jsp as a welcome page in web.xml by adding:
{noformat}
<welcome-file-list>
  <welcome-file>
    /index.jsp
  </welcome-file>
</welcome-file-list>
{noformat}

Comment 1 Jiri Locker 2011-03-11 15:24:09 UTC
Of course, accessing http://hostname:9080/jboss-brms/index.jsp works fine.

Comment 2 Jiri Locker 2011-03-15 15:01:08 UTC
Link: Added: This issue is related to JBQA-4169


Comment 3 manstis 2011-08-17 22:00:25 UTC
This should have been resolved in 5.2.0 Drools project.

Comment 4 Ryan Zhang 2011-08-25 10:35:16 UTC
I also checked that this should be fixed in 5.2.0 BRMS.

Put this to ON_QA states.

Comment 5 lcarlon 2011-08-30 05:59:06 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
https://bugzilla.redhat.com/show_bug.cgi?id=724666

IBM WebSphere Application Server returned a 404 page not found error message when http://localhost:8080/jboss-brms/. The Drools component has been upgraded to 5.2 and the bug no longer presents.

Comment 6 lcarlon 2011-09-14 04:26:57 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,3 +1 @@
-https://bugzilla.redhat.com/show_bug.cgi?id=724666
-
 IBM WebSphere Application Server returned a 404 page not found error message when http://localhost:8080/jboss-brms/. The Drools component has been upgraded to 5.2 and the bug no longer presents.

Comment 7 Jiri Locker 2011-09-14 17:30:36 UTC
Fixed verified in ER4.

Comment 8 Jiri Locker 2011-09-15 14:45:00 UTC
(In reply to comment #7)
> Fixed verified in ER4.

ER4 was a typo, fix verified in ER3.

Comment 9 lcarlon 2011-10-05 05:16:38 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-IBM WebSphere Application Server returned a 404 page not found error message when http://localhost:8080/jboss-brms/. The Drools component has been upgraded to 5.2 and the bug no longer presents.+IBM WebSphere Application Server returned a '404 page not found' error message when users attempted to access http://localhost:8080/jboss-brms/. The Drools component has been upgraded to 5.2 and the bug no longer presents.

Comment 10 Amana 2013-02-13 17:00:26 UTC
Is it fixed on BRMS 5.3.1 ? I have one customer that has experienced this exactly error on BRMS 5.3.1 , webSphere 8.0.0.5.

Comment 11 Lukáš Petrovický 2013-02-14 09:18:58 UTC
It seems that the issue has indeed been verified as fixed. If you're the problem, please reopen. (But keep in mind that WAS 8 has never been certified so far.)

Comment 16 Red Hat Bugzilla 2025-02-10 03:13:57 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.