September 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1362) FULL_XA infinispan caches need to properly register with TransactionManager for recovery.

by Paul Ferraro (JIRA)

FULL_XA infinispan caches need to properly register with TransactionManager for recovery. ----------------------------------------------------------------------------------------- Key: AS7-1362 URL: https://issues.jboss.org/browse/AS7-1362 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.1.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-3215) NPE when calling PackageBuilder.addPackageFromDrl(Reader)

by Jean-Marc Vanel (JIRA)

NPE when calling PackageBuilder.addPackageFromDrl(Reader) --------------------------------------------------------- Key: JBRULES-3215 URL: https://issues.jboss.org/browse/JBRULES-3215 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.3.0.Beta1 Environment: % uname -a Linux oem-laptop 2.6.32-5-amd64 #1 SMP Fri Sep 9 20:23:16 UTC 2011 x86_64 GNU/Linux % java -version java version "1.7.0" Java(TM) SE Runtime Environment (build 1.7.0-b147) Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode) Reporter: Jean-Marc Vanel Assignee: Mark Proctor Daemon Thread [SwingWorker-pool-3-thread-1] (Suspended (breakpoint at line 89 in ClassUtils)) ClassUtils.canonicalName(Class) line: 89 DeclarationTypeFixer.fix(Declaration) line: 11 JavaRuleBuilderHelper.createVariableContext(String, String, RuleBuildContext, Declaration[], Declaration[], Map<String,Class<?>>) line: 158 JavaRuleBuilderHelper.createConsequenceContext(RuleBuildContext, String, String, String, Map<String,Declaration>, BoundIdentifiers) line: 94 ASMConsequenceStubBuilder(AbstractASMConsequenceBuilder).consequenceContext(RuleBuildContext, String) line: 47 ASMConsequenceStubBuilder(AbstractASMConsequenceBuilder).build(RuleBuildContext, String) line: 17 RuleBuilder.build(RuleBuildContext) line: 99 PackageBuilder.addRule(RuleDescr) line: 1993 PackageBuilder.addPackage(PackageDescr) line: 793 PackageBuilder.addPackageFromDrl(Reader) line: 355 NOTE: with the debugger, I saw that variable $JTEXT_FIELD is causing the problem; see the DRL below in "how to reproduce" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (AS7-1209) Xa-datasource:add requires a non-empty map "xa-data-source-properties", which is not documented

by Heiko Rupp (JIRA)

Xa-datasource:add requires a non-empty map "xa-data-source-properties", which is not documented ----------------------------------------------------------------------------------------------- Key: AS7-1209 URL: https://issues.jboss.org/browse/AS7-1209 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.CR1 Reporter: Heiko Rupp Assignee: Brian Stansberry [domain@localhost:9999 subsystem=datasources] ./xa-data-source=xa-ds:read-operation-description(name=add) does not list a (required) property "xa-data-source-properties", but when this is not provided, adding a xa-datasource fails and console shows [Server:server-two] 15:25:52,983 WARN [org.jboss.as.controller] (pool-1-thread-35) Operation ("add") failed - address: ([ [Server:server-two] ("subsystem" => "datasources"), [Server:server-two] ("xa-data-source" => "postgres") [Server:server-two] ]): java.lang.IllegalArgumentException Adding an empty xa-data-source-properties map also makes the :add fail. It only works when this property is present and some (dummy!) values are given. 1) the requirement for this xa-da.. should be documented 2) it should be optional 3) an empty map should be allowed (if no xa-props are needed) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-1924) XaDataSourceService does not set UserTransactionJndiName during deployment

by Bob McWhirter (JIRA)

XaDataSourceService does not set UserTransactionJndiName during deployment -------------------------------------------------------------------------- Key: AS7-1924 URL: https://issues.jboss.org/browse/AS7-1924 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.0.2.Final Reporter: Bob McWhirter Assignee: Jesper Pedersen The XaDataSourceService doesn't set the UserTransactionJndiName, so it defaults to java:/UserTransaction, which seems invalid within the context of AS7. In-line commit comment here: https://github.com/jbossas/jboss-as/commit/7fd76db27e89e40e9a16243fc05846... Additionally, setting up the URL delimeter uses the dataSourceConfig instead of the xaDataSourceConfig, but that seems harmless, so far. In TorqueBox, we hacked around: https://github.com/torquebox/torquebox/blob/7f51e360749d8093fc291fbf238b7... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JGRP-1227) Discovery protocol based on GoGrid

by Bela Ban (JIRA)

Discovery protocol based on GoGrid ---------------------------------- Key: JGRP-1227 URL: https://jira.jboss.org/browse/JGRP-1227 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 Similar to S3_PING (Amazon), create a discovery protocol (extending FILE_PING) which uses Rackspace's distributed store -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-8560) Tech opinion on JBAS-6244

by Misty Stanley-Jones (JIRA)

Tech opinion on JBAS-6244 ------------------------- Key: JBAS-8560 URL: https://jira.jboss.org/browse/JBAS-8560 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Misty Stanley-Jones Assignee: Jonathan Halliday I need to know if JBAS-6244 (https://jira.jboss.org/browse/JBAS-6244) is still relevant and whether this has already been documented or not. The JIRA and linked articles are extremely old, and I have gotten zero feedback from GSS on this. Jonathan, can you have a quick glance over it and let me know who I might talk ti about it? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8717) JBoss 6 RC1 crash when using MOD_JK

by Kleber Rocha (JIRA)

JBoss 6 RC1 crash when using MOD_JK ----------------------------------- Key: JBAS-8717 URL: https://jira.jboss.org/browse/JBAS-8717 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.CR1 Environment: Linux CEntOS 5.5, JDK 1.6.0_23-b05 Reporter: Kleber Rocha JBoss work fine, but when I configure Apache with mod_jk and I start a connection, JBoss crash and create a file hs_err_pidXXXX.log, with this information: # JRE version: 6.0_23-b05 # Java VM: Java HotSpot(TM) 64-Bit Server VM (19.0-b09 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libapr-1.so.0+0x1b58f] apr_pollset_add+0x8f This don´t happen with M5. Exist any workaround for this? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
5
0 / 0

[JBoss JIRA] Created: (AS7-1869) Specifying dependency on JPA service.

by Jeff Yu (JIRA)

Specifying dependency on JPA service. ------------------------------------- Key: AS7-1869 URL: https://issues.jboss.org/browse/AS7-1869 Project: Application Server 7 Issue Type: Feature Request Components: JPA / Hibernate Affects Versions: 7.0.1.Final Reporter: Jeff Yu Assignee: Scott Marlow Fix For: 7.1.0.Alpha1 In RiftSaw project, we want to make sure when we starting that RiftSaw service, the JPA service has been started already. So we need to a way to specify this dependency. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (AS7-1703) Add module names to be used for 3rd party (external) JPA persistence providers (helpful for testing)

by Scott Marlow (JIRA)

Add module names to be used for 3rd party (external) JPA persistence providers (helpful for testing) ---------------------------------------------------------------------------------------------------- Key: AS7-1703 URL: https://issues.jboss.org/browse/AS7-1703 Project: Application Server 7 Issue Type: Task Components: JPA / Hibernate Affects Versions: 7.0.1.Final Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.1.0.Beta1 for example, if provider="oracle.toplink.essentials.ejb.cmp3.EntityManagerFactoryProvider", the provider module name and provider adapter should be pre-determined or generated based on the provider class name. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-3219) Build fails if Fact Model contains fields starting with an upper case letter

by Mario Fusco (JIRA)

Build fails if Fact Model contains fields starting with an upper case letter ---------------------------------------------------------------------------- Key: JBRULES-3219 URL: https://issues.jboss.org/browse/JBRULES-3219 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco Priority: Minor Build fails if Fact Model contains fields starting with an upper case letter. Also reported in bugzilla as: https://bugzilla.redhat.com/show_bug.cgi?id=724350 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
2
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 September 2011