July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-907) Provide means to cancel an edit operation within the UI

by Heiko Braun (JIRA)

Provide means to cancel an edit operation within the UI ------------------------------------------------------- Key: AS7-907 URL: https://issues.jboss.org/browse/AS7-907 Project: Application Server 7 Issue Type: Enhancement Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.CR1 hbraun: Just an idea when playing with the console. If for example I am editing a queue's information and I want to cancel, I should be able to do that. At the moment I can only see 'Save' and 'Delete -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (JBRULES-3124) Compiler should be able to report warnings

by Mikael Lönneberg (JIRA)

Compiler should be able to report warnings ------------------------------------------ Key: JBRULES-3124 URL: https://issues.jboss.org/browse/JBRULES-3124 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.2.0.Final Reporter: Mikael Lönneberg Assignee: Mark Proctor Fix For: FUTURE 1) add warnings list to packagebuilder 2) add hasWarnings and getWarnings, in mirror of errors. 3) allow hashWarnings and getWarnings to take positive/negative warnings. i.e. ignore duplicate resource (hasWarnings would return false), report duplicate file (is returned in list). This should be some sort of chainable or compositable filter, with sane defaults. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[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, 7 months

2
2
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, 7 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, 7 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, 7 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, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2995) Field "class" not recognized in some constructs

by Wolfgang Laun (JIRA)

Field "class" not recognized in some constructs ----------------------------------------------- Key: JBRULES-2995 URL: https://issues.jboss.org/browse/JBRULES-2995 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.2.0.CR1 Reporter: Wolfgang Laun Assignee: Mark Proctor Given this simple type: declare Foo clazz : Class end and this rule: rule yyy when $f: Foo( $cl: clazz == ( java.lang.String.class ) ) ### $f: Foo( $cl: clazz, eval( $f.getClazz().equals( java.lang.String.class ) ) ) ### $f: Foo( $cl: clazz == java.lang.String.class ) then System.out.println( "--- got a " + $cl ); end Only the first vyariant is accepted by the DRL parser. Other forms are rebuked with, e.g.: Unable to Analyse Expression $f.getClazz().equals( java.lang.String.class ) : [Error: Failed to compile: 2 compilation error(s): - (1,24) unable to resolve method using strict-mode: ex10.Foo.java() - (1,24) unqualified type in strict mode for: java] [Near : {... $f.getClazz().equals( java.lang.String.class ) ....}] ^ [Line: 1, Column: 24] : [Rule name='yyy'] Note the incorrect line number! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-3123) .rf file raises a null pointer exception when it is loaded

by Quentin Caillard (JIRA)

.rf file raises a null pointer exception when it is loaded ---------------------------------------------------------- Key: JBRULES-3123 URL: https://issues.jboss.org/browse/JBRULES-3123 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.2.0.Final Reporter: Quentin Caillard Assignee: Mark Proctor I have just switched from version 5.1.1 to 5.2.0.Final I have a ruleflow (.rf) file which can be loaded. I have the following stack trace : java.lang.NullPointerException at org.drools.compiler.PackageBuilder.addProcessFromXml(PackageBuilder.java:516) at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:556) at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:28) at com.ariadnext.NewDroolsTest$RulesUtils.loadRules(NewDroolsTest.java:106) I made a simple junit test which reproduces the bug. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
16
0 / 0

[JBoss JIRA] Created: (JBRULES-3140) NullPointerException thrown on JPA synchronization.afterCompletion() clearProcessInstances()

by Nick Bruno (JIRA)

NullPointerException thrown on JPA synchronization.afterCompletion() clearProcessInstances() -------------------------------------------------------------------------------------------- Key: JBRULES-3140 URL: https://issues.jboss.org/browse/JBRULES-3140 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.2.0.Final Reporter: Nick Bruno Assignee: Mark Proctor In org.drools.persistence.SingleSessionCommandService$SynchronizationImpl.afterCompletion(), the following generates a NullPointerException when no processes are implemented. {noformat}if ( ksession != null ) { ((InternalKnowledgeRuntime) ksession).getProcessRuntime().clearProcessInstances(); // NullPointerException ((JPAWorkItemManager) ksession.getWorkItemManager()).clearWorkItems(); } {noformat} The fix is to grab the InternalProcessRuntime to a local variable and test if it is null before calling clearProcessInstances(), as so: {noformat}InternalProcessRuntime ipr = ((InternalKnowledgeRuntime) ksession).getProcessRuntime(); if( ipr != null) { ipr.clearProcessInstances(); }{noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
3
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 July 2011