March 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-433) Support verification of a users certificate against an LDAP

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-433: ------------------------------------ Summary: Support verification of a users certificate against an LDAP Key: ELY-433 URL: https://issues.jboss.org/browse/ELY-433 Project: WildFly Elytron Issue Type: Feature Request Components: Realms, SSL Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta5 This is specifically for authentication - NOT for general TrustManager requirements - another Jira issue is tracking looking into a KeyStore implementation backed by LDAP. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-121) Static initializer of class org.apache.log4j.helpers.Loader relies on obsolete java versioning scheme

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-121?page=com.atlassian.jira.plu... ] James Perkins commented on JBLOGGING-121: ----------------------------------------- The {{log4j-jboss-logmanager}} is a fork of log4j 1.x that delegates to the JBoss Log Manager. That download is for log4j2. This would be our concern with log4j 1.x https://github.com/apache/log4j/blob/trunk/src/main/java/org/apache/log4j.... It's about a 3 line change really. If I get some time I'll submit a PR for it. > Static initializer of class org.apache.log4j.helpers.Loader relies on obsolete java versioning scheme > ----------------------------------------------------------------------------------------------------- > > Key: JBLOGGING-121 > URL: https://issues.jboss.org/browse/JBLOGGING-121 > Project: JBoss Logging > Issue Type: Bug > Components: jboss-logging-log4j > Reporter: Richard Opalka > Assignee: James Perkins > > JDK9 will introduce new java versioning scheme, see JEP-223 > http://openjdk.java.net/jeps/223 > Please update static initializer of class org.apache.log4j.helpers.Loader accordingly > to ensure smooth JDK9 migration. ATM the initializer will not handle Java 9 properly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-432) Support setEnableSessionCreation on ServerSSLContextBuilder

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-432: ------------------------------------ Summary: Support setEnableSessionCreation on ServerSSLContextBuilder Key: ELY-432 URL: https://issues.jboss.org/browse/ELY-432 Project: WildFly Elytron Issue Type: Feature Request Components: SSL Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta5 It is already possible to configure this one for XNIO and Undertow so we should add this config option to our own builder. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1421) CLI shutdown command doesn't support graceful shutdown

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1421: ---------------------------------------- Summary: CLI shutdown command doesn't support graceful shutdown Key: WFCORE-1421 URL: https://issues.jboss.org/browse/WFCORE-1421 Project: WildFly Core Issue Type: Bug Components: CLI Affects Versions: 2.1.0.CR1 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.0.0.Alpha1 The shutdown command needs to support a timeout param so users can have a graceful shutdown. I'm calling this a bug because the low level :shutdown op is not reliable for CLI users due to the issues with handling of connection closing that the shutdown command takes care of. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6313) Upgrade Narayana to 5.3.0.Final

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-6313?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-6313: -------------------------------- Description: https://issues.jboss.org/browse/JBTM/fixforversion/12329807/?selectedTab=... > Upgrade Narayana to 5.3.0.Final > ------------------------------- > > Key: WFLY-6313 > URL: https://issues.jboss.org/browse/WFLY-6313 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 11.0.0.Alpha1 > > > https://issues.jboss.org/browse/JBTM/fixforversion/12329807/?selectedTab=... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6313) Upgrade Narayana to 5.3.0.Final

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-6313?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-6313: -------------------------------- Fix Version/s: 11.0.0.Alpha1 > Upgrade Narayana to 5.3.0.Final > ------------------------------- > > Key: WFLY-6313 > URL: https://issues.jboss.org/browse/WFLY-6313 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 11.0.0.Alpha1 > > > https://issues.jboss.org/browse/JBTM/fixforversion/12329807/?selectedTab=... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6313) Upgrade Narayana to 5.3.0.Final

by Tom Jenkinson (JIRA)

Tom Jenkinson created WFLY-6313: ----------------------------------- Summary: Upgrade Narayana to 5.3.0.Final Key: WFLY-6313 URL: https://issues.jboss.org/browse/WFLY-6313 Project: WildFly Issue Type: Component Upgrade Components: Transactions Reporter: Tom Jenkinson Assignee: Tom Jenkinson -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1420) CLI shutdown command doesn't support graceful shutdown

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1420: ---------------------------------------- Summary: CLI shutdown command doesn't support graceful shutdown Key: WFCORE-1420 URL: https://issues.jboss.org/browse/WFCORE-1420 Project: WildFly Core Issue Type: Bug Components: CLI Affects Versions: 2.1.0.CR1 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.0.0.Alpha1 The shutdown command needs to support a timeout param so users can have a graceful shutdown. I'm calling this a bug because the low level :shutdown op is not reliable for CLI users due to the issues with handling of connection closing that the shutdown command takes care of. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6312) Intermittent failure: client gets NPE in ejbremote scenario

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6312?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned WFLY-6312: ------------------------------------ Component/s: Remoting (was: Clustering) Assignee: David Lloyd (was: Paul Ferraro) > Intermittent failure: client gets NPE in ejbremote scenario > ------------------------------------------------------------- > > Key: WFLY-6312 > URL: https://issues.jboss.org/browse/WFLY-6312 > Project: WildFly > Issue Type: Bug > Components: Remoting > Affects Versions: 10.0.0.Final > Reporter: Michal Vinkler > Assignee: David Lloyd > > Seen in a scenario: ejb-ejbremote-shutdown-repl-async > Approx. 20 seconds after perf18 was restarted (after previous graceful shutdown), client logged thi NPE seven times. No error occurred on any of the servers during that time. > {code} > 2016/02/25 19:23:11:869 EST [ERROR][Runner - 633] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <java.lang.NullPointerException> > java.lang.NullPointerException > at org.jboss.remoting3.remote.OutboundMessage$2.getKey(OutboundMessage.java:173) > at org.jboss.remoting3.remote.OutboundMessage$2.getKey(OutboundMessage.java:171) > at org.jboss.remoting3.remote.IntIndexHashMap.doGet(IntIndexHashMap.java:507) > at org.jboss.remoting3.remote.IntIndexHashMap.containsKey(IntIndexHashMap.java:169) > at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:313) > at org.jboss.ejb.client.remoting.ChannelAssociation.acquireChannelMessageOutputStream(ChannelAssociation.java:281) > at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.processInvocationInternal(RemotingConnectionEJBReceiver.java:295) > at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.access$100(RemotingConnectionEJBReceiver.java:77) > at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver$2.run(RemotingConnectionEJBReceiver.java:282) > at java.security.AccessController.doPrivileged(Native Method) > at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.processInvocation(RemotingConnectionEJBReceiver.java:279) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:184) > at org.jboss.ejb.client.EJBObjectInterceptor.handleInvocation(EJBObjectInterceptor.java:58) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.EJBHomeInterceptor.handleInvocation(EJBHomeInterceptor.java:83) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:138) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183) > at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146) > at com.sun.proxy.$Proxy2.getSerialAndIncrement(Unknown Source) > at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:84) > at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52) > at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103) > at java.lang.Thread.run(Thread.java:745) > {code} > Client link: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-e... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6312) Intermittent failure: client gets NPE in ejbremote scenario

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-6312?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-6312: ----------------------------------- An NPE is always a bug. In this case it is in Remoting, so the upstream JIRA should be opened in the REM3 project (ideally including the exact version of Remoting that this problem was observed in). > Intermittent failure: client gets NPE in ejbremote scenario > ------------------------------------------------------------- > > Key: WFLY-6312 > URL: https://issues.jboss.org/browse/WFLY-6312 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Michal Vinkler > Assignee: Paul Ferraro > > Seen in a scenario: ejb-ejbremote-shutdown-repl-async > Approx. 20 seconds after perf18 was restarted (after previous graceful shutdown), client logged thi NPE seven times. No error occurred on any of the servers during that time. > {code} > 2016/02/25 19:23:11:869 EST [ERROR][Runner - 633] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <java.lang.NullPointerException> > java.lang.NullPointerException > at org.jboss.remoting3.remote.OutboundMessage$2.getKey(OutboundMessage.java:173) > at org.jboss.remoting3.remote.OutboundMessage$2.getKey(OutboundMessage.java:171) > at org.jboss.remoting3.remote.IntIndexHashMap.doGet(IntIndexHashMap.java:507) > at org.jboss.remoting3.remote.IntIndexHashMap.containsKey(IntIndexHashMap.java:169) > at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:313) > at org.jboss.ejb.client.remoting.ChannelAssociation.acquireChannelMessageOutputStream(ChannelAssociation.java:281) > at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.processInvocationInternal(RemotingConnectionEJBReceiver.java:295) > at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.access$100(RemotingConnectionEJBReceiver.java:77) > at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver$2.run(RemotingConnectionEJBReceiver.java:282) > at java.security.AccessController.doPrivileged(Native Method) > at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.processInvocation(RemotingConnectionEJBReceiver.java:279) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:184) > at org.jboss.ejb.client.EJBObjectInterceptor.handleInvocation(EJBObjectInterceptor.java:58) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.EJBHomeInterceptor.handleInvocation(EJBHomeInterceptor.java:83) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:138) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183) > at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146) > at com.sun.proxy.$Proxy2.getSerialAndIncrement(Unknown Source) > at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:84) > at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52) > at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103) > at java.lang.Thread.run(Thread.java:745) > {code} > Client link: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-e... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 March 2016