September 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AG-35) Use ServiceLoader to discover implementations

by Luis Barreiro (JIRA)

Luis Barreiro created AG-35: ------------------------------- Summary: Use ServiceLoader to discover implementations Key: AG-35 URL: https://issues.jboss.org/browse/AG-35 Project: Agroal Issue Type: Bug Components: api, hikari, pool Affects Versions: 0.2 Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 0.3 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-977) Release PicketBox 5.0.3.Beta1

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/SECURITY-977?page=com.atlassian.jira.plug... ] Stefan Guilhen closed SECURITY-977. ----------------------------------- Resolution: Done PicketBox 5.0.3.Beta1 has been released and is available on Nexus. > Release PicketBox 5.0.3.Beta1 > ----------------------------- > > Key: SECURITY-977 > URL: https://issues.jboss.org/browse/SECURITY-977 > Project: PicketBox > Issue Type: Task > Components: JBossSX, Security-SPI, PicketBox > Reporter: Stefan Guilhen > Assignee: Stefan Guilhen > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-976) Make PicketBox releasable using maven release plugin

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/SECURITY-976?page=com.atlassian.jira.plug... ] Stefan Guilhen updated SECURITY-976: ------------------------------------ Git Pull Request: https://github.com/picketbox/picketbox/pull/71 > Make PicketBox releasable using maven release plugin > ---------------------------------------------------- > > Key: SECURITY-976 > URL: https://issues.jboss.org/browse/SECURITY-976 > Project: PicketBox > Issue Type: Task > Components: JBossSX, Security-SPI, PicketBox > Affects Versions: PicketBox_5_0_2.Final > Reporter: Stefan Guilhen > Assignee: Stefan Guilhen > Fix For: PicketBox_5_0_3.Beta1 > > > PicketBox is currently released using maven deploy plugin, which requires a few manual steps to update versions in poms and tag the release. As the project is entering maintenance mode it is desirable that releases can be created using the maven release plugin. The release plugin automates most of the steps that are currently done manually or with the help of scripts and allows for easier maintenance. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-976) Make PicketBox releasable using maven release plugin

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/SECURITY-976?page=com.atlassian.jira.plug... ] Stefan Guilhen resolved SECURITY-976. ------------------------------------- Resolution: Done > Make PicketBox releasable using maven release plugin > ---------------------------------------------------- > > Key: SECURITY-976 > URL: https://issues.jboss.org/browse/SECURITY-976 > Project: PicketBox > Issue Type: Task > Components: JBossSX, Security-SPI, PicketBox > Affects Versions: PicketBox_5_0_2.Final > Reporter: Stefan Guilhen > Assignee: Stefan Guilhen > Fix For: PicketBox_5_0_3.Beta1 > > > PicketBox is currently released using maven deploy plugin, which requires a few manual steps to update versions in poms and tag the release. As the project is entering maintenance mode it is desirable that releases can be created using the maven release plugin. The release plugin automates most of the steps that are currently done manually or with the help of scripts and allows for easier maintenance. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-975) Default distinguishedNameAttribute value of LdapExtLoginModule causes not working referrals on MS Active Directory

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/SECURITY-975?page=com.atlassian.jira.plug... ] Stefan Guilhen updated SECURITY-975: ------------------------------------ Fix Version/s: PicketBox_5_0_3.Beta1 > Default distinguishedNameAttribute value of LdapExtLoginModule causes not working referrals on MS Active Directory > ------------------------------------------------------------------------------------------------------------------ > > Key: SECURITY-975 > URL: https://issues.jboss.org/browse/SECURITY-975 > Project: PicketBox > Issue Type: Bug > Components: PicketBox > Affects Versions: PicketBox_5_0_2.Final > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > Fix For: PicketBox_5_0_3.Beta1 > > > In case when crossRef object to different domain is configured on MS Active Directory for handling referrals and JBoss EAP 7 uses LdapExtLoginModule then default value ('distinguishedName') of distinguishedNameAttribute option causes wrong handling of referrals which leads to authentication fail for referral users. > Referral object is returned by original LDAP server (LDAP server which includes crossRef to different domain) but user is obtained through value of distinguishedName attribute from that response. It leads to authentication attempt with referral user against original LDAP server instead of referenced LDAP server which results to failed authentication. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-975) Default distinguishedNameAttribute value of LdapExtLoginModule causes not working referrals on MS Active Directory

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/SECURITY-975?page=com.atlassian.jira.plug... ] Stefan Guilhen resolved SECURITY-975. ------------------------------------- Resolution: Done > Default distinguishedNameAttribute value of LdapExtLoginModule causes not working referrals on MS Active Directory > ------------------------------------------------------------------------------------------------------------------ > > Key: SECURITY-975 > URL: https://issues.jboss.org/browse/SECURITY-975 > Project: PicketBox > Issue Type: Bug > Components: PicketBox > Affects Versions: PicketBox_5_0_2.Final > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > Fix For: PicketBox_5_0_3.Beta1 > > > In case when crossRef object to different domain is configured on MS Active Directory for handling referrals and JBoss EAP 7 uses LdapExtLoginModule then default value ('distinguishedName') of distinguishedNameAttribute option causes wrong handling of referrals which leads to authentication fail for referral users. > Referral object is returned by original LDAP server (LDAP server which includes crossRef to different domain) but user is obtained through value of distinguishedName attribute from that response. It leads to authentication attempt with referral user against original LDAP server instead of referenced LDAP server which results to failed authentication. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-977) Release PicketBox 5.0.3.Beta1

by Stefan Guilhen (JIRA)

Stefan Guilhen created SECURITY-977: --------------------------------------- Summary: Release PicketBox 5.0.3.Beta1 Key: SECURITY-977 URL: https://issues.jboss.org/browse/SECURITY-977 Project: PicketBox Issue Type: Task Components: JBossSX, Security-SPI, PicketBox Reporter: Stefan Guilhen Assignee: Stefan Guilhen -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-976) Make PicketBox releasable using maven release plugin

by Stefan Guilhen (JIRA)

Stefan Guilhen created SECURITY-976: --------------------------------------- Summary: Make PicketBox releasable using maven release plugin Key: SECURITY-976 URL: https://issues.jboss.org/browse/SECURITY-976 Project: PicketBox Issue Type: Task Components: JBossSX, Security-SPI, PicketBox Affects Versions: PicketBox_5_0_2.Final Reporter: Stefan Guilhen Assignee: Stefan Guilhen Fix For: PicketBox_5_0_3.Beta1 PicketBox is currently released using maven deploy plugin, which requires a few manual steps to update versions in poms and tag the release. As the project is entering maintenance mode it is desirable that releases can be created using the maven release plugin. The release plugin automates most of the steps that are currently done manually or with the help of scripts and allows for easier maintenance. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9374) AMQ154003: Unable to reconnect org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.apache.activemq.artemis.ra.ActiveMQResourceAdapter@3ca2957 destination=inQueue

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-9374?page=com.atlassian.jira.plugin.... ] Jeff Mesnil closed WFLY-9374. ----------------------------- Resolution: Rejected The fix in Apache Artemis upstream does not require any modification in the messaging-activemq subsystem > AMQ154003: Unable to reconnect org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.apache.activemq.artemis.ra.ActiveMQResourceAdapter@3ca2957 destination=inQueue > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9374 > URL: https://issues.jboss.org/browse/WFLY-9374 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 11.0.0.CR1 > Environment: Red Hat JBoss Enterprise Application Platform (EAP) > - 7.0.7 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > When trying to connect to remote HornetQ broker (EAP 6.4.17) running in JBoss instance using standalone-full-ha.xml profile the following exception is thrown: > {noformat} > 2017-09-18 09:05:14,006 ERROR [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ154003: Unable to reconnect org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.apache.activemq.artemis.ra.ActiveMQResourceAdapter@3ca2957 destination=inQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15): java.lang.ClassCastException: org.hornetq.core.remoting.impl.netty.NettyConnectorFactory cannot be cast to org.apache.activemq.artemis.spi.core.remoting.ConnectorFactory > at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl$2.run(ClientSessionFactoryImpl.java:952) > at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl$2.run(ClientSessionFactoryImpl.java:950) > at java.security.AccessController.doPrivileged(Native Method) > at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.instantiateConnectorFactory(ClientSessionFactoryImpl.java:950) > at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.<init>(ClientSessionFactoryImpl.java:179) > at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:757) > at org.apache.activemq.artemis.ra.inflow.ActiveMQActivation.setup(ActiveMQActivation.java:316) > at org.apache.activemq.artemis.ra.inflow.ActiveMQActivation.reconnect(ActiveMQActivation.java:681) > at org.apache.activemq.artemis.ra.inflow.ActiveMQActivation$SetupActivation.run(ActiveMQActivation.java:725) > at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:223) > at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) > at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:808) > at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45) > at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:828) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > {noformat} > The same EAP 7 configuration works if the remote EAP 6 instance is using standalone-full.xml profile. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3262) Log stacktrace when exception occures in static method

by Martin Stefanko (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3262?page=com.atlassian.jira.plugi... ] Martin Stefanko updated WFCORE-3262: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2780, https://github.com/wildfly/wildfly-core/pull/2842 (was: https://github.com/wildfly/wildfly-core/pull/2780) > Log stacktrace when exception occures in static method > ------------------------------------------------------ > > Key: WFCORE-3262 > URL: https://issues.jboss.org/browse/WFCORE-3262 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 3.0.1.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Critical > > There is a bug JBEAP-12968. It was very hard to find out was is going on as stacktrace of exception was hidden. Even setting TRACE level in jboss-cli.properties does not reveal anything. > {code} > ./jboss-cli.bat -c "-Dwildfly.config.url=C:\wildfly-config.xml" > java.lang.ExceptionInInitializerError: java.lang.NullPointerException > {code} > Please log full stacktrace into jboss-cli.log in such case. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 September 2017