I hereby claim:
- I am ctomc on github.
- I am ctomc (https://keybase.io/ctomc) on keybase.
- I have a public key ASD-0wM5gtF-mlFGsL2TQZP96NiAJFIvW-97ad2d-nT8hwo
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
/* | |
* JBoss, Home of Professional Open Source | |
* Copyright 2017, Red Hat, Inc., and individual contributors as indicated | |
* by the @authors tag. | |
* | |
* Licensed under the Apache License, Version 2.0 (the "License"); | |
* you may not use this file except in compliance with the License. | |
* You may obtain a copy of the License at | |
* | |
* http://www.apache.org/licenses/LICENSE-2.0 |
This agreement is between you and Red Hat, Inc. ("Red Hat"). In this agreement, "You" shall mean the owner of the Contribution, as defined below, including any individual or any corporation or entity which has authorized the signatory of this agreement to act on its behalf. The purpose of this license is to set forth the terms and conditions under which we may use software that you wish to contribute to us for the purpose of use within one or more of our software development projects. Nothing in this license changes your ongoing right to use your contributions as you wish for any purpose. | |
By clicking the Sign button below, I hereby agree to the following terms and conditions: | |
As used in this agreement, the term "Contribution" shall mean any software, including source code and/or object code, documentation, or modifications to the foregoing, which You make available or submit to Red Hat in any form. Contributions shall not include any software or documentation which has been explicitly marked to indicate |
Title: Building a Custom Trimmed Down WildFly Distribution | |
Abstract: | |
WildFly is a very versatile, highly modular enterprise class application server with very small core footprint, and various capabilities added to it by way of extensions, also known as subsystems. | |
Not every application requires the full set of Java EE 7 APIs, or clustering with centralized management, and thanks to its modular design it’s not so difficult to create a custom distribution of the server. | |
In cloud environments resources like disk space and memory are scarce, so trimming down or assembling a custom distribution of the server can come handy. | |
WildFly 9 comes with completely new set of build assembly tools that allow us to provide different distributions like core, web & full to suite user's needs better. | |
In this talk we will take a look at: |
hw: | |
1x 4 core cpu | |
configuration: | |
MaxFileDescriptorCount set to 4096 | |
<worker name="default" /> | |
<worker name="second-worker"/> | |
<worker name="third-worker" task-max-threads="50"/> |
location / { | |
index index.html index.htm; | |
proxy_set_header Host $host; | |
proxy_set_header SSL_SESSION_ID $ssl_session_id; | |
proxy_set_header SSL_CLIENT_CERT $ssl_client_cert; | |
proxy_set_header SSL_CIPHER $ssl_cipher | |
proxy_pass http://localhost:8080; | |
} |
Enter legacy AS version: 7.1.3.Final | |
Using target model: 7.1.3.Final | |
Enter type [S](standalone)/H(host)/D(domain)/F(domain + host):S | |
Read from target directory or from the legacy-models directory - t/[l]: | |
Report on differences in the model when the management versions are different? y/[n]: y | |
Reporting on differences in the model when the management versions are different | |
Loading legacy model versions for 7.1.3.Final.... | |
Loaded legacy model versions | |
Loading model versions for currently running server... |
<subsystem xmlns="urn:jboss:domain:undertow:1.0"> | |
<worker name="default" task-core-threads="12" io-threads="3"/> | |
<buffer-pool name="default" buffer-size="1024" buffers-per-slice="1024"/> | |
<virtual-host default-host="localhost"> | |
<http-listener name="default" socket-binding="http" worker="default" buffer-pool="default"/> | |
<ajp-listener name="ajp-connector" socket-binding="ajp"/> | |
<handlers> |