February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2277) i18n for jaxr subsystem

by Thomas Diesler (Created) (JIRA)

i18n for jaxr subsystem ----------------------- Key: AS7-2277 URL: https://issues.jboss.org/browse/AS7-2277 Project: Application Server 7 Issue Type: Task Components: JAXR Reporter: Thomas Diesler Assignee: Thomas Diesler Extract log and error messages to resource bundle. This task should be done when there is a reasonable working system -- 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, 11 months

3
2
0 / 0

[JBoss JIRA] (AS7-2700) Connections participating in transactions should not be eligable for idle-timeouts

by Nicklas Karlsson (Created) (JIRA)

Connections participating in transactions should not be eligable for idle-timeouts ---------------------------------------------------------------------------------- Key: AS7-2700 URL: https://issues.jboss.org/browse/AS7-2700 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.0.Alpha1 Reporter: Nicklas Karlsson Assignee: Jesper Pedersen Scott Marlow: I think the other part of the bug, is that connections shouldn't "idle-timeout" if they are enlisted into a transaction (which I believe should mean they are eligible for sharing). In other words, I believe the following should work: 1. set idle-timeout-minutes=1 (currently this is 1 millisecond but 1 minute should also work). 2. JTA transaction begins. 3. Hibernate gets a non-xa resource X1 (database connection), enlists it into the transaction. 4. Hibernate inserts a row into a database table using X1. 5. Hibernate closes X1 which shouldn't make X1 eligible for idle-timeout handling, since it is still enlisted in the transaction. 6. Hibernate gets a non-xa resource, X1 should be returned. Imagine that two minutes has elapsed since the transaction started, X1 should not be idle-timed out. 7. Hibernate inserts another row into a database table using the resource that should still be X1. If the resource is not X1, the "ARJUNA12140: Adding multiple last resources is disallowed" error will occur. 8. The JTA transaction is committed successfully. Maybe the IJ "idle-timeout" test case could simulate the above with a test case that doesn't run always but maybe is run selectively. I think the unit test will have to run for over a minute once the conversion error is fixed (e.g. since idle-timeout-minutes will be treated as minutes instead of milliseconds). -- 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, 11 months

9
9
0 / 0

[JBoss JIRA] (AS7-3192) Property expansion stopped working in datasource connection-url

by Stian Thorgersen (Created) (JIRA)

Property expansion stopped working in datasource connection-url --------------------------------------------------------------- Key: AS7-3192 URL: https://issues.jboss.org/browse/AS7-3192 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.0.CR1b Reporter: Stian Thorgersen On 7.0.2.Final it was possible to use property expansion in the datasource connection-url, which is very useful for example when using embedded Apache Derby to specify that it should store the db in AS7's data directory. The following worked fine on 7.0.2.Final, but stopped working in 7.1.0.CR1b (not tested on other 7.1.0.X versions): {code} <connection-url>jdbc:derby:${jboss.server.data.dir}/mydb;create=true</connection-url> {code} Without property expansion, and with property expansion not available for system-properties either (see AS7-2579) it is rather difficult to make sure the db for an embedded database is saved within the AS7 data 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

13 years, 11 months

3
2
0 / 0

[JBoss JIRA] (AS7-3433) DataSource's <url-delimiter> value is ignored by AS7DataSourceDeployer

by Xi CHEN (JIRA)

Xi CHEN created AS7-3433: ---------------------------- Summary: DataSource's <url-delimiter> value is ignored by AS7DataSourceDeployer Key: AS7-3433 URL: https://issues.jboss.org/browse/AS7-3433 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.0.CR1 Environment: JBoss 7.1.0.CR1, MS SQL Sever 2005/2008 Reporter: Xi CHEN We try to use <datasource ... > <connection-url>jdbc:sqlserver://SERVER_ONE:1433;databaseName=MyDB|jdbc:sqlserver://SERVER_TWO:1433;databaseName=MyDB</connection-url> <url-delimiter>|</url-delimiter> ... </datasource> to treate database failover case, but it doesn't work in JBoss 7.1.0.CR1. It just use the first connection url. By looking at the code source of jboss connector ( in org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.java), I found the url-delimiter's value is never set into LocalManagedConnectionFactory. -- 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, 11 months

3
3
0 / 0

[JBoss JIRA] (AS7-2569) Datasource name bound in Naming Service is not the jndi-name attribute

by Rich Raposa (Created) (JIRA)

Datasource name bound in Naming Service is not the jndi-name attribute ----------------------------------------------------------------------- Key: AS7-2569 URL: https://issues.jboss.org/browse/AS7-2569 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.0.Alpha1 Reporter: Rich Raposa Here is my datasource definition: "data-source" => { "JBTravel" => { "jndi-name"=>"java:jboss/JBTravelDatasource" ...other settings } } When I do a JNDI lookup for "JBTravel", it's found successfully. If I do a JNDI lookup for "java:jboss/JBTravelDatasource", I get a NameNotFoundException. I think the wrong name is getting bound in the naming service. -- 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, 11 months

5
5
0 / 0

[JBoss JIRA] Created: (JGRP-1325) TopologyUUID.isSameSite() returns false if both siteIds are null

by Dan Berindei (JIRA)

TopologyUUID.isSameSite() returns false if both siteIds are null ---------------------------------------------------------------- Key: JGRP-1325 URL: https://issues.jboss.org/browse/JGRP-1325 Project: JGroups Issue Type: Bug Affects Versions: 2.12.1 Reporter: Dan Berindei Assignee: Bela Ban Priority: Minor When the siteId of both TopologyUUIDs is null, isSameSite() should return true but it returns false. Same with rackId/isSameRack() and machineId/isSameMachine(). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9106) In domain mode, prevent end-user access to and visibility of most configuration write operations

by Brian Stansberry (JIRA)

In domain mode, prevent end-user access to and visibility of most configuration write operations ------------------------------------------------------------------------------------------------ Key: JBAS-9106 URL: https://issues.jboss.org/browse/JBAS-9106 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta4 In domain mode most (almost certainly all) server level operations that update the persistent configuration should not be directly accessible by the end user and should not appear in the results of the read-resource-description, read-operation-names or read-operation-description operations if executed against a server-level resource. They can only be invoked by the host controller that is responsible for the server. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

5
8
0 / 0

[JBoss JIRA] (JBJCA-742) Annotation based resource adapter without @Connector fails

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-742: ------------------------------------- Summary: Annotation based resource adapter without @Connector fails Key: JBJCA-742 URL: https://issues.jboss.org/browse/JBJCA-742 Project: IronJacamar Issue Type: Bug Components: Common Affects Versions: 1.1.0.Alpha5, 1.0.7.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Critical Fix For: 1.0.8.Final, 1.1.0.Alpha6 An annotation based resource adapter without a @Connector fails -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] (JBAOP-810) jboss-aop (single jar) build failed

by gil cattaneo (JIRA)

gil cattaneo created JBAOP-810: ---------------------------------- Summary: jboss-aop (single jar) build failed Key: JBAOP-810 URL: https://issues.jboss.org/browse/JBAOP-810 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Components: Aspect Library Affects Versions: 2.2.2.GA Environment: Java-Version: 1.7.0_b147-icedtea Os-Arch: i386 Os-Name: Linux Os-Version: 3.2.2-desktop586-1.mga2 Reporter: gil cattaneo Priority: Minor [INFO] --- maven-assembly-plugin:2.2.2:attached (single) @ jboss-aop --- [INFO] Reading assembly descriptor: src/assembly/single.xml [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Skipping JBoss AOP Parent POM [INFO] This project has been banned from the build due to previous failures. [INFO] ------------------------------------------------------------------------ [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] JBoss AOP Parent POM .............................. SUCCESS [1.937s] [INFO] JBoss AOP Framework ............................... FAILURE [13:05.747s] [INFO] JBoss AOP Maven Plugin ............................ SKIPPED [INFO] JBoss AOP Pluggable Instrumentor .................. SKIPPED [INFO] JBoss AOP Aspects ................................. SKIPPED [INFO] JBoss AOP AS Integration Core ..................... SKIPPED [INFO] JBoss AOP Helper .................................. SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 13:16.522s [INFO] Finished at: Mon Feb 06 14:26:14 CET 2012 [INFO] Final Memory: 48M/909M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.2.2:attached (single) on project jboss-aop: Failed to create assembly: Error creating assembly archive single: Failed to retrieve numeric file attributes using: '/bin/sh -c ls -1nlaR /' -> [Help 1] -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] (AS7-3636) Multi deployment does not work for Arquillian for AS7 protocol

by Ondřej Chaloupka (JIRA)

Ondřej Chaloupka created AS7-3636: ------------------------------------- Summary: Multi deployment does not work for Arquillian for AS7 protocol Key: AS7-3636 URL: https://issues.jboss.org/browse/AS7-3636 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.1.0.CR1b Reporter: Ondřej Chaloupka Assignee: Aslak Knutsen Priority: Minor For Arquillian the multideployment does not work over AS7 protocol. This issue was discussed with Aslak Knutsen and you can check the forum https://community.jboss.org/message/714601 for more details. When you want to create two deployments (two jars to deploy) in a one test file and each deployment has its own test (test operates on the deployment) then test does not find correct module in which is executed. One test passes while second one fails with CNFE when it tries to make JNDI lookup for own session bean. The test class is like this: {code} @Deployment(managed=true, testable = true, name = "postconstruct", order = 1) public static Archive<?> deploy() { ... return jar1; } @Deployment(managed=true, testable = true, name = "postconstruct2", order = 2) public static Archive<?> deploy2() { ... return jar2; } @Test @OperateOnDeployment("postconstruct") public void test() throws NamingException { CountedSessionBean bean = (CountedSessionBean) ctx.lookup("java:global/postconstruct/" + CountedSessionBean.class.getSimpleName()); ... } @Test @OperateOnDeployment("postconstruct2") public void test2() { CountedSessionBean2 bean = (CountedSessionBean2) ctx.lookup("java:global/postconstruct2/" + CountedSessionBean2.class.getSimpleName()); ... } {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, 11 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 2012