February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-893) Second security vault warning is displayed even if only one vault definition is present in the server configuration

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-893?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-893: -------------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1389201|https://bugzilla.redhat.com/show_bug.cgi?id=1389201] from VERIFIED to CLOSED > Second security vault warning is displayed even if only one vault definition is present in the server configuration > ------------------------------------------------------------------------------------------------------------------- > > Key: SECURITY-893 > URL: https://issues.jboss.org/browse/SECURITY-893 > Project: PicketBox > Issue Type: Bug > Components: JBossSX, Security-SPI > Affects Versions: PicketBox_4_1_0.Beta2 > Reporter: Ivo Studensky > Assignee: Peter Skopek > > The BZ's description: > I have only one vault configured in the standalone.xml but I see following warning message in the server log file after login attempt (bindCredentials login module option uses a vaulted password): > {noformat} > 09:10:58,854 WARN [org.jboss.security] (http-/127.0.0.1:8080-1) PBOX000378: Attempt to create the second Security Vault [org.picketbox.plugins.vault.PicketBoxSecurityVault] is invalid. Only one Security Vault is supported. Change your configuration, please. > {noformat} > This issue is related to the previous fix for bz1055577, \[1\]. The problem needs to be fixed on EAP side in time of Security Subsystem configuration processing. Fix will be provided by bz1181457 \[2\]. > \[1\] https://bugzilla.redhat.com/show_bug.cgi?id=1055577 > \[2\] https://bugzilla.redhat.com/show_bug.cgi?id=1181457 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7140) Injection with @EJB is not working as expected with CDI (REST) beans

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-7140?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-7140: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1377705|https://bugzilla.redhat.com/show_bug.cgi?id=1377705] from VERIFIED to CLOSED > Injection with @EJB is not working as expected with CDI (REST) beans > -------------------------------------------------------------------- > > Key: WFLY-7140 > URL: https://issues.jboss.org/browse/WFLY-7140 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, EJB > Reporter: Wolf-Dieter Fink > Assignee: Tomas Remes > Fix For: 11.0.0.Alpha1 > > > The injection with @EJB should work the same way in a Rest service (CDI Bean) as it does in a Servlet. > @EJB(lookup = "ejb:jboss-ejb-multi-server-app-one/ejb/AppOneBean!org.jboss.as.quickstarts.ejb.multi.server.app.AppOne") > is not working correct if used in a CDI Bean in the reproducer example. > Reproducer can be found here: > git@github.com:wfink/jboss-eap-quickstarts.git > BRANCH: 6.4.x_ejb-multi-server_reproducerEJB-injection > SubProject: ejb-multi-server (used only a part of it to have a web-app and a ejb-app) > see ejb-multi-server/README-reproducerEJB-injection -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1998) Custom NameService by sun.net.spi.nameservice.provider.n doesn't work on WildFly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1998?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1998: ------------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1395543|https://bugzilla.redhat.com/show_bug.cgi?id=1395543] from VERIFIED to CLOSED > Custom NameService by sun.net.spi.nameservice.provider.n doesn't work on WildFly > -------------------------------------------------------------------------------- > > Key: WFCORE-1998 > URL: https://issues.jboss.org/browse/WFCORE-1998 > Project: WildFly Core > Issue Type: Bug > Components: Modules > Affects Versions: 2.2.0.Final > Reporter: Osamu Nagano > Assignee: Osamu Nagano > Labels: downstream_dependency > Fix For: 3.0.0.Alpha13 > > Attachments: nameserviceProviderTest.zip > > > System property {{sun.net.spi.nameservice.provider.<n>}} allows a user to customize a NameService. It works on a standalone java, which is using JBoss Modules, if {{services="import"}} is added on sun.jdk module dependency and the sun.jdk module has the following additional dependencies. > {code} > <path name="sun/net/spi/nameservice"/> > <path name="sun/net/spi/nameservice/dns"/> > {code} > Though it doesn't work as a web application which has the same module path and the same dependency in jboss-deployment-structure.xml. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7150) EJB injection with indirection via web.xml is ignored

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-7150?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-7150: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1377705|https://bugzilla.redhat.com/show_bug.cgi?id=1377705] from VERIFIED to CLOSED > EJB injection with indirection via web.xml is ignored > ----------------------------------------------------- > > Key: WFLY-7150 > URL: https://issues.jboss.org/browse/WFLY-7150 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Web (Undertow) > Reporter: Wolf-Dieter Fink > Assignee: Stuart Douglas > Fix For: 11.0.0.Alpha1 > > > If a web application contains a Servlet and a REST service (as CDI Bean) with an @EJB(lookup="java:comp/env/xxxx") injection for a indirection via web.xml/jboss-web.xml the CDI Bean will ignore it without any message whereas the Servlet inject the EJB proxy as expected. > This approach is used to be able to change/adjust the target EJB by changing the DD and not the application code. > Reproducer can be found here: > git@github.com:wfink/jboss-eap-quickstarts.git > BRANCH: 6.4.x_ejb-multi-server_reproducerEJB-injection2 > SubProject: ejb-multi-server (used only a part of it to have a web-app and a ejb-app) > see ejb-multi-server/README-reproducerEJB-injection -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4168) jdr.sh CommandLineMain does not run jdr on the application server

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4168?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4168: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1195507|https://bugzilla.redhat.com/show_bug.cgi?id=1195507] from VERIFIED to CLOSED > jdr.sh CommandLineMain does not run jdr on the application server > ----------------------------------------------------------------- > > Key: WFLY-4168 > URL: https://issues.jboss.org/browse/WFLY-4168 > Project: WildFly > Issue Type: Bug > Components: JDR > Affects Versions: 9.0.0.Alpha1 > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: 9.0.0.Beta1 > > > jdr.sh CommandLineMain does not run jdr on the application server > JDR run via the CLI / Managemenet API - runs the JDR report in the Application Server's JVM > /subsystem=jdr:generate-jdr-report() > Running jdr.sh / jdr.bat runs the JDR report in the JDR JVM > jdr.sh / jdr.bat should run the JDR report in the Application Server's JVM if it is running. If it is not running, then it should just collect the files that are available. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7372) Hibernate Scanner implementation class shouldn't leak application entity classes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-7372?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-7372: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1390207|https://bugzilla.redhat.com/show_bug.cgi?id=1390207] from VERIFIED to CLOSED > Hibernate Scanner implementation class shouldn't leak application entity classes > -------------------------------------------------------------------------------- > > Key: WFLY-7372 > URL: https://issues.jboss.org/browse/WFLY-7372 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: JBoss AS7 7.2.0.Final, 10.1.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4957) After failback backup prints warnings to log

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4957?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4957: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1159290|https://bugzilla.redhat.com/show_bug.cgi?id=1159290] from VERIFIED to CLOSED > After failback backup prints warnings to log > -------------------------------------------- > > Key: WFLY-4957 > URL: https://issues.jboss.org/browse/WFLY-4957 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Alpha5 > Environment: Fedora 22 > openjdk 8 > Reporter: Erich Duda > Assignee: Jeff Mesnil > Priority: Critical > Fix For: 10.0.0.CR5 > > Attachments: master.xml, slave.xml > > > 15:34:59,123 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 4) WFLYMSGAMQ0004: Failed to destroy queue: ExpiryQueue: java.lang.IllegalStateException: Cannot access JMS Server, core server is not yet active > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.checkInitialised(JMSServerManagerImpl.java:1640) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.access$1100(JMSServerManagerImpl.java:101) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl$3.runException(JMSServerManagerImpl.java:752) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.runAfterActive(JMSServerManagerImpl.java:1847) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.removeQueueFromBindingRegistry(JMSServerManagerImpl.java:741) > at org.wildfly.extension.messaging.activemq.jms.JMSQueueService$2.run(JMSQueueService.java:101) > 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) > 15:34:59,123 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 68) WFLYMSGAMQ0004: Failed to destroy queue: AsyncQueue: java.lang.IllegalStateException: Cannot access JMS Server, core server is not yet active > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.checkInitialised(JMSServerManagerImpl.java:1640) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.access$1100(JMSServerManagerImpl.java:101) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl$3.runException(JMSServerManagerImpl.java:752) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.runAfterActive(JMSServerManagerImpl.java:1847) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.removeQueueFromBindingRegistry(JMSServerManagerImpl.java:741) > at org.wildfly.extension.messaging.activemq.jms.JMSQueueService$2.run(JMSQueueService.java:101) > 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) > 15:34:59,123 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 9) WFLYMSGAMQ0004: Failed to destroy queue: DLQ: java.lang.IllegalStateException: Cannot access JMS Server, core server is not yet active > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.checkInitialised(JMSServerManagerImpl.java:1640) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.access$1100(JMSServerManagerImpl.java:101) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl$3.runException(JMSServerManagerImpl.java:752) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.runAfterActive(JMSServerManagerImpl.java:1847) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.removeQueueFromBindingRegistry(JMSServerManagerImpl.java:741) > at org.wildfly.extension.messaging.activemq.jms.JMSQueueService$2.run(JMSQueueService.java:101) > 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) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4407) Upgrade wildfly-core to 1.0.0.Beta1

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4407?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4407: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1196686|https://bugzilla.redhat.com/show_bug.cgi?id=1196686] from VERIFIED to CLOSED > Upgrade wildfly-core to 1.0.0.Beta1 > ----------------------------------- > > Key: WFLY-4407 > URL: https://issues.jboss.org/browse/WFLY-4407 > Project: WildFly > Issue Type: Component Upgrade > Affects Versions: 9.0.0.Alpha1 > Reporter: Bartosz Baranowski > Assignee: Jason Greene > Fix For: 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4404) View does not inherit 'default' methods from interfaces( JDK8 )

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4404?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4404: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1196686|https://bugzilla.redhat.com/show_bug.cgi?id=1196686] from VERIFIED to CLOSED > View does not inherit 'default' methods from interfaces( JDK8 ) > --------------------------------------------------------------- > > Key: WFLY-4404 > URL: https://issues.jboss.org/browse/WFLY-4404 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 9.0.0.Alpha1 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 10.0.0.CR5 > > > View and View service do not inherit JDK8 'default' methods from interfaces. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-725) Remove ClassIndex from the server module

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-725?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-725: ------------------------------------------------ Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1196686|https://bugzilla.redhat.com/show_bug.cgi?id=1196686] from VERIFIED to CLOSED > Remove ClassIndex from the server module > ---------------------------------------- > > Key: WFCORE-725 > URL: https://issues.jboss.org/browse/WFCORE-725 > Project: WildFly Core > Issue Type: Task > Components: Server > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 2.0.0.Beta3 > > > ClassIndex is only used in a couple of places, and it is confusing to have two different indexes. It should be merged into ClassReflectionIndex. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 February 2017