November 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9574) Distribution files does not have POSIX permissions perfectly set

by Romain Pelisse (JIRA)

[ https://issues.jboss.org/browse/WFLY-9574?page=com.atlassian.jira.plugin.... ] Romain Pelisse updated WFLY-9574: --------------------------------- Description: The server provisioning copy (and extract) files in order to assemble the distribution based the information of the feature-pack. While doing so on a POSIX system, it keeps the permissions of the original files, which are not always optimum (see JBEAP-12374). Specifically, .properties and .jar files are associated with the mask rw-rw-r-- giving access to it to any other and allowing group member to modify the file ; On a "regular" Maven project, all of those changes could be specified in the assembly.xml, however in Wildfly cases, this is not really option because the provisioning-maven-plugin and feature-pack-build-maven-plugin are manipulating the content of the archive being built. Also, using assembly.xml would mean edit and update the 4 or 5 different assembly.xml in the project directory tree. I plan thus to propose a fix for wildfly-build-tools to address all those (small) problems. was: The server provisioning copy (and extract) files in order to assemble the distribution based the information of the feature-pack. While doing so on a POSIX system, it keeps the permissions of the original files, which are not always optimum (see JBEAP-12374). For instance: * .properties and .jar files are associated with the mask rw-rw-r-- giving access to it to any other and allowing group member to modify the file ; * some directories like domain/tmp/auth have to restrictive mask like rwx------ that needs to be turned into rwxrwxr-x and other, likes domain have again a too permissive mask rwxrwxr-x (should be rwxr-xr-x). On a "regular" Maven project, all of those changes could be specified in the assembly.xml, however in Wildfly cases, this is not really option because the provisioning-maven-plugin and feature-pack-build-maven-plugin are manipulating the content of the archive being built. Also, using assembly.xml would mean edit and update the 4 or 5 different assembly.xml in the project directory tree. I plan thus to propose a fix for wildfly-build-tools to address all those (small) problems. > Distribution files does not have POSIX permissions perfectly set > ---------------------------------------------------------------- > > Key: WFLY-9574 > URL: https://issues.jboss.org/browse/WFLY-9574 > Project: WildFly > Issue Type: Enhancement > Components: Build System > Affects Versions: 11.0.0.Final > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Priority: Minor > > The server provisioning copy (and extract) files in order to assemble the distribution based the information of the feature-pack. > While doing so on a POSIX system, it keeps the permissions of the original files, which are not always optimum (see JBEAP-12374). Specifically, .properties and .jar files are associated with the mask rw-rw-r-- giving access to it to any other and allowing group member to modify the file ; > On a "regular" Maven project, all of those changes could be specified in the assembly.xml, however in Wildfly cases, this is not really option because the provisioning-maven-plugin and feature-pack-build-maven-plugin are manipulating the content of the archive being built. Also, using assembly.xml would mean edit and update the 4 or 5 different assembly.xml in the project directory tree. > I plan thus to propose a fix for wildfly-build-tools to address all those (small) problems. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9568) Test case for WFCORE-1392 - Undeploy doesn't remove Data content if server is in --admin-only mode

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFLY-9568?page=com.atlassian.jira.plugin.... ] Tomas Hofman closed WFLY-9568. ------------------------------ Resolution: Won't Do Closing, test will be implemented in core. > Test case for WFCORE-1392 - Undeploy doesn't remove Data content if server is in --admin-only mode > --------------------------------------------------------------------------------------------------- > > Key: WFLY-9568 > URL: https://issues.jboss.org/browse/WFLY-9568 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Tomas Hofman > Assignee: Tomas Hofman > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9583) Drop org.jboss.as.test.clustering.single.jdbcstore.TransactionalJdbcStoreTestCase

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9583?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9583: --------------------------------- Description: While the behaviour verification belongs to Infinspan rather than the AS, the dependent Jira is rejected https://issues.jboss.org/browse/ISPN-604. (was: The dependent Jira is rejected https://issues.jboss.org/browse/ISPN-604) > Drop org.jboss.as.test.clustering.single.jdbcstore.TransactionalJdbcStoreTestCase > --------------------------------------------------------------------------------- > > Key: WFLY-9583 > URL: https://issues.jboss.org/browse/WFLY-9583 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 12.0.0.Alpha1 > > > While the behaviour verification belongs to Infinspan rather than the AS, the dependent Jira is rejected https://issues.jboss.org/browse/ISPN-604. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9583) Drop org.jboss.as.test.clustering.single.jdbcstore.TransactionalJdbcStoreTestCase

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9583?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9583: --------------------------------- Fix Version/s: 12.0.0.Alpha1 > Drop org.jboss.as.test.clustering.single.jdbcstore.TransactionalJdbcStoreTestCase > --------------------------------------------------------------------------------- > > Key: WFLY-9583 > URL: https://issues.jboss.org/browse/WFLY-9583 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 12.0.0.Alpha1 > > > While the behaviour verification belongs to Infinspan rather than the AS, the dependent Jira is rejected https://issues.jboss.org/browse/ISPN-604. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9583) Drop org.jboss.as.test.clustering.single.jdbcstore.TransactionalJdbcStoreTestCase

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-9583: ------------------------------------ Summary: Drop org.jboss.as.test.clustering.single.jdbcstore.TransactionalJdbcStoreTestCase Key: WFLY-9583 URL: https://issues.jboss.org/browse/WFLY-9583 Project: WildFly Issue Type: Task Components: Clustering, Test Suite Reporter: Radoslav Husar Assignee: Radoslav Husar The dependent Jira is rejected https://issues.jboss.org/browse/ISPN-604 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2146) kie-maven-plugin does not include package in error messages

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2146?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-2146: -------------------------------- Sprint: 2017 Week 47-48 > kie-maven-plugin does not include package in error messages > ----------------------------------------------------------- > > Key: DROOLS-2146 > URL: https://issues.jboss.org/browse/DROOLS-2146 > Project: Drools > Issue Type: Bug > Reporter: Alexandre Porcelli > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2237) The single node in the cluster not become a coordinator after coordinator leave.

by kfir avraham (JIRA)

[ https://issues.jboss.org/browse/JGRP-2237?page=com.atlassian.jira.plugin.... ] kfir avraham commented on JGRP-2237: ------------------------------------ i attached another logs in trace mode, you can see from 'Nov-29-2017 *+00:24:08+* GMT-12:00 [org.jgroups.protocols.TCP] [TcpServer.Acceptor[8102]-5,clm-tlv-spih62-62502] [TRACE] - 10.63.16.13:8102: rejected connection from 10.63.16.3:8102 (connection existed and my address won as it's higher)' > The single node in the cluster not become a coordinator after coordinator leave. > -------------------------------------------------------------------------------- > > Key: JGRP-2237 > URL: https://issues.jboss.org/browse/JGRP-2237 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.2, 4.0.8 > Reporter: kfir avraham > Assignee: Bela Ban > Priority: Minor > Attachments: Server_A.txt, Server_A_Trace_mode.rtf, Server_B.txt, Server_B_Trace_mode.rtf, conf.txt, test.xml > > > I got cluster with 2 members, sometimes when the first node (coordinator) leave the cluster the second one is not become a coordinator. > When the first one is rejoin, he could not determine coordinator and select new one from the nodes list. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2237) The single node in the cluster not become a coordinator after coordinator leave.

by kfir avraham (JIRA)

[ https://issues.jboss.org/browse/JGRP-2237?page=com.atlassian.jira.plugin.... ] kfir avraham updated JGRP-2237: ------------------------------- Attachment: Server_A_Trace_mode.rtf Server_B_Trace_mode.rtf > The single node in the cluster not become a coordinator after coordinator leave. > -------------------------------------------------------------------------------- > > Key: JGRP-2237 > URL: https://issues.jboss.org/browse/JGRP-2237 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.2, 4.0.8 > Reporter: kfir avraham > Assignee: Bela Ban > Priority: Minor > Attachments: Server_A.txt, Server_A_Trace_mode.rtf, Server_B.txt, Server_B_Trace_mode.rtf, conf.txt, test.xml > > > I got cluster with 2 members, sometimes when the first node (coordinator) leave the cluster the second one is not become a coordinator. > When the first one is rejoin, he could not determine coordinator and select new one from the nodes list. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9582) server not starting from windows service

by Cheng Fang (JIRA)

[ https://issues.jboss.org/browse/WFLY-9582?page=com.atlassian.jira.plugin.... ] Cheng Fang updated WFLY-9582: ----------------------------- Component/s: (was: Batch) > server not starting from windows service > ---------------------------------------- > > Key: WFLY-9582 > URL: https://issues.jboss.org/browse/WFLY-9582 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 9.0.2.Final > Environment: Window 7 64-bit system > Reporter: Roshan Royal > Assignee: Cheng Fang > Priority: Blocker > > Getting below error while trying to start server through windows service. > [2017-11-29 14:24:47] [info] [14908] Commons Daemon procrun (1.0.15.0 64-bit) started > [2017-11-29 14:24:47] [info] [14908] Starting service 'Wildfly' ... > [2017-11-29 14:24:47] [info] [ 3760] Commons Daemon procrun (1.0.15.0 64-bit) started > [2017-11-29 14:24:47] [info] [ 3760] Running 'Wildfly' Service... > [2017-11-29 14:24:47] [info] [15500] Starting service... > [2017-11-29 14:24:47] [info] [15500] Service started in 3 ms. > [2017-11-29 14:24:47] [info] [ 3760] Run service finished. > [2017-11-29 14:24:47] [info] [ 3760] Commons Daemon procrun finished > [2017-11-29 14:24:48] [error] [14908] Failed to start 'Wildfly' service > [2017-11-29 14:24:48] [error] [14908] The data area passed to a system call is too small. > [2017-11-29 14:24:48] [info] [14908] Start service finished. > [2017-11-29 14:24:48] [error] [14908] Commons Daemon procrun failed with exit value: 5 (Failed to start service) > [2017-11-29 14:24:48] [error] [14908] The data area passed to a system call is too small. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9582) server not starting from windows service

by Cheng Fang (JIRA)

[ https://issues.jboss.org/browse/WFLY-9582?page=com.atlassian.jira.plugin.... ] Cheng Fang reassigned WFLY-9582: -------------------------------- Assignee: Tomaz Cerar (was: Cheng Fang) > server not starting from windows service > ---------------------------------------- > > Key: WFLY-9582 > URL: https://issues.jboss.org/browse/WFLY-9582 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 9.0.2.Final > Environment: Window 7 64-bit system > Reporter: Roshan Royal > Assignee: Tomaz Cerar > Priority: Blocker > > Getting below error while trying to start server through windows service. > [2017-11-29 14:24:47] [info] [14908] Commons Daemon procrun (1.0.15.0 64-bit) started > [2017-11-29 14:24:47] [info] [14908] Starting service 'Wildfly' ... > [2017-11-29 14:24:47] [info] [ 3760] Commons Daemon procrun (1.0.15.0 64-bit) started > [2017-11-29 14:24:47] [info] [ 3760] Running 'Wildfly' Service... > [2017-11-29 14:24:47] [info] [15500] Starting service... > [2017-11-29 14:24:47] [info] [15500] Service started in 3 ms. > [2017-11-29 14:24:47] [info] [ 3760] Run service finished. > [2017-11-29 14:24:47] [info] [ 3760] Commons Daemon procrun finished > [2017-11-29 14:24:48] [error] [14908] Failed to start 'Wildfly' service > [2017-11-29 14:24:48] [error] [14908] The data area passed to a system call is too small. > [2017-11-29 14:24:48] [info] [14908] Start service finished. > [2017-11-29 14:24:48] [error] [14908] Commons Daemon procrun failed with exit value: 5 (Failed to start service) > [2017-11-29 14:24:48] [error] [14908] The data area passed to a system call is too small. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2017