[DOCU-1017] Update JBoss WildFly deployment instructions Created: 10/May/17  Updated: 14/May/18  Resolved: 09/Oct/17

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: 5.5
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Richard Gange Assignee: Richard Gange
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File wildfly-8.0-libs.txt    
Issue Links:
relation
is related to MGNLPN-371 NotSerializableException for VariantM... Closed
is related to MGNLCE-95 Cannot start Magnolia 5.5 on Wildfly 8 Closed
is related to MGNLCE-97 Cannot start Magnolia 5.5 on EAP 6.4 Closed
is related to MGNLREST-86 RESTEasy 3.0.19.Final has issue, REST... Closed
is related to MGNLUI-2652 Serialisation issue with Admincentral... Closed
is related to MGNLUI-4211 Vaadin HEARTBEAT causes null pointer ... Closed
is related to DOCU-696 Update JBoss AS configuration Page Closed
is related to MGNLEE-429 Include all quirks and config changes... Closed
supersession
supersedes DOCU-695 Update page "JBoss AS configuration" ... Closed

 Description   

Currently in the certified stack we list:

Wildfly 8 and later
JBoss EAP 6.3.3 and later



 Comments   
Comment by Richard Gange [ 10/May/17 ]

WFly 8 - RESTEasy 3.0.6.Final
WFly 10.0 - RESTEasy 3.0.14.Final
WFly 10.1 - RESTEasy 3.0.19.Final
WFly 11.0 Alpha1 - RESTEasy 3.0.21.Final

EAP 6.3.3 - RESTEasy 2.3.8.Final
EAP 6.4 - RESTEasy 2.3.10.Final

EAP 7.0 - RESTEasy 3.0.19.SP1
EAP 7.1 - RESTEasy 3.0.21.Final

Magnolia 5.5 - RESTEasy 3.0.19.Final
Magnolia 5.4 - RESTEasy 3.0.4.Final

Comment by Richard Gange [ 12/May/17 ]

Only the RESTEasy version that is shipped with the EAP will be supported in both production and development environment. Replacing the libraries or using a different version of RESTEasy than what we ship will be considered as a third party deployment and will not be supported

Source: https://developer.jboss.org/thread/262213

Comment by Richard Gange [ 12/May/17 ]

Another important note. The cache browser app uses our rest client modules:

[INFO] |  |  |  +- info.magnolia.cache:magnolia-cache-browser-app:jar:5.5.3:compile
[INFO] |  |  |  |  +- info.magnolia.restclient:magnolia-resteasy-client:jar:1.1.1:compile
[INFO] |  |  |  |  |  +- info.magnolia.restclient:magnolia-rest-client:jar:1.1.1:compile
[INFO] |  |  |  |  |  \- org.jboss.resteasy:resteasy-jackson2-provider:jar:3.0.19.Final:compile
Comment by Richard Gange [ 16/May/17 ]

Magnolia 5.5.4 + Wildfly 10.1

  1. weld subsystem exclusion in jboss-deployment-descriptor.xml in folder WEB-INF.
  2. log4j exclusions in jboss-deployment-descriptor.xml in folder WEB-INF.
    <?xml version="1.0"?>
    <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
        <deployment>
            <exclude-subsystems>
                <subsystem name="weld" />
            </exclude-subsystems>
            <exclusions>
                <module name="org.apache.log4j" />
                <module name="org.slf4j" />
            </exclusions>
        </deployment>
    </jboss-deployment-structure>
    
  3. Configure JAAS Login in standalone.xml.
    <subsystem xmlns="urn:jboss:domain:security:1.2">
    	<security-domains>
    		<security-domain name="magnolia" cache-type="default">
    			<authentication>
    				<login-module code="info.magnolia.jaas.sp.jcr.JCRAuthenticationModule"
    					flag="requisite" />
    				<login-module code="info.magnolia.jaas.sp.jcr.JCRAuthorizationModule"
    					flag="required" />
    			</authentication>
    		</security-domain>
    		<security-domain name="Jackrabbit" cache-type="default">
    			<authentication>
    				<login-module
    					code="org.apache.jackrabbit.core.security.SimpleLoginModule" flag="required" />
    			</authentication>
    		</security-domain>
    		<security-domain name="other" cache-type="default">
    			<authentication>
    				<login-module
    					code="org.apache.jackrabbit.core.security.SimpleLoginModule" flag="required" />
    			</authentication>
    		</security-domain>
    	</security-domains>
    </subsystem>
    
Comment by Christoph Meier [ 19/Oct/17 ]

rgange - If you need a review, ask somebody from support or services (e.g. miruela?). I have no glue about the details here.
Otherwise please close the ticket.

Comment by Rajeev Singh [ 12/May/18 ]

Hi Richard,

Do you think it can be root cause for https://jira.magnolia-cms.com/browse/SUPPORT-8669 ?
Meaning 5.5.10 could fail on JBoss EAP 6.4.10.GA (AS 7.5.10.Final-redhat-2) ? 

Request you to let me know in case you have any inputs.

I believe @Mercedes Iruela will also be trying to check from her end. 

Thanks in advance. 

Regards,

Rajeev

Comment by Richard Gange [ 13/May/18 ]

Hi rajeevsingh-

I did at one time try to deploy Magnolia 5.5 on JBoss 6.4 and was not successful. Therefore I made a recommendation that we change the Certified Stack to be JBoss EAP 7.0 and later for Magnolia 5.5. My investigation was recorded here MGNLCE-97. For that reason, I would have to agree with Mercedes assessment that you should upgrade your server.

HTH
Rich

Comment by Rajeev Singh [ 14/May/18 ]

Hello Richard,

Good morning, thank your for the confirmation. I will try to upgrade jboss and continue ivestigation.

Thanks once again. 

Best Regards,

Rajeev

Generated at Mon Feb 12 01:14:24 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.