December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1470) Release WildFly Elytron 1.2.0.Beta11

by Darran Lofthouse (JIRA)

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

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3472) Add HostExcludeResourceDefinition.KnownRelease items for EAP 7.1

by Kabir Khan (JIRA)

Kabir Khan created WFCORE-3472: ---------------------------------- Summary: Add HostExcludeResourceDefinition.KnownRelease items for EAP 7.1 Key: WFCORE-3472 URL: https://issues.jboss.org/browse/WFCORE-3472 Project: WildFly Core Issue Type: Task Components: Domain Management Reporter: Kabir Khan Assignee: Kabir Khan -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3470) Add an option to configure the service display name during service install

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3470?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-3470: ---------------------------------------- Fix Version/s: 4.0.0.Alpha6 Assignee: David Le Borgne (was: Tomaz Cerar) Resolution: Done > Add an option to configure the service display name during service install > -------------------------------------------------------------------------- > > Key: WFCORE-3470 > URL: https://issues.jboss.org/browse/WFCORE-3470 > Project: WildFly Core > Issue Type: Feature Request > Components: Scripts > Reporter: David Le Borgne > Assignee: David Le Borgne > Priority: Minor > Fix For: 4.0.0.Alpha6 > > > The docs/contrib/scripts/service.bat lacks an option to configure the service display name during service installation. The service display name will take the value of the service name. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3470) Add an option to configure the service display name during service install

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3470?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-9619 to WFCORE-3470: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-3470 (was: WFLY-9619) Component/s: Scripts (was: Scripts) > Add an option to configure the service display name during service install > -------------------------------------------------------------------------- > > Key: WFCORE-3470 > URL: https://issues.jboss.org/browse/WFCORE-3470 > Project: WildFly Core > Issue Type: Feature Request > Components: Scripts > Reporter: David Le Borgne > Assignee: Tomaz Cerar > Priority: Minor > > The docs/contrib/scripts/service.bat lacks an option to configure the service display name during service installation. The service display name will take the value of the service name. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3471) Upgrade WildFly Elytron to 1.2.0.Beta11

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-3471: ---------------------------------------- Summary: Upgrade WildFly Elytron to 1.2.0.Beta11 Key: WFCORE-3471 URL: https://issues.jboss.org/browse/WFCORE-3471 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 4.0.0.Alpha6 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ELY-1461) Java 9: Eliminate reflection warning from security manager

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-1461?page=com.atlassian.jira.plugin.s... ] David Lloyd resolved ELY-1461. ------------------------------ Fix Version/s: 1.2.0.Beta11 Resolution: Done > Java 9: Eliminate reflection warning from security manager > ---------------------------------------------------------- > > Key: ELY-1461 > URL: https://issues.jboss.org/browse/ELY-1461 > Project: WildFly Elytron > Issue Type: Task > Components: Security Manager > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.2.0.Beta11 > > > Java 9 does not take kindly to our invasive reflection into AccessControlContext; also, if the implementation happens to not have the same fields, we fail to start the entire application server. > Our enhanced debug output is nice but for now this should be changed to be Java 9-safe. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ELY-1470) Release WildFly Elytron 1.2.0.Beta11

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1470: ------------------------------------- Summary: Release WildFly Elytron 1.2.0.Beta11 Key: ELY-1470 URL: https://issues.jboss.org/browse/ELY-1470 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.2.0.Beta11 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ELY-124) Java 8+ supports unbound SASL servers; GSSAPI and DIGEST-MD5 both use this value

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-124?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-124: -------------------------------- [~mchoma] The client provides the serverName when server is created as unbound (serverName = null). Negotiated property mean value is provided by opposite side of the communication - so yes, client in case of SaslServer. Ad task 8001104: this is feature request for feature, which is necessary to implement unbound for GS2/GSSAPI sasl server - this is used in attached pull request. > Java 8+ supports unbound SASL servers; GSSAPI and DIGEST-MD5 both use this value > -------------------------------------------------------------------------------- > > Key: ELY-124 > URL: https://issues.jboss.org/browse/ELY-124 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Affects Versions: 1.2.0.Beta10 > Reporter: David Lloyd > Assignee: Jan Kalina > Fix For: 1.2.0.Beta11 > > > Since Java 8, the SaslServerFactory interface has been changed so that the serverName may be null. If null, the server name is considered "unbound" and the client can select what server name it wants to use. > The release notes say: > {quote} > SASL service for multiple host names: When creating a SASL server, the server name can be set to null to denote an unbound server, which means a client can request for the service using any server name. After a context is established, the server can retrieve the name as a negotiated property with the key name SASL.BOUND_SERVER_NAME. See RFE 7110803. > {quote} > The updated JavaDoc says: > {quote} > serverName - The fully qualified host name of the server to authenticate to, or null if the server is not bound to any specific host name. If the mechanism does not allow an unbound server, a SaslException will be thrown. > {quote} > The RFE link is: http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7110803 > The two SASL mechanisms in Elytron that would be impacted by this are DIGEST-MD5 and GSSAPI. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ELY-283) Investigate Elytron and gssproxy interoperability

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-283?page=com.atlassian.jira.plugin.sy... ] David Lloyd commented on ELY-283: --------------------------------- I think you are correct that it must be a bug in the library, so an upstream bug should be reported. I think that the OpenJDK security team would accept the patch to initialize it to 0 though, knowing that it works around such a bug. Nice job! > Investigate Elytron and gssproxy interoperability > ------------------------------------------------- > > Key: ELY-283 > URL: https://issues.jboss.org/browse/ELY-283 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Reporter: Peter Skopek > Assignee: Jan Kalina > Fix For: 2.0.0.Alpha1 > > Attachments: openjdk-patch-native-mechs.patch > > > Investigate Elytron and gssproxy interoperability. > https://fedorahosted.org/gss-proxy/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6696) Problem with infinispan, Unable to acquire lock after 15 seconds for key

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-6696?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-6696: ------------------------------------ To support concurrent distributed web session access, you should configure your web session cache configuration to be non-transactional, with READ_COMMITTED isolation. We're working on improving distributed web session concurrency over the next few releases, such that sessions are fully concurrent, but only on one node at a time. > Problem with infinispan, Unable to acquire lock after 15 seconds for key > ------------------------------------------------------------------------- > > Key: WFLY-6696 > URL: https://issues.jboss.org/browse/WFLY-6696 > Project: WildFly > Issue Type: Bug > Components: Clustering, Web (Undertow) > Affects Versions: 10.0.0.Final > Environment: linux debian, apache, oracle database > Reporter: Bruno Silva > Assignee: Paul Ferraro > Attachments: error.txt > > > I have two nodes in cluster using standalone-ha.xml, but when put <distributable/> into web.xml the error below has happened frenquently and I'm using SSO. > {noformat} > 2016-06-09 14:46:55,160 ERROR [io.undertow.request] (default task-93) UT005071: Undertow request failed HttpServerExchange{ GET /intranet/app/pagina.action request Cookie=[JSESSIONID=hwGOzICm6QQGaHzyf3MQ8jK8j7aRBGbDksNF4oeK.node3; JSESSIONIDSSO=iYEO1MGfzBBsKmvmuO8HPz0whseKXJmRzjuuuiRQ; org.infinispan.util.concurrent.TimeoutException: ISPN000299: Unable to acquire lock after 15 seconds for key hwGOzICm6QQGaHzyf3MQ8jK8j7aRBGbDksNF4oeK and requestor GlobalTransaction:<node3>:475504:local. Lock is held by GlobalTransaction:<node3>:474447:local > at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.lock(DefaultLockManager.java:236) > at org.infinispan.interceptors.locking.AbstractLockingInterceptor.lockAllAndRecord(AbstractLockingInterceptor.java:199) > at org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.checkPendingAndLockAllKeys(AbstractTxLockingInterceptor.java:199) > at org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockAllOrRegisterBackupLock(AbstractTxLockingInterceptor.java:165) > at org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitLockControlCommand(PessimisticLockingInterceptor.java:184) > at org.infinispan.commands.control.LockControlCommand.acceptVisitor(LockControlCommand.java:110) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99) > at org.infinispan.interceptors.TxInterceptor.invokeNextInterceptorAndVerifyTransaction(TxInterceptor.java:157) > at org.infinispan.interceptors.TxInterceptor.visitLockControlCommand(TxInterceptor.java:215) > at org.infinispan.commands.control.LockControlCommand.acceptVisitor(LockControlCommand.java:110) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99) > at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:113) > at org.infinispan.commands.AbstractVisitor.visitLockControlCommand(AbstractVisitor.java:163) > at org.infinispan.statetransfer.TransactionSynchronizerInterceptor.visitLockControlCommand(TransactionSynchronizerInterceptor.java:78) > at org.infinispan.commands.control.LockControlCommand.acceptVisitor(LockControlCommand.java:110) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99) > at org.infinispan.statetransfer.StateTransferInterceptor.handleTxCommand(StateTransferInterceptor.java:238) > at org.infinispan.statetransfer.StateTransferInterceptor.visitLockControlCommand(StateTransferInterceptor.java:102) > at org.infinispan.commands.control.LockControlCommand.acceptVisitor(LockControlCommand.java:110) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99) > at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:107) > at org.infinispan.interceptors.InvocationContextInterceptor.visitLockControlCommand(InvocationContextInterceptor.java:81) > at org.infinispan.commands.control.LockControlCommand.acceptVisitor(LockControlCommand.java:110) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99) > at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:113) > at org.infinispan.commands.AbstractVisitor.visitLockControlCommand(AbstractVisitor.java:163) > at org.infinispan.commands.control.LockControlCommand.acceptVisitor(LockControlCommand.java:110) > at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:336) > at org.infinispan.cache.impl.CacheImpl.lock(CacheImpl.java:828) > at org.infinispan.cache.impl.CacheImpl.lock(CacheImpl.java:810) > at org.infinispan.cache.impl.AbstractDelegatingAdvancedCache.lock(AbstractDelegatingAdvancedCache.java:177) > at org.wildfly.clustering.web.infinispan.session.InfinispanSessionMetaDataFactory.getValue(InfinispanSessionMetaDataFactory.java:84) > at org.wildfly.clustering.web.infinispan.session.InfinispanSessionMetaDataFactory.findValue(InfinispanSessionMetaDataFactory.java:69) > at org.wildfly.clustering.web.infinispan.session.InfinispanSessionMetaDataFactory.findValue(InfinispanSessionMetaDataFactory.java:39) > at org.wildfly.clustering.web.infinispan.session.InfinispanSessionFactory.findValue(InfinispanSessionFactory.java:61) > at org.wildfly.clustering.web.infinispan.session.InfinispanSessionFactory.findValue(InfinispanSessionFactory.java:40) > at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager.findSession(InfinispanSessionManager.java:234) > at org.wildfly.clustering.web.undertow.session.DistributableSessionManager.getSession(DistributableSessionManager.java:139) > at io.undertow.servlet.spec.ServletContextImpl.getSession(ServletContextImpl.java:726) > at io.undertow.servlet.spec.ServletContextImpl.getSession(ServletContextImpl.java:756) > at io.undertow.servlet.spec.ServletContextImpl.updateSessionAccessTime(ServletContextImpl.java:760) > at io.undertow.servlet.spec.HttpServletResponseImpl.responseDone(HttpServletResponseImpl.java:557) > at io.undertow.servlet.spec.HttpServletResponseImpl.doErrorDispatch(HttpServletResponseImpl.java:168) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:319) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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 2017