May 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1241) Remove javaee module

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-1241?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-1241: -------------------------------------- This module should not actually be removed, but should be removed from all implicit dependencies. > Remove javaee module > -------------------- > > Key: WFLY-1241 > URL: https://issues.jboss.org/browse/WFLY-1241 > Project: WildFly > Issue Type: Task > Components: EE > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > Rather than having one module that imports all the JavaEE API's they should be imported individually so excludes will work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-735) spnego AdvancedLdapLoginModule cannot cope with roles contains a slash

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-735?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-735: -------------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 953513|https://bugzilla.redhat.com/show_bug.cgi?id=953513] from MODIFIED to ON_QA > spnego AdvancedLdapLoginModule cannot cope with roles contains a slash > ---------------------------------------------------------------------- > > Key: SECURITY-735 > URL: https://issues.jboss.org/browse/SECURITY-735 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_2_2 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_2_3 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-82) Wrong injection made by container

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-82?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-82: --------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 909914|https://bugzilla.redhat.com/show_bug.cgi?id=909914] from MODIFIED to ON_QA > Wrong injection made by container > --------------------------------- > > Key: WFLY-82 > URL: https://issues.jboss.org/browse/WFLY-82 > Project: WildFly > Issue Type: Bug > Components: EE, EJB, JPA / Hibernate > Reporter: Luan Cestari > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > > Description of problem: > I got an issue in a salesforce case [1] about an incorrect injection. > [1] https://c.na7.visual.force.com/apex/Case_View?id=500A000000CRqDG&sfdc.ove... > Version-Release number of selected component (if applicable): > How reproducible: > To reproduce the case is required to have two PersistentUnit (PU), a Abstract class with a setter method to inject one PU and others classes inheriting the Abstract class and overriding the setter method to inject a different PU. In the runtime, the container inject twice the PU, first the correct PU and then the PU described in super class. > I talked with the client (who is a Red Hat consultant) and we made the attached project based on a very simple JBoss example to reproduce the issue which happens in EAP6. I put a lot of 'println' to be very clear (even printing stacktrace to show who is calling). The most important files are: > -> hibernate4Test/src/main/java/org/jboss/as/quickstart/hibernate4/data/BaseDAO.java -- The abstract class with the default PU injection > -> hibernate4Test/src/main/java/org/jboss/as/quickstart/hibernate4/data/MemberRepository.java -- BaseDAO subclass > -> hibernate4Test/src/main/java/org/jboss/as/quickstart/hibernate4/data/SecondaryMemberRepository.java -- BaseDAO subclass > -> hibernate4Test/src/main/java/org/jboss/as/quickstart/hibernate4/data/MemberListProducer.java -- The class which inject the MemberListProducer and SecondaryMemberRepository > -> hibernate4Test/src/main/resources/META-INF/persistence.xml -- We changed the configuration here to each PU have a different entity mapped > Steps to Reproduce: > > Actual results: > The EM injection occurs twice, which the last one the wrong EM. > Expected results: > Just one injection occurs. > Additional info: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-88) Recovery not fully triggered when distributed transaction falls down at prepare phase of 2PC

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-88?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-88: --------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 952746|https://bugzilla.redhat.com/show_bug.cgi?id=952746] from MODIFIED to ON_QA > Recovery not fully triggered when distributed transaction falls down at prepare phase of 2PC > -------------------------------------------------------------------------------------------- > > Key: WFLY-88 > URL: https://issues.jboss.org/browse/WFLY-88 > Project: WildFly > Issue Type: Bug > Components: EJB, Remoting > Reporter: Ivo Studensky > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha1 > > Attachments: logs_prepareHaltClient.tgz > > > It looks like recovery process is not fully triggered on a distributed transaction when the transaction falls down at prepare phase of 2PC. In the new crash recovery tests over propagated transactions only one of two servers recovers from the crash, but the other keeps an unfinished tx in its tx log. > It corresponds to prepareHaltClient and prepareHaltServer test methods of org.jboss.as.test.jbossts.crashrec.txpropagation.TxPropagationCrashRecoveryTestCase, see JBQA-2604 for general description of the new tests. The prepareHaltClient test crashes the server which initiated the transaction, while as the prepareHaltServer test crashes the second server. > The tests are written against EAP6.x branch, so for reproducing this it is needed a built server from the 7.1 branch of AS7. > Steps to reproduce. > 1. git clone -b as7 git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-transactions.git > 2. cd eap-tests-transactions > 3. git checkout tx_propag_crashrec_tests > 4a. mvn clean verify -Dtest=TxPropagationCrashRecoveryTestCase#prepareHaltClient -Djboss.dist=<path to jboss-as-7.1.3.Final-SNAPSHOT> > or > 4b. mvn clean verify -Dtest=TxPropagationCrashRecoveryTestCase#prepareHaltServer -Djboss.dist=<path to jboss-as-7.1.3.Final-SNAPSHOT> > The logs of prepareHaltClient run attached to this jira. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1278) Upgrade HornetQ to 2.3.0.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1278?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1278: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 956278|https://bugzilla.redhat.com/show_bug.cgi?id=956278] from MODIFIED to ON_QA > Upgrade HornetQ to 2.3.0.Final > ------------------------------ > > Key: WFLY-1278 > URL: https://issues.jboss.org/browse/WFLY-1278 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > HornetQ 2.3.0.Final depends on Netty 3.6.2.Final which is the version in WildFly (no need to also upgrade Netty) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-737) spnego AdvancedLdapLoginModule cannot cope with roles contains a slash

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-737?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-737: -------------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 953513|https://bugzilla.redhat.com/show_bug.cgi?id=953513] from MODIFIED to ON_QA > spnego AdvancedLdapLoginModule cannot cope with roles contains a slash > ---------------------------------------------------------------------- > > Key: SECURITY-737 > URL: https://issues.jboss.org/browse/SECURITY-737 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_1_3 > Reporter: Tom Fonteyne > Assignee: Tom Fonteyne > > cloned from: https://bugzilla.redhat.com/show_bug.cgi?id=953513 > back port for EAP 5.x upstream -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-736) Tag and release JBoss Negotiation 2.2.3

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-736?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-736: -------------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 955555|https://bugzilla.redhat.com/show_bug.cgi?id=955555] from MODIFIED to ON_QA > Tag and release JBoss Negotiation 2.2.3 > --------------------------------------- > > Key: SECURITY-736 > URL: https://issues.jboss.org/browse/SECURITY-736 > Project: PicketBox > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_2_3 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-413) Upgrade to JBoss Negotiation 2.2.3

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-413?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-413: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 955555|https://bugzilla.redhat.com/show_bug.cgi?id=955555] from MODIFIED to ON_QA > Upgrade to JBoss Negotiation 2.2.3 > ---------------------------------- > > Key: WFLY-413 > URL: https://issues.jboss.org/browse/WFLY-413 > Project: WildFly > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-112) pooled connection factory does not define an application security policy

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-112?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-112: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 951188|https://bugzilla.redhat.com/show_bug.cgi?id=951188] from MODIFIED to ON_QA > pooled connection factory does not define an application security policy > ------------------------------------------------------------------------ > > Key: WFLY-112 > URL: https://issues.jboss.org/browse/WFLY-112 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Critical > Fix For: 8.0.0.Alpha1 > > > From a customer case, it appears that AS7 pooled-connection-factory does not set an application security policy for its JCA pool. > This implies a performance overhead since destroying a connection implies having to creating a new one every time (https://docspace.corp.redhat.com/docs/DOC-101004#IJ000612_Destroying_a_co...) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-115) JMSService error during :reload operation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-115?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-115: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 951649|https://bugzilla.redhat.com/show_bug.cgi?id=951649] from MODIFIED to ON_QA > JMSService error during :reload operation > ----------------------------------------- > > Key: WFLY-115 > URL: https://issues.jboss.org/browse/WFLY-115 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > if the admin client performs a :reload operation, the JMSService throws an exception and HornetQ server is not stopped properly and do not release its resources: > {noformat} > 20:01:54,480 ERROR [org.jboss.messaging] (MSC service thread 1-1) JBAS011602: Exception while stopping JMS server: java.lang.IllegalStateException: Service already removed > at org.jboss.msc.service.ServiceControllerImpl.internalSetMode(ServiceControllerImpl.java:792) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl.internalSetMode(ServiceControllerImpl.java:775) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl.setMode(ServiceControllerImpl.java:754) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.as.messaging.jms.JMSService$1.deActivate(JMSService.java:103) [jboss-as-messaging-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT] > at org.hornetq.core.server.impl.HornetQServerImpl.callDeActiveCallbacks(HornetQServerImpl.java:1374) [hornetq-server-2.3.0.CR2.jar:] > at org.hornetq.core.server.impl.HornetQServerImpl.stop(HornetQServerImpl.java:598) [hornetq-server-2.3.0.CR2.jar:] > at org.hornetq.core.server.impl.HornetQServerImpl.stop(HornetQServerImpl.java:542) [hornetq-server-2.3.0.CR2.jar:] > at org.hornetq.core.server.impl.HornetQServerImpl.stop(HornetQServerImpl.java:509) [hornetq-server-2.3.0.CR2.jar:] > at org.hornetq.jms.server.impl.JMSServerManagerImpl.stop(JMSServerManagerImpl.java:502) [hornetq-jms-server-2.3.0.CR2.jar:] > at org.jboss.as.messaging.jms.JMSService.stop(JMSService.java:119) [jboss-as-messaging-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2082) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2043) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_15] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_15] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_15] > {noformat} > When the HornetQ server is reloaded, it fails to lock its lock files that were not properly released during stop. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 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 May 2013