April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5793) Allow selective CI builds

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5793?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-5793: --------------------------------- Assignee: Ken Wills (was: Tomaz Cerar) > Allow selective CI builds > ------------------------- > > Key: WFLY-5793 > URL: https://issues.jboss.org/browse/WFLY-5793 > Project: WildFly > Issue Type: Enhancement > Reporter: Ryan Emerson > Assignee: Ken Wills > Priority: Optional > > Currently the testsuite is ran against all PRs regardless of which files are being changed. This is waste of energy/resources when commits only contain changes that do not effect code (e.g. when updating README.md). > A possible solution would be for a blacklist to be created, which lists the file types which can be safely ignored by CI when a PR only contains changes to files of the listed file types. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9477) Cannot create two hosts with unspecified default web module in Undertow

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9477?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-9477: --------------------------------- Assignee: (was: Tomaz Cerar) > Cannot create two hosts with unspecified default web module in Undertow > ----------------------------------------------------------------------- > > Key: WFLY-9477 > URL: https://issues.jboss.org/browse/WFLY-9477 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 11.0.0.Final > Reporter: Tomaz Cerar > Priority: Minor > > As a user, I cannot create two hosts with unspecified default web module. Currently the default-web-module is checked only for uniqueness and by default there is defined ROOT.war, which by default doesn't exist. Current behavior is that in case of non existing module defined by default-web-module, when accessing the root context ('/'), the content defined as part of welcome-file handler is provided. > As a user I should not be forced to put random values to avoid duplicity check, when I don't want to have set default-web-module. As such the default-web-module should have undefined default which could be checked and avoided failures due duplicates as there are in reality none. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10037) QS Ejb-security-jaas admin authorisation exception

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10037?page=com.atlassian.jira.plugin... ] Tomaz Cerar reassigned WFLY-10037: ---------------------------------- Assignee: Sande Gilda (was: Tomaz Cerar) > QS Ejb-security-jaas admin authorisation exception > -------------------------------------------------- > > Key: WFLY-10037 > URL: https://issues.jboss.org/browse/WFLY-10037 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 13.0.0.Beta1 > Reporter: Jozef Cibik > Assignee: Sande Gilda > Priority: Minor > > The user authenticated in client/servlet doesn't have admin authorisation, therefore server throws a stacktrace in server logs when executing "mvn exec:exec" or accessing QS URL. > Readme should mention this exception in server log. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3307) Parameters passed to standalone.sh are not printed on startup

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3307?page=com.atlassian.jira.plugi... ] Tomaz Cerar reassigned WFCORE-3307: ----------------------------------- Assignee: James Perkins (was: Tomaz Cerar) > Parameters passed to standalone.sh are not printed on startup > ------------------------------------------------------------- > > Key: WFCORE-3307 > URL: https://issues.jboss.org/browse/WFCORE-3307 > Project: WildFly Core > Issue Type: Enhancement > Components: Scripts > Affects Versions: 3.0.3.Final > Environment: linux / windows > Reporter: kobogian hitis > Assignee: James Perkins > Priority: Minor > > Parameters passed to standalone.sh should also be printed on startup (like JAVA_OPTS). > Actually I think something like the output of `ps aux | grep "org.jboss.as.standalone"` should also be printed, when jboss starts. > Not printing them causes confusion between what is printed and what is actually applied. > If for example someone runs this: `standalone.sh -Djboss.socket.binding.port-offset=100` and at the same time `-Djboss.socket.binding.port-offset=0` exists in JAVA_OPTS, then the latter will be printed but the first will be used. > Someone might argue about setting only JAVA_OPTS before running standalone.sh. > The reason I avoid setting JAVA_OPTS is that if I set them before running standalone.sh, then the default Wildfly opts (-Djava.net.preferIPv4Stack=true" -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true") are never used, which causes other problems. This could be a bug byitself, but for now I consider it as expected behaviour. > So the most clean approach that I see for setting options in a single place (both with -D and custom flags (e.g. -b)) is appending them as params to standalone.sh (e.g. inside a wrapper script myapp-run.sh). > It should be possible however to be able to see them being printed somewhere. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1828) Make it easier to register add and remove handlers with customized definitions

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1828?page=com.atlassian.jira.plugi... ] Tomaz Cerar reassigned WFCORE-1828: ----------------------------------- Assignee: (was: Tomaz Cerar) > Make it easier to register add and remove handlers with customized definitions > ------------------------------------------------------------------------------ > > Key: WFCORE-1828 > URL: https://issues.jboss.org/browse/WFCORE-1828 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Priority: Minor > > The nice way to build up a ResourceDefinition is with the Parameters object. And that works well with most add and remove handlers where the RD when building up the MRR generates a definition for the handlers. > But in cases where there needs to be some customization of the add description (e.g. deployment(-overlay) add where the content param can have fields that are not used in the content attribute) then the only option is in some way or other to override registerOperations. That or have the add OSH implement DescriptionProvider. Which we don't want. ;) > Perhaps add setAddDescription/setRemoveDescription to Parameters, or > {code} > public interface SelfDescibingOperationStepHandler extends OperationStepHandler { > OperationDefinition getDefinition(); > } > {code} > Enhancing Parameters sound better. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9173) Update JavaMail to 1.6.0 (or newer)

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9173?page=com.atlassian.jira.plugin.... ] Tomaz Cerar resolved WFLY-9173. ------------------------------- Fix Version/s: 12.0.0.Final Resolution: Done > Update JavaMail to 1.6.0 (or newer) > ----------------------------------- > > Key: WFLY-9173 > URL: https://issues.jboss.org/browse/WFLY-9173 > Project: WildFly > Issue Type: Feature Request > Components: Mail > Affects Versions: 10.1.0.Final > Reporter: Rob Heine > Assignee: Tomaz Cerar > Priority: Minor > Fix For: 12.0.0.Final > > > JavaMail 1.6.0 has been released. Please integrate this version in WildFly (maybe it might find its way into WildFly-10.x :) ). > Source: https://github.com/javaee/javamail/releases -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9977) Redundant CONSOLE log handler adding in CLI scripts for messaging-clustering* QS

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9977?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-9977: --------------------------------- Assignee: (was: Tomaz Cerar) > Redundant CONSOLE log handler adding in CLI scripts for messaging-clustering* QS > -------------------------------------------------------------------------------- > > Key: WFLY-9977 > URL: https://issues.jboss.org/browse/WFLY-9977 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 12.0.0.Final > Reporter: Nikoleta Žiaková > > CLI scripts in messaging-clustering and messaging-clustering-singleton QS contain redundant step for adding CONSOLE log handler. They fails with: > {code} > Failure: WFLYCTL0212: Duplicate resource > {code} > The reason is that CONSOLE log handler is enabled by default. > Readme files mention adding the handler, too: > https://github.com/wildfly/quickstart/tree/master/messaging-clustering > https://github.com/wildfly/quickstart/tree/master/messaging-clustering-si... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4051) Use descriptive error message for duplicate host/context deployments

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4051?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-4051: --------------------------------- Assignee: (was: Tomaz Cerar) > Use descriptive error message for duplicate host/context deployments > -------------------------------------------------------------------- > > Key: WFLY-4051 > URL: https://issues.jboss.org/browse/WFLY-4051 > Project: WildFly > Issue Type: Enhancement > Components: Web (Undertow) > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Ferraro > Priority: Minor > > If a user attempts to deploy a web application to a host/context to which another application is deployed, this will fail for obvious reasons. > What isn't obvious is the error message. Currently, users will see a DuplicateServiceException. Ideally, the error message should indicate that another application is deployed for the same host and context path. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2925) Separate heap settings in standalone.conf and domain.conf from rest of JAVA_OPTS

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2925?page=com.atlassian.jira.plugi... ] Tomaz Cerar reassigned WFCORE-2925: ----------------------------------- Assignee: James Perkins (was: Tomaz Cerar) > Separate heap settings in standalone.conf and domain.conf from rest of JAVA_OPTS > -------------------------------------------------------------------------------- > > Key: WFCORE-2925 > URL: https://issues.jboss.org/browse/WFCORE-2925 > Project: WildFly Core > Issue Type: Enhancement > Components: Scripts > Reporter: Brian Stansberry > Assignee: James Perkins > > Let's do this: > {code} > if [ "x$JBOSS_JAVA_SIZING" = "x" ]; then > JBOSS_JAVA_SIZING="-Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m" > fi > if [ "x$JAVA_OPTS" = "x" ]; then > JAVA_OPTS="$JBOSS_JAVA_SIZING -Djava.net.preferIPv4Stack=true" > JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true" > else > echo "JAVA_OPTS already set in environment; overriding default settings with values: $JAVA_OPTS" > fi > {code} > That will allow users to easily control memory sizing by setting that specific env var externally while still relying on our defaults for all the other fussy stuff in JAVA_OPTS. > The JBOSS_JAVA_SIZING name was 20 secs of thought on my part. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7618) Fix code to not use default platform dependant encoding

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7618?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-7618: --------------------------------- Assignee: (was: Tomaz Cerar) > Fix code to not use default platform dependant encoding > ------------------------------------------------------- > > Key: WFLY-7618 > URL: https://issues.jboss.org/browse/WFLY-7618 > Project: WildFly > Issue Type: Task > Reporter: Rostislav Svoboda > > WFLY codebase depends in some cases on system default encoding. This should be fixed to use de facto standard UTF8. > This JIRA is followup of WFCORE-1510 in the main codebase. Main concern (proven by history too) is Windows. > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2018