December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7724) Wildly 10 Freeze no able to ping, nothing happening in logs

by Rohit Lakshykar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7724?page=com.atlassian.jira.plugin.... ] Rohit Lakshykar updated WFLY-7724: ---------------------------------- Description: I am using wildfy 10 sever for financial production machine since more then 8 month. I have never faced any issue till yet. From the last few days in every 2 days wildfly server stop responding, even server.log got stopped. And i can't see any exception, in logs too. I don't know what this is started happening suddenly. Please somebody help me. was: I am using wildfy 10 sever for financial production machine since more then 8 month. I have never faced any issue till yet. From the last few days in every 2 days wildfly server stop responding, even server.log got stopped. And i can't see any exception, in logs too. I don't know what this is stared happening suddenly. Please somebody help me. > Wildly 10 Freeze no able to ping, nothing happening in logs > ------------------------------------------------------------ > > Key: WFLY-7724 > URL: https://issues.jboss.org/browse/WFLY-7724 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.Final > Reporter: Rohit Lakshykar > Assignee: Jason Greene > Priority: Blocker > > I am using wildfy 10 sever for financial production machine since more then 8 month. > I have never faced any issue till yet. From the last few days in every 2 days wildfly server stop responding, even server.log got stopped. > And i can't see any exception, in logs too. I don't know what this is started happening suddenly. > Please somebody help me. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7724) Wildly 10 Freeze no able to ping, nothing happening in logs

by Rohit Lakshykar (JIRA)

Rohit Lakshykar created WFLY-7724: ------------------------------------- Summary: Wildly 10 Freeze no able to ping, nothing happening in logs Key: WFLY-7724 URL: https://issues.jboss.org/browse/WFLY-7724 Project: WildFly Issue Type: Bug Affects Versions: 10.0.0.Final Reporter: Rohit Lakshykar Assignee: Jason Greene Priority: Blocker I am using wildfy 10 sever for financial production machine since more then 8 month. I have never faced any issue till yet. From the last few days in every 2 days wildfly server stop responding, even server.log got stopped. And i can't see any exception, in logs too. I don't know what this is stared happening suddenly. Please somebody help me. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-807) Minor fixes to client configuration schema and parsing

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-807?page=com.atlassian.jira.plugin.sy... ] Pedro Igor updated ELY-807: --------------------------- Affects Version/s: 1.1.0.Beta17 > Minor fixes to client configuration schema and parsing > ------------------------------------------------------ > > Key: ELY-807 > URL: https://issues.jboss.org/browse/ELY-807 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Affects Versions: 1.1.0.Beta17 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.Beta17 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-807) Minor fixes to client configuration schema and parsing

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-807?page=com.atlassian.jira.plugin.sy... ] Pedro Igor updated ELY-807: --------------------------- Fix Version/s: 1.1.0.Beta17 > Minor fixes to client configuration schema and parsing > ------------------------------------------------------ > > Key: ELY-807 > URL: https://issues.jboss.org/browse/ELY-807 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Affects Versions: 1.1.0.Beta17 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.Beta17 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-807) Minor fixes to client configuration schema and parsing

by Pedro Igor (JIRA)

Pedro Igor created ELY-807: ------------------------------ Summary: Minor fixes to client configuration schema and parsing Key: ELY-807 URL: https://issues.jboss.org/browse/ELY-807 Project: WildFly Elytron Issue Type: Bug Components: Authentication Client Reporter: Pedro Igor Assignee: Pedro Igor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2080) WildFlyElytronProvider should only be created once

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2080?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2080: ------------------------------------- Fix Version/s: 3.0.0.Alpha15 > WildFlyElytronProvider should only be created once > -------------------------------------------------- > > Key: WFCORE-2080 > URL: https://issues.jboss.org/browse/WFCORE-2080 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Tomaz Cerar > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 3.0.0.Alpha15 > > > Currently WildFlyElytronProvider is created dynamicly when needed as it is created in supplier > to SecurityProviderServerMechanismFactory > example of hot method profiling https://paste.fedoraproject.org/495618/69264714/raw/ > which shows that currently provider can be created each time mgmt / remoting request is made -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-806) Wrong description of missing target-name in simple-permission-mapper

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-806?page=com.atlassian.jira.plugin.sy... ] Jan Kalina moved WFLY-7723 to ELY-806: -------------------------------------- Project: WildFly Elytron (was: WildFly) Key: ELY-806 (was: WFLY-7723) Component/s: Utils (was: Security) Fix Version/s: (was: 11.0.0.Alpha1) > Wrong description of missing target-name in simple-permission-mapper > -------------------------------------------------------------------- > > Key: ELY-806 > URL: https://issues.jboss.org/browse/ELY-806 > Project: WildFly Elytron > Issue Type: Bug > Components: Utils > Reporter: Jan Kalina > Assignee: Jan Kalina > Labels: user_experience > > In case when simple-permission-mapper cannot be added through CLI command due to missing target-name attribute, then IllegalArgumentException with wrong description is thrown. It says: "Parameter '*name*' may not be null". It should be "Parameter '*target-name*' may not be null". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7723) Wrong description of missing target-name in simple-permission-mapper

by Jan Kalina (JIRA)

Jan Kalina created WFLY-7723: -------------------------------- Summary: Wrong description of missing target-name in simple-permission-mapper Key: WFLY-7723 URL: https://issues.jboss.org/browse/WFLY-7723 Project: WildFly Issue Type: Bug Components: Security Reporter: Jan Kalina Assignee: Jan Kalina Fix For: 11.0.0.Alpha1 In case when simple-permission-mapper cannot be added through CLI command due to missing target-name attribute, then IllegalArgumentException with wrong description is thrown. It says: "Parameter '*name*' may not be null". It should be "Parameter '*target-name*' may not be null". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6936) RebindTestCase fails with security manager

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFLY-6936?page=com.atlassian.jira.plugin.... ] Ken Wills commented on WFLY-6936: --------------------------------- FYI Ingo, the security manager change was merged into wildfly-core yesterday. > RebindTestCase fails with security manager > ------------------------------------------ > > Key: WFLY-6936 > URL: https://issues.jboss.org/browse/WFLY-6936 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Jan Tymel > Assignee: Ingo Weiss > Fix For: 11.0.0.Alpha1 > > > *org.jboss.as.test.integration.naming.RebindTestCase#testRebinding* > *org.jboss.as.test.integration.naming.RebindTestCase#testRebindingLookup* > *org.jboss.as.test.integration.naming.RebindTestCase#testRebindingObjectFactory* > {{./integration-tests.sh -DtestLogToFile=false -Dts.noSmoke -Dts.basic -Dtest=org.jboss.as.test.integration.naming.RebindTestCase#testRebinding -Dsecurity.manager}} > Fails with: > {code} > Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("org.jboss.remoting3.security.RemotingPermission" "createEndpoint")" in code source "(vfs:/content/RebindTestCase.jar <no signer certificates>)" of "null") > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:273) > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175) > at org.jboss.remoting3.Remoting.createEndpoint(Remoting.java:85) > at org.jboss.remoting3.Remoting.createEndpoint(Remoting.java:112) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:120) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:64) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:139) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:114) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147) > ... 145 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2080) WildFlyElytronProvider should only be created once

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFCORE-2080: ----------------------------------- Summary: WildFlyElytronProvider should only be created once Key: WFCORE-2080 URL: https://issues.jboss.org/browse/WFCORE-2080 Project: WildFly Core Issue Type: Bug Components: Security Reporter: Tomaz Cerar Assignee: Darran Lofthouse Priority: Critical Currently WildFlyElytronProvider is created dynamicly when needed as it is created in supplier to SecurityProviderServerMechanismFactory example of hot method profiling https://paste.fedoraproject.org/495618/69264714/raw/ which shows that currently provider can be created each time mgmt / remoting request is made -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

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 December 2016