October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1963) Rollback leaves files undeleted on Windows

by Emanuel Muckenhuber (JIRA)

[ https://issues.jboss.org/browse/WFLY-1963?page=com.atlassian.jira.plugin.... ] Emanuel Muckenhuber resolved WFLY-1963. --------------------------------------- Resolution: Done > Rollback leaves files undeleted on Windows > ------------------------------------------ > > Key: WFLY-1963 > URL: https://issues.jboss.org/browse/WFLY-1963 > Project: WildFly > Issue Type: Bug > Components: Patching > Reporter: Jan Martiska > Assignee: Emanuel Muckenhuber > Priority: Blocker > > When rolling back a patch on Windows, if some of its files are still used (eg. active modules), file locking prevents the rollback process to delete them. We need a solution probably cleaning up these files when the server is being restarted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1963) Rollback leaves files undeleted on Windows

by Emanuel Muckenhuber (JIRA)

[ https://issues.jboss.org/browse/WFLY-1963?page=com.atlassian.jira.plugin.... ] Emanuel Muckenhuber updated WFLY-1963: -------------------------------------- Fix Version/s: 8.0.0.CR1 > Rollback leaves files undeleted on Windows > ------------------------------------------ > > Key: WFLY-1963 > URL: https://issues.jboss.org/browse/WFLY-1963 > Project: WildFly > Issue Type: Bug > Components: Patching > Reporter: Jan Martiska > Assignee: Emanuel Muckenhuber > Priority: Blocker > Fix For: 8.0.0.CR1 > > > When rolling back a patch on Windows, if some of its files are still used (eg. active modules), file locking prevents the rollback process to delete them. We need a solution probably cleaning up these files when the server is being restarted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-101) JMSService.start is doing blocking I/O

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-101?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-101: ---------------------------------------------- Jeff Mesnil <jmesnil(a)redhat.com> made a comment on [bug 1003913|https://bugzilla.redhat.com/show_bug.cgi?id=1003913] (In reply to Miroslav Novak from comment #5) > Problem is "[WFLY-101] JMSService.start to perform blocking I/O > asynchronously" I guess only way to verify is to read the code, right? That's correct, there is no observable way to verify this. Reading the code, it appears that the JMSService.start/stop methods performs HornetQ-related operations asynchronously in a separate executor: https://github.com/jmesnil/jboss-eap/commit/161295de1ae35a10c53dcc8f4fce9... > JMSService.start is doing blocking I/O > -------------------------------------- > > Key: WFLY-101 > URL: https://issues.jboss.org/browse/WFLY-101 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > flag the start context as asynchronous -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1741) RBAC: Response headers don't match payload structure

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-1741?page=com.atlassian.jira.plugin.... ] Heiko Braun closed WFLY-1741. ----------------------------- Resolution: Rejected > RBAC: Response headers don't match payload structure > ---------------------------------------------------- > > Key: WFLY-1741 > URL: https://issues.jboss.org/browse/WFLY-1741 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Braun > Assignee: Brian Stansberry > > the 'relative-address' header doesn't match the response structure: > (hint: the 'data-source' element is missing) > {noformat} > [standalone@localhost:9990 /] /subsystem=datasources:read-children-resources(child-type=data-source){roles=monitor} > { > "outcome" => "success", > "result" => { > "ExampleDS" => { > "allocation-retry" => undefined, > "allocation-retry-wait-millis" => undefined, > [...] } > }, > "response-headers" => {"access-control" => [ { > "absolute-address" => [ > ("subsystem" => "datasources"), > ("data-source" => "ExampleDS") > ], > "relative-address" => [("data-source" => "ExampleDS")], > "filtered-attributes" => [ > "user-name", > "security-domain", > "password" > ] > } > ]} > } > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1650) Legacy subsystem testing needs some classloading exclusion mecanism

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1650?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1650: ----------------------------------------------- Pavel Jelinek <pjelinek(a)redhat.com> changed the Status of [bug 980923|https://bugzilla.redhat.com/show_bug.cgi?id=980923] from ON_QA to ASSIGNED > Legacy subsystem testing needs some classloading exclusion mecanism > ------------------------------------------------------------------- > > Key: WFLY-1650 > URL: https://issues.jboss.org/browse/WFLY-1650 > Project: WildFly > Issue Type: Bug > Components: Logging, Test Suite > Affects Versions: 8.0.0.Alpha3 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Fix For: 8.0.0.Beta1 > > > When translation messages are used (which is the case of EAP) we have conflicts between generated $logger classes when testing submodules. > Some $logger classes exis thus they are loaded by the parent classloader before the childfirstclassloader tries to load them, thus we have a potential ClassCastException brewing. > For exemple this breaks the EAP build on a French OS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1650) Legacy subsystem testing needs some classloading exclusion mecanism

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1650?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1650: ----------------------------------------------- Pavel Jelinek <pjelinek(a)redhat.com> made a comment on [bug 980923|https://bugzilla.redhat.com/show_bug.cgi?id=980923] Tests mentioned above pass, but for EAP 6.2.0 ER4 with fr_FR locale there are still some failing tests: org.jboss.as.jpa.subsystem.JPA11SubsystemTestCase.testTransformers7_1_2 org.jboss.as.jpa.subsystem.JPA11SubsystemTestCase.testTransformersRejectExpressions7_1_2 org.jboss.as.modcluster.ModClusterSubsystemTestCase.testTransformers712 org.jboss.as.modcluster.ModClusterSubsystemTestCase.testExpressionsAreRejected712 org.jboss.as.osgi.parser.OSGiSubsystemTestCase.testTransformerAS712 org.jboss.as.osgi.parser.OSGiSubsystemTestCase.testRejectExpressionsAS712 See: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-60-as-testsuite-... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-60-as-testsuite-... > Legacy subsystem testing needs some classloading exclusion mecanism > ------------------------------------------------------------------- > > Key: WFLY-1650 > URL: https://issues.jboss.org/browse/WFLY-1650 > Project: WildFly > Issue Type: Bug > Components: Logging, Test Suite > Affects Versions: 8.0.0.Alpha3 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Fix For: 8.0.0.Beta1 > > > When translation messages are used (which is the case of EAP) we have conflicts between generated $logger classes when testing submodules. > Some $logger classes exis thus they are loaded by the parent classloader before the childfirstclassloader tries to load them, thus we have a potential ClassCastException brewing. > For exemple this breaks the EAP build on a French OS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-290) Can't parse condition as FieldConstraintDescr in 5.5.0

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-290?page=com.atlassian.jira.plugin... ] Davide Sottara edited comment on DROOLS-290 at 10/8/13 2:31 AM: ---------------------------------------------------------------- Constraints are handled differently in 5.5 than 5.0. In later versions, you can have "free-form" constraints as opposed to simpler <Field OP Value>. This is not a bug. Are you manipulating the Descr tree yourself? Those classes have never been part of the public API, as far as I know was (Author: dsotty): Constraints are handled differently in 5.5 as opposed to 5.0. In later versions, you can have "free-form" constraints as opposed to simpler <Field OP Value>. This is not a bug. Are you manipulating the Descr tree yourself? Those classes have never been part of the public API, as far as I know > Can't parse condition as FieldConstraintDescr in 5.5.0 > ------------------------------------------------------ > > Key: DROOLS-290 > URL: https://issues.jboss.org/browse/DROOLS-290 > Project: Drools > Issue Type: Release > Security Level: Public(Everyone can see) > Environment: jdk1.6.0.25 > Reporter: Paul Qing > Assignee: Mark Proctor > > hi everyone, > I met a issue when I upgrade drools from 5.0.1 to 5.5.0. when I parse a rule in the 5.5.0. It will parse condition as ExprConstraintDescr. However,It can parse this condition as FieldConstraintDescr in the 5.0.1. I don't know that this is a bug or not. the rule is as following: > rule "guy_13" > when > $g:Guy(age==13) > then > return true; > end > the root cause is the parser has parsed "$g:Guy(age==13)" as ExprConstraintDescr in the 5.5.0 and it can work in the 5.0.1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-291) ClassCastException during constraint jitting when an interface is used for implementation and traiting

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-291: ------------------------------------- Summary: ClassCastException during constraint jitting when an interface is used for implementation and traiting Key: DROOLS-291 URL: https://issues.jboss.org/browse/DROOLS-291 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.CR4, 5.5.0.Final Reporter: Davide Sottara Assignee: Mark Proctor Priority: Critical The following combination is needed: - an interface IX with at least one getter/setter pair - a trait IY extending IX - a class K implementing IX - a jittable constraint on IX The constraint is first triggered by an "instance" of IY, but jitted by an instance of K. The condition analyzer assumes that IY is the natural domain of the constratint, rather than IX. The jitted constraint will then try to cast K to IY, resulting in a disruptive CCE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2255) ManagedAuditLoggerImpl doesn't replace handlers correctly

by Josef Cacek (JIRA)

Josef Cacek created WFLY-2255: --------------------------------- Summary: ManagedAuditLoggerImpl doesn't replace handlers correctly Key: WFLY-2255 URL: https://issues.jboss.org/browse/WFLY-2255 Project: WildFly Issue Type: Bug Components: Logging Affects Versions: 8.0.0.Beta1 Reporter: Josef Cacek Assignee: Josef Cacek -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-290) Can't parse condition as FieldConstraintDescr in 5.5.0

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-290?page=com.atlassian.jira.plugin... ] Davide Sottara commented on DROOLS-290: --------------------------------------- Constraints are handled differently in 5.5 as opposed to 5.0. In later versions, you can have "free-form" constraints as opposed to simpler <Field OP Value>. This is not a bug. Are you manipulating the Descr tree yourself? Those classes have never been part of the public API, as far as I know > Can't parse condition as FieldConstraintDescr in 5.5.0 > ------------------------------------------------------ > > Key: DROOLS-290 > URL: https://issues.jboss.org/browse/DROOLS-290 > Project: Drools > Issue Type: Release > Security Level: Public(Everyone can see) > Environment: jdk1.6.0.25 > Reporter: Paul Qing > Assignee: Mark Proctor > > hi everyone, > I met a issue when I upgrade drools from 5.0.1 to 5.5.0. when I parse a rule in the 5.5.0. It will parse condition as ExprConstraintDescr. However,It can parse this condition as FieldConstraintDescr in the 5.0.1. I don't know that this is a bug or not. the rule is as following: > rule "guy_13" > when > $g:Guy(age==13) > then > return true; > end > the root cause is the parser has parsed "$g:Guy(age==13)" as ExprConstraintDescr in the 5.5.0 and it can work in the 5.0.1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
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 October 2013