April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2841) BinaryHeapQueueAgendaGroup fails to return top salience item

by k s (JIRA)

BinaryHeapQueueAgendaGroup fails to return top salience item ------------------------------------------------------------ Key: JBRULES-2841 URL: https://issues.jboss.org/browse/JBRULES-2841 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.1.1.FINAL Reporter: k s Assignee: Mark Proctor We have come across a case where the rules engine does not fire the top priority (top salience) rule. After a lot of careful debugging, it seems that the BinaryHeapQueueAgendaGroup implementation (and most likely the supporting BinaryHeapQueue) has a bug. It is not a common case and it was hard to reproduce. We have put together a junit test to show the problem. The test "replays" the trace from the case where we show the error (sparing you from all the complexity of the actual rules and produced it). I will attach the JUnit test and the trace file that drives the test. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-9358) Can't invoke read-config-as-xml on the host

by Brian Stansberry (JIRA)

Can't invoke read-config-as-xml on the host ------------------------------------------- Key: JBAS-9358 URL: https://issues.jboss.org/browse/JBAS-9358 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.Beta3 java.lang.RuntimeException: "No handler for read-config-as-xml at address [(\"host\" => \"local\")]" at org.jboss.as.demos.domain.interactive.runner.ExampleRunner.executeForResult(ExampleRunner.java:1265) at org.jboss.as.demos.domain.interactive.runner.ExampleRunner.writeHostController(ExampleRunner.java:336) at org.jboss.as.demos.domain.interactive.runner.ExampleRunner.dumpHostController(ExampleRunner.java:320) I suspect the handler got dropped. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBJCA-555) Add testConnection to pool api

by Jesper Pedersen (JIRA)

Add testConnection to pool api ------------------------------ Key: JBJCA-555 URL: https://issues.jboss.org/browse/JBJCA-555 Project: IronJacamar Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Beta6 Add a testConnection() method to the pool api, such that receiving a connection can be tested from the management layer. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-588) Try to load classes from defining classloader before delegating to TCCL

by Marcus Moyses (JIRA)

Try to load classes from defining classloader before delegating to TCCL ----------------------------------------------------------------------- Key: SECURITY-588 URL: https://issues.jboss.org/browse/SECURITY-588 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Enhancement Security Level: Public (Everyone can see) Components: PicketBox Affects Versions: PicketBox_v4_0_alpha8 Reporter: Marcus Moyses Assignee: Marcus Moyses Fix For: PicketBox_v4_0_beta1 Most classes in PicketBox try to use the TCCL by default to load classes. We need to try and load classes from the defining classloader (the one that loaded the current class) before delegating classloading to TCCL. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-587) SecurityContextFactory defaults to TCCL

by Jesper Pedersen (JIRA)

SecurityContextFactory defaults to TCCL --------------------------------------- Key: SECURITY-587 URL: https://issues.jboss.org/browse/SECURITY-587 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: Security SPI Affects Versions: PicketBox_v4_0_alpha8 Reporter: Jesper Pedersen Assignee: Marcus Moyses The SecurityContextFactory defaults to using the TCCL for loading classes. The order should be: 1) Passed in ClassLoader 2) ClassLoader that defined SecurityContextFactory 3) TCCL -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-9357) add 'exit' as an alternative to 'quit'

by Alexey Loubyansky (JIRA)

add 'exit' as an alternative to 'quit' -------------------------------------- Key: JBAS-9357 URL: https://issues.jboss.org/browse/JBAS-9357 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.Beta4 Witnessed numerous attempts to hit 'exit' instead of 'quit' to terminate the cli session, I'm adding 'exit' as an alternative alias. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9340) Separate the HTTP server management from the context management.

by Darran Lofthouse (JIRA)

Separate the HTTP server management from the context management. ---------------------------------------------------------------- Key: JBAS-9340 URL: https://issues.jboss.org/browse/JBAS-9340 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse This change is to separate the HTTP server control from the contexts, this should make it easier to add and remove additional contexts and also to remove the dependency on a specific context. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-9348) Provide JBAS-9010 result report to operation's ResultHandler

by Brian Stansberry (JIRA)

Provide JBAS-9010 result report to operation's ResultHandler ------------------------------------------------------------ Key: JBAS-9348 URL: https://issues.jboss.org/browse/JBAS-9348 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.Beta3 The JBAS-9010 fix puts error reports in the log, but the ResultHandler always gets handleResultComplete() which results in a "success" response. Track newly added failures or missing dependencies and pass them to handleFailed(). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9182) Unify failure description key

by Heiko Rupp (JIRA)

Unify failure description key ----------------------------- Key: JBAS-9182 URL: https://issues.jboss.org/browse/JBAS-9182 Project: JBoss Application Server Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta1 Reporter: Heiko Rupp The "standard" failure description in standalone mode { "outcome" : "failed", "failure-description" : [{ "PROPERTY_VALUE" : { "java.lang.IllegalArgumentException" : "Invalid key specification" } }] } note "failure-description" Sometimes it is different: [localhost:9999 /] /server-group=new:add(profile=default) { "outcome" => "failed", "result" => {"domain-failure-description" => [("java.lang.IllegalStateException" => "Resource at address [(\"server-group\" => \"new\")] already exists")]} } note "domain-failure-description". Please unify that. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-9350) Optional parameter to read-resource-description to include inherited methods or not

by Kabir Khan (JIRA)

Optional parameter to read-resource-description to include inherited methods or not ----------------------------------------------------------------------------------- Key: JBAS-9350 URL: https://issues.jboss.org/browse/JBAS-9350 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 7.0.0.Beta4 There were some comments on JBAS-8922, and when looking at the model to check it for errors, I needed a way to get rid of the noise from the inherited ops. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
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 April 2011