February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3637) Intermittent failure in FileInputTestCase

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3637?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-3637: ---------------------------------------------- Some of the observed issues should be related to this problem. I can't say if all cases will be fixed by it. > Intermittent failure in FileInputTestCase > ----------------------------------------- > > Key: WFCORE-3637 > URL: https://issues.jboss.org/browse/WFCORE-3637 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 4.0.0.Beta1 > Reporter: Brian Stansberry > Assignee: Jean-Francois Denise > > Test fails about 1% of the time on ci.wildfly.org: > https://ci.wildfly.org/project.html?buildTypeId=&branch_WildFlyCore_PullR... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9891) Upgrade picketlink to 2.5.5.SP9

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-9891?page=com.atlassian.jira.plugin.... ] Ivo Studensky moved JBEAP-14274 to WFLY-9891: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9891 (was: JBEAP-14274) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Build System) Affects Version/s: (was: 7.0.8.GA) Fix Version/s: (was: 7.2.0.GA) > Upgrade picketlink to 2.5.5.SP9 > ------------------------------- > > Key: WFLY-9891 > URL: https://issues.jboss.org/browse/WFLY-9891 > Project: WildFly > Issue Type: Component Upgrade > Components: Security > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Labels: downstream_dependency > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9884) WeldResourceInjectionServices runs into NoSuchElementException when deploying multiple EJBs

by Jacob Ilsø (JIRA)

[ https://issues.jboss.org/browse/WFLY-9884?page=com.atlassian.jira.plugin.... ] Jacob Ilsø edited comment on WFLY-9884 at 2/22/18 9:04 AM: ----------------------------------------------------------- [~jaikiran] Thanks! I'll try out your proposed fix on my environment. was (Author: jacobilsoe): [~jaikiran] I'll try out your proposed fixed on my environment. > WeldResourceInjectionServices runs into NoSuchElementException when deploying multiple EJBs > ------------------------------------------------------------------------------------------- > > Key: WFLY-9884 > URL: https://issues.jboss.org/browse/WFLY-9884 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 11.0.0.Final, 12.0.0.Beta1 > Environment: Windows 8.1 Enterprise. > Reporter: Jacob Ilsø > Assignee: Jason Greene > Attachments: log.txt > > > I have an EAR file with several "@Singleton @Startup" beans. Each bean having a number of @Inject and @Resource fields. When I deploy the EAR in WildFly 11 it sometimes fails with a NoSuchElementException (see [^log.txt] for a full stacktrace). > I cannot reproduce it consistently but it seems to only happen on a "clean" WildFly installation. I haven't seen this on earlier versions of WildFly. > Let me know if you want me to try to build an EAR for reproducing this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1524) Elytron error message less comprehensive in jdk9 compared to jdk8

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-1524?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on ELY-1524: ---------------------------------- I don't think it's likely this is an Elytron bug per se. It might be something in the CLI's callback handler? > Elytron error message less comprehensive in jdk9 compared to jdk8 > ----------------------------------------------------------------- > > Key: ELY-1524 > URL: https://issues.jboss.org/browse/ELY-1524 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Affects Versions: 1.2.0.Final > Reporter: Martin Choma > > I like jdk8 error message where there is obvious GS2-KRB5 has been attempted but failed for some reason, PLAIN has been attempted, but failed for some reason. > {code:title=jdk8} > Failed to connect to the controller: Unable to authenticate against controller at localhost:9993: Authentication failed: all available authentication mechanisms failed: > GS2-KRB5: javax.security.sasl.SaslException: GS2-KRB5: Server rejected authentication > PLAIN: javax.security.sasl.SaslException: ELY05053: Callback handler failed for unknown reason [Caused by java.io.IOException: Failed to read username: Invalid Usage. Prompt attempted in non-interactive mode. Please check commands or change CLI mode.] > {code} > Whereas in jdk9 error message hides the fact GS2-KRB5 was attempted and just prints error for PLAIN mechanism, but does not mention explicitely it is PLAIN mechanism > {code:title=jdk9} > Failed to connect to the controller: Unable to authenticate against controller at localhost:9993: Cannot get password: Failed to read username: Invalid Usage. Prompt attempted in non-interactive mode. Please check commands or change CLI mode. > {code} > This is general question, but I have hit this with this specific use case: > 1. server is configured to use GS2-KRB5 and PLAIN > 2. server is configured with TLS > 3. client is configured to use GS2-KRB5 > 4. expectation is authentication should be not successful because channel binding GS2-KRB5-PLUS should be used. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-16) Set Up Confluence Board

by Prachi Yadav (JIRA)

[ https://issues.jboss.org/browse/SWSQE-16?page=com.atlassian.jira.plugin.s... ] Prachi Yadav commented on SWSQE-16: ----------------------------------- Installed Conflunce server... working on setup > Set Up Confluence Board > ----------------------- > > Key: SWSQE-16 > URL: https://issues.jboss.org/browse/SWSQE-16 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Minor > > * We could have meeting notes, sprint retrospective notes, we could reference JIRAs (QE and Dev board), create pages for tasks documentation even test plans could be created on Confluence -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9878) EclipseLink Entity Scanning broken in Wildfly 11

by Jive JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-9878?page=com.atlassian.jira.plugin.... ] Jive JIRA Integration updated WFLY-9878: ---------------------------------------- Forum Reference: https://developer.jboss.org/message/980566#980566 > EclipseLink Entity Scanning broken in Wildfly 11 > ------------------------------------------------ > > Key: WFLY-9878 > URL: https://issues.jboss.org/browse/WFLY-9878 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 11.0.0.Final > Environment: Enterprise Maven Project > Wildfly 11 > Eclipse Link 2.7.1 (2.6.3 and 2.64 were also tested) > Reporter: Alessandro Moscatelli > Assignee: Scott Marlow > Fix For: 12.0.0.Final > > > Following : > https://docs.jboss.org/author/display/WFLY/JPA+Reference+Guide#JPAReferen... > When you try to persist ANY entity (located in ejb, or jar or anywhere you want) if such entity is not listed in persistence.xml you'll get a : > Caused by: javax.ejb.EJBException: java.lang.IllegalArgumentException: Object: org.visiontech.optoplus.entity.Provider[ id=null ] is not a known Entity type > If I list such entity in persistence.xml the error is gone and the entity is persisted. > Inside standalone.xml I used : > <system-properties> > ... > <property name="eclipselink.archive.factory" value="org.jipijapa.eclipselink.JBossArchiveFactoryImpl"/> > </system-properties> > Is this a problem related to the last version (11 Final) of jipijapa.eclipselink ? > I found several topic stating that what I done worked with Wildfly 10 and older version of jipijapa. > I tried several combination of older jipijapa and eclipselink versions without success. > I have about 130 entities in my probject, I'd REALLY love not to enlist them all. > My persistence.xml : > <persistence-unit name="optoplus"> > <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider> > <jta-data-source>java:/jdbc/db_optoplus</jta-data-source> > <exclude-unlisted-classes>false</exclude-unlisted-classes> > </persistence-unit> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1524) Elytron error message less comprehensive in jdk9 compared to jdk8

by Martin Choma (JIRA)

Martin Choma created ELY-1524: --------------------------------- Summary: Elytron error message less comprehensive in jdk9 compared to jdk8 Key: ELY-1524 URL: https://issues.jboss.org/browse/ELY-1524 Project: WildFly Elytron Issue Type: Bug Components: Authentication Mechanisms Affects Versions: 1.2.0.Final Reporter: Martin Choma I like jdk8 error message where there is obvious GS2-KRB5 has been attempted but failed for some reason, PLAIN has been attempted, but failed for some reason. {code:title=jdk8} Failed to connect to the controller: Unable to authenticate against controller at localhost:9993: Authentication failed: all available authentication mechanisms failed: GS2-KRB5: javax.security.sasl.SaslException: GS2-KRB5: Server rejected authentication PLAIN: javax.security.sasl.SaslException: ELY05053: Callback handler failed for unknown reason [Caused by java.io.IOException: Failed to read username: Invalid Usage. Prompt attempted in non-interactive mode. Please check commands or change CLI mode.] {code} Whereas in jdk9 error message hides the fact GS2-KRB5 was attempted and just prints error for PLAIN mechanism, but does not mention explicitely it is PLAIN mechanism {code:title=jdk9} Failed to connect to the controller: Unable to authenticate against controller at localhost:9993: Cannot get password: Failed to read username: Invalid Usage. Prompt attempted in non-interactive mode. Please check commands or change CLI mode. {code} This is general question, but I have hit this with this specific use case: 1. server is configured to use GS2-KRB5 and PLAIN 2. server is configured with TLS 3. client is configured to use GS2-KRB5 4. expectation is authentication should be not successful because channel binding GS2-KRB5-PLUS should be used. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9884) WeldResourceInjectionServices runs into NoSuchElementException when deploying multiple EJBs

by Jacob Ilsø (JIRA)

[ https://issues.jboss.org/browse/WFLY-9884?page=com.atlassian.jira.plugin.... ] Jacob Ilsø commented on WFLY-9884: ---------------------------------- [~jaikiran] I'll try out your proposed fixed on my environment. > WeldResourceInjectionServices runs into NoSuchElementException when deploying multiple EJBs > ------------------------------------------------------------------------------------------- > > Key: WFLY-9884 > URL: https://issues.jboss.org/browse/WFLY-9884 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 11.0.0.Final, 12.0.0.Beta1 > Environment: Windows 8.1 Enterprise. > Reporter: Jacob Ilsø > Assignee: Jason Greene > Attachments: log.txt > > > I have an EAR file with several "@Singleton @Startup" beans. Each bean having a number of @Inject and @Resource fields. When I deploy the EAR in WildFly 11 it sometimes fails with a NoSuchElementException (see [^log.txt] for a full stacktrace). > I cannot reproduce it consistently but it seems to only happen on a "clean" WildFly installation. I haven't seen this on earlier versions of WildFly. > Let me know if you want me to try to build an EAR for reproducing this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9884) WeldResourceInjectionServices runs into NoSuchElementException when deploying multiple EJBs

by Jacob Ilsø (JIRA)

[ https://issues.jboss.org/browse/WFLY-9884?page=com.atlassian.jira.plugin.... ] Jacob Ilsø commented on WFLY-9884: ---------------------------------- A bit more debugging seems to indicate that it happens when resolving this: @Resource(lookup = "java:jboss/datasources/MyDS") DataSource dataSource; > WeldResourceInjectionServices runs into NoSuchElementException when deploying multiple EJBs > ------------------------------------------------------------------------------------------- > > Key: WFLY-9884 > URL: https://issues.jboss.org/browse/WFLY-9884 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 11.0.0.Final, 12.0.0.Beta1 > Environment: Windows 8.1 Enterprise. > Reporter: Jacob Ilsø > Assignee: Jason Greene > Attachments: log.txt > > > I have an EAR file with several "@Singleton @Startup" beans. Each bean having a number of @Inject and @Resource fields. When I deploy the EAR in WildFly 11 it sometimes fails with a NoSuchElementException (see [^log.txt] for a full stacktrace). > I cannot reproduce it consistently but it seems to only happen on a "clean" WildFly installation. I haven't seen this on earlier versions of WildFly. > Let me know if you want me to try to build an EAR for reproducing this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9884) WeldResourceInjectionServices runs into NoSuchElementException when deploying multiple EJBs

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-9884?page=com.atlassian.jira.plugin.... ] jaikiran pai updated WFLY-9884: ------------------------------- Component/s: CDI / Weld > WeldResourceInjectionServices runs into NoSuchElementException when deploying multiple EJBs > ------------------------------------------------------------------------------------------- > > Key: WFLY-9884 > URL: https://issues.jboss.org/browse/WFLY-9884 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 11.0.0.Final, 12.0.0.Beta1 > Environment: Windows 8.1 Enterprise. > Reporter: Jacob Ilsø > Assignee: Jason Greene > Attachments: log.txt > > > I have an EAR file with several "@Singleton @Startup" beans. Each bean having a number of @Inject and @Resource fields. When I deploy the EAR in WildFly 11 it sometimes fails with a NoSuchElementException (see [^log.txt] for a full stacktrace). > I cannot reproduce it consistently but it seems to only happen on a "clean" WildFly installation. I haven't seen this on earlier versions of WildFly. > Let me know if you want me to try to build an EAR for reproducing this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2018