September 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1984) DataSource pool config: Modification fails

by Heiko Braun (JIRA)

DataSource pool config: Modification fails ------------------------------------------ Key: AS7-1984 URL: https://issues.jboss.org/browse/AS7-1984 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.Beta1 [Host Controller] 15:02:28,221 ERROR [org.jboss.as.controller] (HttpManagementService-threads - 5) Operation ("write-attribute") failed - address: ([ [Host Controller] ("profile" => "default"), [Host Controller] ("subsystem" => "datasources"), [Host Controller] ("xa-data-source" => "myXA") [Host Controller] ]) - failure description: "Invalid parameter name: value" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1986) Ability to specify datasource connection properties

by Heiko Braun (JIRA)

Ability to specify datasource connection properties --------------------------------------------------- Key: AS7-1986 URL: https://issues.jboss.org/browse/AS7-1986 Project: Application Server 7 Issue Type: Feature Request Components: JCA Reporter: Heiko Braun Assignee: Jesper Pedersen Fix For: 7.1.0.Beta1 anything tat goes into <connection-property/> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1973) CLI - modify-data-source does not work

by Dominik Pospisil (JIRA)

CLI - modify-data-source does not work -------------------------------------- Key: AS7-1973 URL: https://issues.jboss.org/browse/AS7-1973 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Dominik Pospisil Assignee: Brian Stansberry This operation used to work in Alpha1 but does not work anymore: [standalone@localhost:9999 /] add-data-source --jndi-name=java:jboss/datasources/TestDS --driver-name=h2 --pool-name=TestDS --connection-url=jdbc:h2:mem:test;DB_CLOSE_DELAY=-1 [standalone@localhost:9999 /] modify-data-source --jndi-name=java:jboss/datasources/TestDS --idle-timeout-minutes=5 The result is: {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "Invalid parameter name: value"}} Error logged: 12:46:07,903 ERROR [org.jboss.as.controller] (pool-3-thread-3) Operation ("write-attribute") failed - address: ([ ("subsystem" => "datasources"), ("data-source" => "java:jboss/datasources/TestDS") ]) - failure description: "Invalid parameter name: value" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBJCA-678) IronJacamar 1.1.0.Alpha2

by Jesper Pedersen (JIRA)

IronJacamar 1.1.0.Alpha2 ------------------------ Key: JBJCA-678 URL: https://issues.jboss.org/browse/JBJCA-678 Project: IronJacamar Issue Type: Release Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Alpha2 Release notes: https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310691&versi... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-626) Issues building JBoss Negotiation with updated assembly plug-in (Version 2.2.1)

by Darran Lofthouse (JIRA)

Issues building JBoss Negotiation with updated assembly plug-in (Version 2.2.1) ------------------------------------------------------------------------------- Key: SECURITY-626 URL: https://issues.jboss.org/browse/SECURITY-626 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.3.Beta2 Reporter: Darran Lofthouse Assignee: Anil Saldhana -- 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: (AS7-1980) The Management Console lets me delete all the server groups and then I can't add one.

by Misty Stanley-Jones (JIRA)

The Management Console lets me delete all the server groups and then I can't add one. ------------------------------------------------------------------------------------- Key: AS7-1980 URL: https://issues.jboss.org/browse/AS7-1980 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: Open To Community Environment: Fedora 15, Git pull 6e719b8. Reporter: Misty Stanley-Jones Assignee: Heiko Braun Since you have to choose a server group to "base" your new server group on, if you delete all of the server groups, you can't create a new one in the Management Console. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
6
0 / 0

[JBoss JIRA] Created: (AS7-1669) The Web Management Console does not allow a new Server to be defined on a Host if the Host has no existing servers

by Rich Raposa (JIRA)

The Web Management Console does not allow a new Server to be defined on a Host if the Host has no existing servers ------------------------------------------------------------------------------------------------------------------ Key: AS7-1669 URL: https://issues.jboss.org/browse/AS7-1669 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: No Release Environment: RHEL6, EAP 6 Alpha1 Reporter: Rich Raposa Assignee: Heiko Braun The host.xml file comes pre-configured with three servers. Using the Management Console, if you delete all the servers, then you can no longer add one to that particular host. You can try - but the new server ends up on a different host than the one you have selected in the "Host" dropdown menu. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (AS7-1923) Switch to version 1.1 of domain schema be default.

by Darran Lofthouse (JIRA)

Switch to version 1.1 of domain schema be default. -------------------------------------------------- Key: AS7-1923 URL: https://issues.jboss.org/browse/AS7-1923 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse (At this stage 1.0 is only supported for parsing - discussion will continue re trying to support minimum schema version or original schema version on marshalling) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
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

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