March 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-141) Add a Credential to Name Resolver SPI

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-141?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-141: ------------------------------------ Assignee: Darran Lofthouse > Add a Credential to Name Resolver SPI > ------------------------------------- > > Key: ELY-141 > URL: https://issues.jboss.org/browse/ELY-141 > Project: WildFly Elytron > Issue Type: Feature Request > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta5 > > > We are predominantly considering this in the context of the validation side of the API. > However should still not exclude the possibility that after obtaining a RealmIdentity the validation may still be performed in the mechanism. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-428) HTTP Mechanism configuration during deployment

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-428?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-428: -------------------------------------- We discussed this during our design sessions this week, the outcome was: - Mechanisms will be able to access resources from their application, however they will not be able to do this until the first request is received making this a lazy approach to initialisation, in addition to this we will have an 'Application' attachment context the mechanism can use to cache this. The alternative for mechanisms is to provide a pre-configured mechanism factory that will have already managed that configuration in advance. > HTTP Mechanism configuration during deployment > ---------------------------------------------- > > Key: ELY-428 > URL: https://issues.jboss.org/browse/ELY-428 > Project: WildFly Elytron > Issue Type: Enhancement > Components: HTTP > Affects Versions: 1.0.2.Final > Reporter: Pedro Igor > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta5 > > > It should be possible to configure a HTTP mechanism during deployment in order to parse/load configuration and reuse it in subsequent requests to an application. > The most common use case for that is around mechanisms that need to read some configuration from inside a deployment (or provided by the mech config) when it is being deployed to the server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-99) Support for one-time messages

by David Lloyd (JIRA)

David Lloyd created LOGTOOL-99: ---------------------------------- Summary: Support for one-time messages Key: LOGTOOL-99 URL: https://issues.jboss.org/browse/LOGTOOL-99 Project: Log Tool Issue Type: Feature Request Reporter: David Lloyd Assignee: James Perkins Fix For: 2.1.0.Alpha1 Add an annotation that indicates that a log message should only be logged one time. The imlpementation would use a private static final AtomicBoolean with CAS to ensure that the message is logged one time, guarding such messages with code that is something like this: {code} AtomicBoolean someMessageCalledOnce = this.someMessageCalledOnce; do { if (someMessageCalledOnce.get()) return; } while (! someMessageCalledOnce.compareAndSet(false, true)); // ... log message here ... {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6407) IdentityUrl element has changed but XSD schema not

by Hynek Švábek (JIRA)

Hynek Švábek created WFLY-6407: ---------------------------------- Summary: IdentityUrl element has changed but XSD schema not Key: WFLY-6407 URL: https://issues.jboss.org/browse/WFLY-6407 Project: WildFly Issue Type: Bug Components: Security Reporter: Hynek Švábek Assignee: Darran Lofthouse Depending on this Jira issue https://issues.jboss.org/browse/PLINK-695 there are some changes about IdentityUrl element. Now you can define <Provider> in picketlink.xml like this: {code} <PicketLinkSP xmlns="urn:picketlink:identity-federation:config:2.1" ServerEnvironment="tomcat" BindingType="${bindingType}"> <IdentityURL> <Provider DefaultUrl="http://${hostname}:8080/${idpContextPath}/" Type="org.picketlink.test.integration.federation.saml.util.CustomIdentityURLProvider" Page="/selectDomain.jsp"/> </IdentityURL> <ServiceURL>http://${hostname}:8080/${deployment}/</ServiceURL> </PicketLinkSP> {code} But there are missing relevant changes in XSD schema (picketlink_v2.1.xsd). Here is link for related commit https://github.com/jbossas/redhat-picketlink/blob/eap-7.x/modules/config/.... There is version 2.5.5.SP1 in EAP7.0.0.ER6. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-462) LDAP realm should use naming subsystem

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-462?page=com.atlassian.jira.plugin.sy... ] David Lloyd commented on ELY-462: --------------------------------- While LDAP does use JNDI, I don't understand the reason why we'd want to use the subsystem. Can you or [~darranl] elaborate? > LDAP realm should use naming subsystem > -------------------------------------- > > Key: ELY-462 > URL: https://issues.jboss.org/browse/ELY-462 > Project: WildFly Elytron > Issue Type: Task > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Minor > > LDAP realm should use naming subsystem (as JDBC realm use datasource) > (requested by Darran on F2F) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6402) EJBs accessible too early (spec violation)

by Fedor Gavrilov (JIRA)

[ https://issues.jboss.org/browse/WFLY-6402?page=com.atlassian.jira.plugin.... ] Fedor Gavrilov reassigned WFLY-6402: ------------------------------------ Assignee: Fedor Gavrilov > EJBs accessible too early (spec violation) > ------------------------------------------ > > Key: WFLY-6402 > URL: https://issues.jboss.org/browse/WFLY-6402 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Brad Maxwell > Assignee: Fedor Gavrilov > Attachments: auto-test-reproducer.zip > > > {code} > EJB 3.1 spec, section 4.8.1: > "If the Startup annotation appears on the Singleton bean class or if the Singleton has been designated via the deployment descriptor as requiring eager initialization, the container must initialize the Singleton bean instance during the application startup sequence. The container must initialize all such startup-time Singletons before any external client requests (that is, client requests originating outside of the application) are delivered to any enterprise bean components in the application. > {code} > Wildlfy does not implement this correctly, and allows calls to other EJBs before a @Startup @Singleton finishes its @PostConstruct call. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6406) Artemis AIO journal fails on zfsonlinux ZFS filesystem

by Dominik Pospisil (JIRA)

[ https://issues.jboss.org/browse/WFLY-6406?page=com.atlassian.jira.plugin.... ] Dominik Pospisil reassigned WFLY-6406: -------------------------------------- Assignee: Dominik Pospisil (was: Jeff Mesnil) > Artemis AIO journal fails on zfsonlinux ZFS filesystem > ------------------------------------------------------ > > Key: WFLY-6406 > URL: https://issues.jboss.org/browse/WFLY-6406 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Dominik Pospisil > Assignee: Dominik Pospisil > > Artemis AIO journal fails on zfsonlinux ZFS filesystem. According to zfsonlinux docs libaio should be supported. > I guess that the initialization should work or failback to NIO. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6406) Artemis AIO journal fails on zfsonlinux ZFS filesystem

by Dominik Pospisil (JIRA)

[ https://issues.jboss.org/browse/WFLY-6406?page=com.atlassian.jira.plugin.... ] Dominik Pospisil commented on WFLY-6406: ---------------------------------------- 2016-03-18 10:25:34,469 ERROR [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ224000: Failure in initialisation: ActiveMQNativeIOError[errorType=NATIVE_ERROR_CANT_INITIALIZE_AIO message=Cannot open file:Invalid argument] at org.apache.activemq.artemis.core.io.aio.AIOSequentialFile.open(AIOSequentialFile.java:137) at org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.createFile0(JournalFilesRepository.java:590) at org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.createFile(JournalFilesRepository.java:543) at org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.ensureMinFiles(JournalFilesRepository.java:206) at org.apache.activemq.artemis.core.journal.impl.JournalImpl.setUpCurrentFile(JournalImpl.java:2652) at org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1728) at org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1126) at org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1110) at org.apache.activemq.artemis.core.persistence.impl.journal.JournalStorageManager.loadMessageJournal(JournalStorageManager.java:1255) at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.loadJournals(ActiveMQServerImpl.java:1701) at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart2(ActiveMQServerImpl.java:1595) at org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:60) at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:393) at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:381) at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:199) at org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:63) at org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:97) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) 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) at org.jboss.threads.JBossThread.run(JBossThread.java:320) Caused by: java.io.IOException: Cannot open file:Invalid argument at org.apache.activemq.artemis.jlibaio.LibaioContext.open(Native Method) at org.apache.activemq.artemis.jlibaio.LibaioContext.openFile(LibaioContext.java:290) at org.apache.activemq.artemis.jlibaio.LibaioContext.openFile(LibaioContext.java:273) at org.apache.activemq.artemis.core.io.aio.AIOSequentialFile.open(AIOSequentialFile.java:133) ... 22 more > Artemis AIO journal fails on zfsonlinux ZFS filesystem > ------------------------------------------------------ > > Key: WFLY-6406 > URL: https://issues.jboss.org/browse/WFLY-6406 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Dominik Pospisil > Assignee: Jeff Mesnil > > Artemis AIO journal fails on zfsonlinux ZFS filesystem. According to zfsonlinux docs libaio should be supported. > I guess that the initialization should work or failback to NIO. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6406) Artemis AIO journal fails on zfsonlinux ZFS filesystem

by Dominik Pospisil (JIRA)

Dominik Pospisil created WFLY-6406: -------------------------------------- Summary: Artemis AIO journal fails on zfsonlinux ZFS filesystem Key: WFLY-6406 URL: https://issues.jboss.org/browse/WFLY-6406 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 10.1.0.Final Reporter: Dominik Pospisil Assignee: Jeff Mesnil Artemis AIO journal fails on zfsonlinux ZFS filesystem. According to zfsonlinux docs libaio should be supported. I guess that the initialization should work or failback to NIO. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1442) ClientAgainstOldServerTestCase fails due to -XX:MaxMetaspaceSize=256m

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1442?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-1442: ------------------------------- Description: The breaking change is https://github.com/wildfly/wildfly-core/commit/737106d7d6ea6d600f52630236... This test starts old versions of the server, some on JDK6 and some on JDK7 where MaxMetaspaceSize does not exist. was:The breaking change is https://github.com/wildfly/wildfly-core/commit/737106d7d6ea6d600f52630236... > ClientAgainstOldServerTestCase fails due to -XX:MaxMetaspaceSize=256m > --------------------------------------------------------------------- > > Key: WFCORE-1442 > URL: https://issues.jboss.org/browse/WFCORE-1442 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > > The breaking change is https://github.com/wildfly/wildfly-core/commit/737106d7d6ea6d600f52630236... > This test starts old versions of the server, some on JDK6 and some on JDK7 where MaxMetaspaceSize does not exist. -- 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