January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2293) Classpath resources being scanned by ResourceChangeScanner could cause improper resource removal

by Steve Ronderos (JIRA)

Classpath resources being scanned by ResourceChangeScanner could cause improper resource removal ------------------------------------------------------------------------------------------------ Key: JBRULES-2293 URL: https://jira.jboss.org/jira/browse/JBRULES-2293 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.0.1.FINAL Environment: Windows XP Java 5 Running in Oracle OC4J 10.1.3.2 Reporter: Steve Ronderos Assignee: Mark Proctor I encountered an issue today with my KnowledgeAgent removing resources from its RuleBase shortly after creating it. I have the ResourceChangeScanner running in my application. I tracked the issue back to the scan() method in ResourceChangeScannerImpl. It appears that the method is trying to identify resources that are no longer available and remove them from both the RuleBase and future scans. To do this it is checking lastModified on the resource and on a result of 0 removing the resource. The resources that I configured in my change-set definitely still exist, but due to URL handler implementation provided by my classloader, getLastModified always returns 0. (The resource I'm retrieving is coming from a jar that is in my application's classpath and the URL handler implementation is oracle.classloader.SharedCodeSourceURL) Full Email Group trail: http://www.nabble.com/Issue-with-ResourceChangeScanner-td25792358.html Michael recommends to never scan classpath resources. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

6
13
0 / 0

[JBoss JIRA] Created: (JBAS-8383) enable xml deployments

by Alexey Loubyansky (JIRA)

enable xml deployments ---------------------- Key: JBAS-8383 URL: https://jira.jboss.org/browse/JBAS-8383 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.M1 At the moment deployments in the domain/standalone are expected to be zip archives. -- 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, 3 months

6
10
0 / 0

[JBoss JIRA] Created: (JBAS-8334) error handling during service deployment

by Alexey Loubyansky (JIRA)

error handling during service deployment ---------------------------------------- Key: JBAS-8334 URL: https://jira.jboss.org/browse/JBAS-8334 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Deployers Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.M1 Errors thrown during service deployment should be properly handled and logged. This task is a main/general one. Each deployment error scenario will be added as a subtask of this one. -- 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, 3 months

5
7
0 / 0

[JBoss JIRA] Created: (JBAS-8335) handling of deployment failed to be added to the MSC batch

by Alexey Loubyansky (JIRA)

handling of deployment failed to be added to the MSC batch ---------------------------------------------------------- Key: JBAS-8335 URL: https://jira.jboss.org/browse/JBAS-8335 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Fix For: 7.0.0.M1 A deployment can fail to be added to the MSC batch. For example, a service may be attempted to be defined which already exists in the batch (in fact, at present this is the only possible error outside of outright code bugs). In this event, the correct thing to do is to log the error and continue. -- 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, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1880) Can fire rules after disposing the Stateful session

by Sravanthi Tipirneni (JIRA)

Can fire rules after disposing the Stateful session --------------------------------------------------- Key: JBRULES-1880 URL: https://jira.jboss.org/jira/browse/JBRULES-1880 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.7 Reporter: Sravanthi Tipirneni Assignee: Mark Proctor Priority: Minor I can access the session and fire rules even after the session is disposed using the dispose method -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-8337) handling of deployment failed at batch resolve time

by Alexey Loubyansky (JIRA)

handling of deployment failed at batch resolve time --------------------------------------------------- Key: JBAS-8337 URL: https://jira.jboss.org/browse/JBAS-8337 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.M1 Types of failures here include: duplicate service definition (i.e. a service was defined that already exists in the container), missing required dependency (i.e. a service was defined that depends on something that isn't there), circular dependency (i.e. two or more service definitions represent circularity in terms of their dependency links). Right now this erases the entire batch, which means that the server cannot start if any of these errors occur. The correct behavior is, in my opinion, to log each error and continue, possibly yielding a report of problem services after the batch is resolved (it is likely, however, that one failure will lead to others). -- 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, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-8336) handling of deployment failed the validation on the domain controller

by Alexey Loubyansky (JIRA)

handling of deployment failed the validation on the domain controller --------------------------------------------------------------------- Key: JBAS-8336 URL: https://jira.jboss.org/browse/JBAS-8336 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Fix For: 7.0.0.M1 A deployment can fail validation on the domain controller. In this event, the deployment is not added to the domain and an error is thrown from the deployer API, so this does not impact the server. -- 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, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-8412) Algorithms for generating server names

by Brian Stansberry (JIRA)

Algorithms for generating server names -------------------------------------- Key: JBAS-8412 URL: https://jira.jboss.org/browse/JBAS-8412 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.M1 Right now we're identifying servers by the static "name" attribute value in the host.xml server element. We need pluggable algorithms for other mechanisms to come up with a name, particularly for cloud use cases. -- 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, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2124) KnowledgeAgent should load knowledge bases directly from Resource (bypassing the ChangeSet)

by Jürgen Schiewe (JIRA)

KnowledgeAgent should load knowledge bases directly from Resource (bypassing the ChangeSet) ------------------------------------------------------------------------------------------- Key: JBRULES-2124 URL: https://jira.jboss.org/jira/browse/JBRULES-2124 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-api, drools-core Affects Versions: 5.0.1.FINAL Reporter: Jürgen Schiewe Assignee: Mark Proctor We develop Drools based applications and use Guvnor as a a repository. Hard-coding the hostname where Guvnor runs is not an option for us because the names are different in each installation and we do not want to modify all the changeset.xml files for each deployment. Instead we would pass one (or more) Resources to the KnowledgeAgent and let it do the monitoring. This would allow us to build URLs dynamically from our system environment configuration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JGRP-1001) Use ByteMan / Metronome to inject faults for testing

by Bela Ban (JIRA)

Use ByteMan / Metronome to inject faults for testing ---------------------------------------------------- Key: JGRP-1001 URL: https://jira.jboss.org/jira/browse/JGRP-1001 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 Use ByteMan (jboss.org/byteman) to simulate issues that can happen at runtime: do this in unit tests. For example: crash of merge leader after initial round (who frees the locks ?) (same for FLUSH) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

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