Bug 1223081 - [GSS](6.4.z) Don't reload jsp after redeploy application in Domain Mode
Summary: [GSS](6.4.z) Don't reload jsp after redeploy application in Domain Mode
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.4
Assignee: Chao Wang
QA Contact: Martin Simka
URL:
Whiteboard:
: 1232061 (view as bug list)
Depends On:
Blocks: 1227556 1235744
TreeView+ depends on / blocked
 
Reported: 2015-05-19 18:37 UTC by Jose Roman Martin Gil
Modified: 2019-08-15 04:36 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1220246 0 unspecified CLOSED [GSS](6.4.z) In Domain mode application replaced via console is not in enabled mode by default 2021-02-22 00:41:40 UTC

Internal Links: 1220246

Description Jose Roman Martin Gil 2015-05-19 18:37:41 UTC
Description of problem:
JBoss EAP in Standalone Mode reload JSP when you redeploy a new version of a application, however JBoss EAP in Domain Mode do that only when you restart the server group where the application is assigned.

In both cases the development attribute in web subsystem is defined as false. 

<subsystem xmlns="urn:jboss:domain:web:2.2" default-virtual-server="default-host" native="false">
                <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/>
                <virtual-server name="default-host" enable-welcome-root="true">
                    <alias name="localhost"/>
                    <alias name="example.com"/>
                </virtual-server>
</subsystem>

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Starts JBoss EAP in Domain Mode
2. Starts a Server Group 
3. Deploy a new Web Application with a index.jsp file with title "version 1.0"
4. Test the application v.1.0 
5. Change title "version 2.0" in index.jsp file
6. Redeploy the application 
7. Test the application v.2.0

Actual results:
The title showed is "version 1.0"

Expected results:
The title must be "version 2.0"

Additional info:
Only when the server group is restarted then "version 2.0" is showed.

There is a KCS (https://access.redhat.com/solutions/334963) with a solution about that: activate development attribute. However it is not recommended for a production environment. 

It is not a solution activate it because it is needed to be applied in a production environment.

The right behaviour is do the same as in Standalone Mode (with out restart servers).

Comment 13 Chao Wang 2015-06-16 01:43:03 UTC
*** Bug 1232061 has been marked as a duplicate of this bug. ***

Comment 14 Martin Simka 2015-09-24 10:59:14 UTC
verified with EAP 6.4.4.CP.CR3

Comment 15 Petr Penicka 2017-01-17 10:50:43 UTC
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.

Comment 16 Petr Penicka 2017-01-17 10:51:06 UTC
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.


Note You need to log in before you can comment on or make changes to this bug.