April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-785) Ignore transactions for non JTA datasources

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-785: ------------------------------------- Summary: Ignore transactions for non JTA datasources Key: JBJCA-785 URL: https://issues.jboss.org/browse/JBJCA-785 Project: IronJacamar Issue Type: Bug Components: Deployer, JDBC Affects Versions: 1.1.0.Alpha6, 1.0.9.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.10.Final, 1.1.0.Alpha7 A non JTA datasource doesn't ignore the transaction status in all cases -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
1
0 / 0

[JBoss JIRA] (AS7-4418) Atrribute <factory-type> is not parsed correctly in configuration of connection-factory

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/AS7-4418?page=com.atlassian.jira.plugin.s... ] Jason Greene moved JBPAPP-8644 to AS7-4418: ------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-4418 (was: JBPAPP-8644) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: (was: EAP 6.0.0 ER 4) Component/s: JMS (was: HornetQ) Security: (was: Public) Fix Version/s: 7.1.2.Final-redhat1 (was: EAP 6.0.0 ER 5) Docs QE Status: (was: NEW) > Atrribute <factory-type> is not parsed correctly in configuration of connection-factory > --------------------------------------------------------------------------------------- > > Key: AS7-4418 > URL: https://issues.jboss.org/browse/AS7-4418 > Project: Application Server 7 > Issue Type: Bug > Components: JMS > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Labels: eap6_need_triage > Fix For: 7.1.2.Final-redhat1 > > > Attribute factory-type in configuration connection factory is not parsed correctly and default "CF" type is always used. > Following configuration should register XAConnectionFactory but attribute factory-type is ignored: > {code} > <connection-factory name="RemoteConnectionFactory"> > > <jms-connection-factories> > ... > <connection-factory name="RemoteConnectionFactory"> > <factory-type>XA_GENERIC</factory-type> > <connectors> > <connector-ref connector-name="netty"/> > </connectors> > <entries> > <entry name="RemoteConnectionFactory"/> > <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/> > </entries> > <ha>true</ha> > </connection-factory> > ... > </jms-connection-factories> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (AS7-4418) Atrribute <factory-type> is not parsed correctly in configuration of connection-factory

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/AS7-4418?page=com.atlassian.jira.plugin.s... ] Jason Greene commented on AS7-4418: ----------------------------------- Hi Jeff, can you look at this? > Atrribute <factory-type> is not parsed correctly in configuration of connection-factory > --------------------------------------------------------------------------------------- > > Key: AS7-4418 > URL: https://issues.jboss.org/browse/AS7-4418 > Project: Application Server 7 > Issue Type: Bug > Components: JMS > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Labels: eap6_need_triage > Fix For: 7.1.2.Final-redhat1 > > > Attribute factory-type in configuration connection factory is not parsed correctly and default "CF" type is always used. > Following configuration should register XAConnectionFactory but attribute factory-type is ignored: > {code} > <connection-factory name="RemoteConnectionFactory"> > > <jms-connection-factories> > ... > <connection-factory name="RemoteConnectionFactory"> > <factory-type>XA_GENERIC</factory-type> > <connectors> > <connector-ref connector-name="netty"/> > </connectors> > <entries> > <entry name="RemoteConnectionFactory"/> > <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/> > </entries> > <ha>true</ha> > </connection-factory> > ... > </jms-connection-factories> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (AS7-4417) permissions for security roles are not redefined by jboss-ejb3.xml

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/AS7-4417?page=com.atlassian.jira.plugin.s... ] Jason Greene moved JBPAPP-8643 to AS7-4417: ------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-4417 (was: JBPAPP-8643) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: (was: EAP 6.0.0 ER 4) Security: (was: Public) Fix Version/s: 7.1.2.Final-redhat1 (was: TBD EAP 6) Docs QE Status: (was: NEW) > permissions for security roles are not redefined by jboss-ejb3.xml > ------------------------------------------------------------------ > > Key: AS7-4417 > URL: https://issues.jboss.org/browse/AS7-4417 > Project: Application Server 7 > Issue Type: Bug > Reporter: Radim Hatlapatka > Assignee: Stuart Douglas > Labels: descriptor, eap6_need_triage, security > Fix For: 7.1.2.Final-redhat1 > > > When I have defined permissions using security roles in ejb-jar.xml (ejb-spec) for certain methods and if I define them differently in jboss-ejb3.xml (jboss-spec) the permissions remain as their are defined in ejb-jar.xml. But I would expect that ejb-spec will redefine the permissions (because merging is not possible). > For details see written tests here: https://github.com/rhatlapa/jboss-as/commit/62adba59b288a53672a6b08c8a710... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (AS7-2694) OperationContext.isBooting() is returning false in domain mode boots

by Brian Stansberry (Created) (JIRA)

OperationContext.isBooting() is returning false in domain mode boots -------------------------------------------------------------------- Key: AS7-2694 URL: https://issues.jboss.org/browse/AS7-2694 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Fix For: 7.1.0.CR1 OperationContext.isBooting() is returning false in domain mode boots. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
3
0 / 0

[JBoss JIRA] (AS7-4409) Add Keystore alias support to security realm keystore definition.

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4409: ------------------------------------- Summary: Add Keystore alias support to security realm keystore definition. Key: AS7-4409 URL: https://issues.jboss.org/browse/AS7-4409 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.2.Final-redhat1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
1
0 / 0

[JBoss JIRA] (AS7-4416) Collect module.xml files during JDR collection

by Jesse Jaggars (JIRA)

Jesse Jaggars created AS7-4416: ---------------------------------- Summary: Collect module.xml files during JDR collection Key: AS7-4416 URL: https://issues.jboss.org/browse/AS7-4416 Project: Application Server 7 Issue Type: Enhancement Components: JDR Affects Versions: 7.1.1.Final Reporter: Jesse Jaggars Assignee: Jesse Jaggars JDR should collect module.xml files from the modules/ directory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-9360) MessagingClientTestCase is not using a deterministic approach to determining queue existence

by Jason Greene (JIRA)

MessagingClientTestCase is not using a deterministic approach to determining queue existence -------------------------------------------------------------------------------------------- Key: JBAS-9360 URL: https://issues.jboss.org/browse/JBAS-9360 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Jason Greene Clebert suggests the issue may be with having a session factory open. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

5
11
0 / 0

[JBoss JIRA] (AS7-4415) Default up handler of Channel created by jgroups subsystem interferes with custom receivers.

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-4415: --------------------------------- Summary: Default up handler of Channel created by jgroups subsystem interferes with custom receivers. Key: AS7-4415 URL: https://issues.jboss.org/browse/AS7-4415 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.1.2.Final-redhat1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (AS7-2480) Intermittent failure in JMSQueueManagementTestCase

by Brian Stansberry (Created) (JIRA)

Intermittent failure in JMSQueueManagementTestCase -------------------------------------------------- Key: AS7-2480 URL: https://issues.jboss.org/browse/AS7-2480 Project: Application Server 7 Issue Type: Task Components: JMS Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.0.CR1 Failed tests: testMessageRemoval(org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase): expected:<[success]> but was:<[failed]> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

5
6
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 April 2012