June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2526) Domain mode passed unwanted sys props to spawned servers

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2526?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-2526: ---------------------------------- Fix Version/s: 3.0.0.Beta27 (was: 3.0.0.Beta26) > Domain mode passed unwanted sys props to spawned servers > -------------------------------------------------------- > > Key: WFCORE-2526 > URL: https://issues.jboss.org/browse/WFCORE-2526 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: John Mazzitelli > Priority: Critical > Fix For: 3.0.0.Beta27 > > > This is related to WFCORE-350, except the solution to that only involves filtering out some but not all unwanted sys props. > I would say the solution should involve any properties, not just jboss.server.xxx properties. > In my case, I'm trying to inject a javaagent into the host controller but I do NOT want the javaagent in the spawned servers. Because my javaagent uses JBoss Logging (JUL) I'm forced to pass in "-Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager" and > "-Djava.util.logging.manager=org.jboss.logmanager.LogManager" so the host controller can start up. > But these gets passed to the spawned servers and causes them to fail to boot up (because while my -javaagent command line argument isn't passed to their JVM, the -D sys props are and those combination of sys props are deadly without a JUL-enabled javaagent). > See: http://lists.jboss.org/pipermail/wildfly-dev/2017-March/005810.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2349) Add RemoteManagementPermission and RemoteJMXPermission checks for remote clients.

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2349?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-2349: ---------------------------------- Fix Version/s: 3.0.0.Beta27 (was: 3.0.0.Beta26) > Add RemoteManagementPermission and RemoteJMXPermission checks for remote clients. > --------------------------------------------------------------------------------- > > Key: WFCORE-2349 > URL: https://issues.jboss.org/browse/WFCORE-2349 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management, Security > Reporter: Darran Lofthouse > Fix For: 3.0.0.Beta27 > > > Other services such as EJB and transactions have a Remote*Permission to verify the remote client has the required permission to use that service - this should be repeated for the management related services to control what a remote client can and can not connect to. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2937) Upgrade to WildFly Elytron 1.1.0.Beta52

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2937?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-2937: ---------------------------------- Fix Version/s: 3.0.0.Beta26 > Upgrade to WildFly Elytron 1.1.0.Beta52 > --------------------------------------- > > Key: WFCORE-2937 > URL: https://issues.jboss.org/browse/WFCORE-2937 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Beta26 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8910) On Windows, when running standalone/Domain with the JAVA_HOME environment variable set (but pointing to an empty directory), JBoss EAP fails to start and does not give an error message.

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8910?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-8910: --------------------------------- Assignee: Durgesh Anaokar (was: Tomaz Cerar) > On Windows, when running standalone/Domain with the JAVA_HOME environment variable set (but pointing to an empty directory), JBoss EAP fails to start and does not give an error message. > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-8910 > URL: https://issues.jboss.org/browse/WFLY-8910 > Project: WildFly > Issue Type: Bug > Components: Scripts > Affects Versions: 11.0.0.Alpha1 > Environment: Windows > Reporter: Durgesh Anaokar > Assignee: Durgesh Anaokar > Priority: Minor > > On Windows 7, when running standalone.bat with the JAVA_HOME environment variable set (but pointing to an empty directory), JBoss EAP fails to start and does not give an error message. > On line 177 of the standalone.bat, a check is made to see if the JAVA_HOME variable points to a valid directory. If it does, it assumes this directory contains bin\java. If bin\java does not exist, the server fails to start and does not give a reason why. > expect to see an error message such as "%JAVA_HOME% path doesn't contain an executable at %JAVA_HOME%\bin\java" > Add additional checks in the standalone.conf to verify that %JAVA_HOME%\bin\java exists and warn if it does not. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8913) It is not possible to add cache store in infinispan subsystem

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-8913?page=com.atlassian.jira.plugin.... ] Paul Ferraro moved JBEAP-11439 to WFLY-8913: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8913 (was: JBEAP-11439) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering (was: Clustering) Affects Version/s: 11.0.0.Alpha1 (was: 7.1.0.DR19) Affects Testing: (was: Regression) > It is not possible to add cache store in infinispan subsystem > ------------------------------------------------------------- > > Key: WFLY-8913 > URL: https://issues.jboss.org/browse/WFLY-8913 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > Adding cache store to already created cache ends by failure even if it should succeed: > {code} > [standalone@localhost:9990 /] /subsystem=infinispan/cache-container=hibernate/invalidation-cache=foobar/store=STORE:add(class="org.infinispan.configuration.cache.SingleFileStoreConfigurationBuilder") > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service org.wildfly.clustering.infinispan.cache.store.hibernate.foobar is already registered", > "rolled-back" => true > } > {code} > This is a regression against 7.1.0.DR18. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8449) EJB contextData not sent back to client in response

by Fedor Gavrilov (JIRA)

[ https://issues.jboss.org/browse/WFLY-8449?page=com.atlassian.jira.plugin.... ] Fedor Gavrilov reopened WFLY-8449: ---------------------------------- The second requirement: "It should also possible to pass serializeable objects from the server side to the client if the invocation returns and have a client side interceptor to read that informations." is still not satisfied and needs another PR. > EJB contextData not sent back to client in response > --------------------------------------------------- > > Key: WFLY-8449 > URL: https://issues.jboss.org/browse/WFLY-8449 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Fedor Gavrilov > Assignee: Fedor Gavrilov > Labels: downstream_dependency, ejb > Fix For: 11.0.0.Beta1 > > > With former JBoss versions it was possible to pass context beside the method invocation from the client to the server and back. This was done via (AOP) interceptors. > Since AS7 and WildFly the only possibility is to pass such context from the client to the server. > It should also possible to pass serializeable objects from the server side to the client if the invocation returns and have a client side interceptor to read that informations. > This was used to return i.e. tracking or additional usefull informations. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8912) org/wildfly/iiop/openjdk/csiv2/ElytronSASClientInterceptor using API removed from Elytron

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8912?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-8912: ----------------------------------- Description: And EjbClientContextSetupProcessor > org/wildfly/iiop/openjdk/csiv2/ElytronSASClientInterceptor using API removed from Elytron > ----------------------------------------------------------------------------------------- > > Key: WFLY-8912 > URL: https://issues.jboss.org/browse/WFLY-8912 > Project: WildFly > Issue Type: Bug > Components: IIOP, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 11.0.0.Beta1 > > > And EjbClientContextSetupProcessor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1236) Release WildFly Elytron 1.1.0.Beta52

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1236?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1236. ----------------------------------- Resolution: Done > Release WildFly Elytron 1.1.0.Beta52 > ------------------------------------ > > Key: ELY-1236 > URL: https://issues.jboss.org/browse/ELY-1236 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta53 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1236) Release WildFly Elytron 1.1.0.Beta52

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1236?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1236: ---------------------------------- Fix Version/s: 1.1.0.Beta52 (was: 1.1.0.Beta53) > Release WildFly Elytron 1.1.0.Beta52 > ------------------------------------ > > Key: ELY-1236 > URL: https://issues.jboss.org/browse/ELY-1236 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta52 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8910) On Windows, when running standalone/Domain with the JAVA_HOME environment variable set (but pointing to an empty directory), JBoss EAP fails to start and does not give an error message.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-8910?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-8910: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1459769 Bugzilla Update: Perform > On Windows, when running standalone/Domain with the JAVA_HOME environment variable set (but pointing to an empty directory), JBoss EAP fails to start and does not give an error message. > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-8910 > URL: https://issues.jboss.org/browse/WFLY-8910 > Project: WildFly > Issue Type: Bug > Components: Scripts > Affects Versions: 11.0.0.Alpha1 > Environment: Windows > Reporter: Durgesh Anaokar > Assignee: Tomaz Cerar > Priority: Minor > > On Windows 7, when running standalone.bat with the JAVA_HOME environment variable set (but pointing to an empty directory), JBoss EAP fails to start and does not give an error message. > On line 177 of the standalone.bat, a check is made to see if the JAVA_HOME variable points to a valid directory. If it does, it assumes this directory contains bin\java. If bin\java does not exist, the server fails to start and does not give a reason why. > expect to see an error message such as "%JAVA_HOME% path doesn't contain an executable at %JAVA_HOME%\bin\java" > Add additional checks in the standalone.conf to verify that %JAVA_HOME%\bin\java exists and warn if it does not. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2017