August 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5259) DataSourceOperationsUnitTestCase fails with db other then h2

by Honza Brázdil (JIRA)

Honza Brázdil created AS7-5259: ---------------------------------- Summary: DataSourceOperationsUnitTestCase fails with db other then h2 Key: AS7-5259 URL: https://issues.jboss.org/browse/AS7-5259 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.1.2.Final (EAP) Reporter: Honza Brázdil Assignee: Stefano Maestri Tests in DataSourceOperationsUnitTestCase fails if run with other database then h2 (-Dds=...). The test should be independent on the ExampleDS datasource. {code} $ mvn install -Dds=mysql51 -rf testsuite/integration/smoke ... Results : Tests in error: testSendWithTxCommit(org.jboss.as.test.smoke.stilts.SimpleStompletTestCase): Connection timed out. testAddDsAndTestConnection(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testAddDisabledDsEnableItAndTestConnection(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testAddDsWithConnectionProperties(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testAddAndRemoveSameName(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testAddAndRemoveNameAndJndiNameDifferent(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testAddAndRemoveXaDs(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testMarshallUnmarshallXaDs(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." disableAndReEnableXaDs(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testAddXaDsWithProperties(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testAddComplexDs(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testAddComplexXaDs(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testXaDsWithSystemProperties(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testDsWithSystemProperties(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS014803: Duplicate resource [(\"system-property\" => \"sql.parameter\")]" {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

13 years, 8 months

4
6
0 / 0

[JBoss JIRA] (AS7-5312) Update to console 1.4.0.Final

by Heiko Braun (JIRA)

Heiko Braun created AS7-5312: -------------------------------- Summary: Update to console 1.4.0.Final Key: AS7-5312 URL: https://issues.jboss.org/browse/AS7-5312 Project: Application Server 7 Issue Type: Feature Request Components: Build System Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.3.Final (EAP) -- 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

13 years, 8 months

2
2
0 / 0

[JBoss JIRA] (AS7-5226) CLI: Allows adding a Datasource with both user-name+password and security-domain specified

by Thomas Hauser (JIRA)

Thomas Hauser created AS7-5226: ---------------------------------- Summary: CLI: Allows adding a Datasource with both user-name+password and security-domain specified Key: AS7-5226 URL: https://issues.jboss.org/browse/AS7-5226 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.2.Final (EAP) Reporter: Thomas Hauser Assignee: Stefano Maestri Running the command [standalone@localhost:9999 /] data-source add --name=TestDS1 --jndi-name=java:jboss/examples/TestDS1 --connection-url=localhost:8888/fake-url --driver-name=h2 --user-name=admin --password=something --security-domain=Management -- 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

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] (AS7-5331) @Resource UserTransaction should not be allowed in CMT beans

by Dominik Pospisil (JIRA)

Dominik Pospisil created AS7-5331: ------------------------------------- Summary: @Resource UserTransaction should not be allowed in CMT beans Key: AS7-5331 URL: https://issues.jboss.org/browse/AS7-5331 Project: Application Server 7 Issue Type: Bug Components: EJB, Transactions Affects Versions: 7.1.2.Final (EAP) Reporter: Dominik Pospisil Assignee: jaikiran pai Currently, it seems then @Resource UserTransaction injection is allowed in CMT beans and injects container managed transaction. In AS/EAP5 this would throw an exception which I think is correct as this violates EJB 3.0 & 3.1 specs. Section 16.12 of the EJB 3.1 specification says: The container must make the UserTransaction interface available to the enterprise beans that are allowed to use this interface (only session and message-driven beans with bean-managed transaction demarcation are allowed to use this interface) either through injection using the Resource annotation or in JNDI under the name java:comp/UserTransaction, in addition to through the EJBContext interface. The authenticationType and shareable elements of the Resource annotation must not be specified. In my interpretation the statement "only session and message-driven beans with bean-managed transaction demarcation are allowed to use this interface" would mean that other beans are prohibited to use this interface. Allowing such beans to use this interface is specification violation. -- 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

13 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-495) Memory leak in NAKACK

by Bela Ban (JIRA)

Memory leak in NAKACK --------------------- Key: JGRP-495 URL: http://jira.jboss.com/jira/browse/JGRP-495 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Priority: Blocker Fix For: 2.5 Probably due to the changes introduced in NAKACK/NakReceiverWindow (http://jira.jboss.com/jira/browse/JGRP-281). To reproduce, run perf.Test on 2 nodes with 1 million 1K messages each. JProfiler shows that we are leaking Map.Entry instances in NAKACK. They seem to accumulate in xmit_table. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] (AS7-5335) CLONE - JGroups protocol properties not always being applied to protocol configurations

by Richard Achmatowicz (JIRA)

Richard Achmatowicz created AS7-5335: ---------------------------------------- Summary: CLONE - JGroups protocol properties not always being applied to protocol configurations Key: AS7-5335 URL: https://issues.jboss.org/browse/AS7-5335 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.2.Final (EAP) Reporter: Richard Achmatowicz Assignee: Richard Achmatowicz Fix For: 7.1.3.Final (EAP) In JGroups subsystem processing, JGroups protocol properties are updated correctly in the model but not always correctly applied to the runtime configuration. For example, specifying an MPING.mcast_port as a property of the protocol MPING will be overridden by the value of the multicast port in the associated socket binding. -- 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

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] (AS7-5333) XaDataSourcePropertyAdd doesn't remove services on rollback

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5333: ------------------------------------- Summary: XaDataSourcePropertyAdd doesn't remove services on rollback Key: AS7-5333 URL: https://issues.jboss.org/browse/AS7-5333 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.2.Final (EAP) Reporter: Brian Stansberry Assignee: Jesper Pedersen Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 The handler doesn't register the ServiceController for the XaDataSourcePropertiesService it installs with the newControllers set, so it doesn't get removed on rollback. -- 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

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] (AS7-4723) Clustering TS: make the default stack SYNC and REPL

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-4723: ----------------------------------- Summary: Clustering TS: make the default stack SYNC and REPL Key: AS7-4723 URL: https://issues.jboss.org/browse/AS7-4723 Project: Application Server 7 Issue Type: Feature Request Components: Clustering, Test Suite Affects Versions: 7.1.1.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 7.1.2.Final (EAP) As per discussion with Jason on AS7 ML. This will enable us to * run faster (no sleep) * and avoid painful intermittent failures -- 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

13 years, 8 months

3
2
0 / 0

[JBoss JIRA] (AS7-5332) vault util requests a URL but expects an absolute path.

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-5332: ------------------------------------- Summary: vault util requests a URL but expects an absolute path. Key: AS7-5332 URL: https://issues.jboss.org/browse/AS7-5332 Project: Application Server 7 Issue Type: Bug Components: Security Affects Versions: 7.1.2.Final (EAP) Reporter: Darran Lofthouse Assignee: Anil Saldhana The vault utility asks for a URL to the keystore but then treats it as an absolute path: - {code} Enter Keystore URL:file:///home/darranl/tmp/vault/vault.keystore Enter Keystore password: Enter Keystore password again: Values match Enter 8 character salt:abcdefgh Enter iteration count as a number (Eg: 44):13 Exception encountered:Keystore [file:///home/darranl/tmp/vault/vault.keystore] doesn't exist. {code} Also is there really a need to take the password twice? That is normally used on setting a new password to ensure it is set correctly, in this case the password could easily be verified against the keystore. -- 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

13 years, 8 months

2
1
0 / 0

[JBoss JIRA] (AS7-5323) component upgrade to Hibernate 4.1.6

by Scott Marlow (JIRA)

Scott Marlow created AS7-5323: --------------------------------- Summary: component upgrade to Hibernate 4.1.6 Key: AS7-5323 URL: https://issues.jboss.org/browse/AS7-5323 Project: Application Server 7 Issue Type: Task Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 -- 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

13 years, 8 months

1
7
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 August 2012