November 2019 - wildfly-dev - Jboss List Archives

by Nouman, Lutfi (SSC/SPC)

Hi all, I have a server build that requires Wildfly application. The OS that I will be using is SLES 12 SP 2. Does Wildfly support SLES 12 SP 2? I have contacted SUSE Customer support and they unfamiliar with wildfly, they do not provide wildfly nor support. They did mention that it should work with SLES without issues but they have not tried it. When I downloaded the Wildfly 18 package to see what contents lie in there something came up. I believe you have scripts in the init.d folder for debian and red hat but not for SLES. I also found an old forum of a user explaining in order to start and stop wildfly a script is needed. Could you please give me some insight or more information? Thank you for your time and effort on this matter. Kind Regards, Lutfi Nouman Support Technician z/VM, Data Center Services Branch Shared Services Canada / Government of Canada lutfi.nouman(a)canada.ca<mailto:lutfi.nouman@canada.ca> / Tel: 343-543-5092 Technicien Informatique z/VM, Direction Générale des Services de Centres de Données Services partagés Canada / Gouvernement du Canada lutfi.nouman(a)canada.ca<mailto:naoufel.chbihi@canada.ca> / Tél : 343-543-5092 [ssc-signature-block]

5 years

3
3
0 / 0

Log in to issues.jboss.org broken

by Dominik Derwiński

I had a JBoss account, but it now redirects to Red Hat account login. Red Hat registration/login sadly fails, after it wants me to agree to Enterprise Agreement and Developer Program Terms & Conditions it crashes with internal server error. I'm unable to post a bug report about WildFly. Regards, Dominik Derwiński

5 years

2
4
0 / 0

Where is jboss fork of Jakarta EE transactions spec?

by Matej Novotny

Hello, I was switching some artifacts from old java EE to their (so much better) Jakarta counterparts and I know we have some forks located under https://github.com/jboss. However, I couldn't locate up-to-date version of transactions api fork, the one we have there is https://github.com/jboss/jboss-transaction-api_spec which was last modified in 2017. Yet looking in WFLY POM, I can see that it uses a newer version of the same dependency - https://github.com/wildfly/wildfly/blob/master/pom.xml#L7181-L7185 Does anyone know if it was placed into another repository? Or perhaps mistakenly not pushed into the repository? Regards Matej

5 years

2
2
0 / 0

Jira components for MicroProfile

by Radoslav Husar

Hello Jira admins whoever you are, Out current Jira components for MicroProfile are a bit messy [1]. 1) We are missing MicroProfile Jira components for OpenAPI, Fault Tolerance, JWT, etc. These need to be added with corresponding owners. 2) The existing components are unnecessarily abbreviated, please rename "MP Config" and alike to "MicroProfile Config" to make them easier to find. 3) The existing component descriptions are a bit mangled, e.g. "MIcroprofile" or "Microprofile". 4) Do we need a "catchall" MicroProfile component for issues not specific to any spec, e.g. [2], [3]? Thanks! Rado PS: As always, I am happy to do it if given admin access ;-) [1] https://issues.jboss.org/projects/WFLY?selectedItem=com.atlassian.jira.ji... [2] https://issues.jboss.org/browse/WFLY-12757 [3] https://issues.jboss.org/browse/WFLY-12681

5 years

3
4
0 / 0

Possible component upgrades report - Elytron Web

by thofman＠redhat.com

5 years

1
0
0 / 0

Possible component upgrades report - Wildfly Elytron

by thofman＠redhat.com

5 years

1
0
0 / 0

Possible component upgrades report - Wildfly Core

by thofman＠redhat.com

5 years

1
0
0 / 0

Possible component upgrades report - Wildfly

by thofman＠redhat.com

5 years

1
0
0 / 0

Add pull request CI coverage of Galleon layers, drop Windows JDK 8

by Brian Stansberry

I'd like to add jobs to the automatic testing of PRs to run the testsuite using slimmed installations provisioned by Galleon. But, we already run a lot of jobs for each PR, enough so that our CI can overburdened during busy times around deadlines. So I don't want to just add jobs. Instead I also propose to drop the Windows + JDK 8 jobs. Galleon Testing During our work on WildFly 18 I added the ability to run portions of the WildFly and WildFly Core testsuites with the tests executing against slimmed server installations provisioned by Galleon instead of against the complete installations normally used. The point of that was to get test coverage of those slimmed installations. Currently we have nightly jobs that run the testsuite this way.[1] As we continue to evolve our set of Galleon layers, e.g. adding layers for MicroProfile specs, I want to be sure we catch problems before PRs get merged. To run tests locally this way you pass -Dts.layers as an arg to maven. Dropping Windows JDK 8 Jobs If we'd drop something in order to free up resources for these Galleon jobs, the Windows JDK 8 ones seem a good choice. We'd still run PRs against Windows JDK 11, and we'd still run PRs against Linux JDK 8. I can't recall any situation where CI found a regression that was specific to the Windows + JDK 8 combination. When CI gets overloaded during rush times, it's the Windows jobs that are most problematic. The Windows jobs take longer because the storage drives they use are slower. Plus we have fewer Windows agents. The effect is during a rush, overall CI for PRs ends up taking hours longer while we wait for Windows agents to come free and then run the job. We'd still run nightly jobs with Windows + JDK 8 so in the off chance there's a problem it would get noticed that way. Specifics For PRs against wildfly/wildfly I'd add a job equivalent to https://ci.wildfly.org/viewType.html?buildTypeId=WF_GalleonLinuxJdk11 and then drop https://ci.wildfly.org/viewType.html?buildTypeId=WildFlyCore_PullRequestW... For PRs against wildfly/wildfly-core I'd add jobs equivalent to https://ci.wildfly.org/viewType.html?buildTypeId=WildFlyCore_GalleonLinux... and https://ci.wildfly.org/viewType.html?buildTypeId=WF_GalleonLinuxJdk8 and then drop https://ci.wildfly.org/viewType.html?buildTypeId=WildFlyCore_PullRequestW... Any thoughts on this? Best regards, Brian [1] See https://ci.wildfly.org/viewType.html?buildTypeId=WF_GalleonLinuxJdk11 https://ci.wildfly.org/viewType.html?buildTypeId=WF_GalleonLinuxJdk8 https://ci.wildfly.org/viewType.html?buildTypeId=WF_GalleonWindowsJdk11 https://ci.wildfly.org/viewType.html?buildTypeId=WildFlyCore_GalleonLinux... https://ci.wildfly.org/viewType.html?buildTypeId=WildFlyCore_GalleonLinux...

5 years

4
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

wildfly-dev November 2019