March 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-465) Cannot find KieModule with LATEST

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-465?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-465: ------------------------------------------------ Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1303018|https://bugzilla.redhat.com/show_bug.cgi?id=1303018] from MODIFIED to ON_QA > Cannot find KieModule with LATEST > --------------------------------- > > Key: DROOLS-465 > URL: https://issues.jboss.org/browse/DROOLS-465 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Beta1 > Reporter: Takami Hirata > Assignee: Mario Fusco > Fix For: 6.4.0.Beta2 > > Attachments: reproducer.zip > > > I install a kmodule into local repository with command {{mvn clean install}}. > Loading this kmodule with 'LATEST' works on the day, but will fail on next day. > Maven will find update on next day because of default updatePolicy 'daily', then maven check local repository ({{org.kie.scanner.Aether}} treats as a remote repository) but local artifact cache does not have 'maven-metadata.xml' which remote artifact should have, so finding update fails and {{org.sonatype.aether.connector.file.FileRepositoryWorker}} removes {{maven-metadata-local.xml}} for cleanup. > {{org.kie.scanner.Aether}} adds local repository to remote repositories, but this may be incorrect usage. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6311) Add bouncycastle artefacts required by Camel integration

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-6311?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated WFLY-6311: --------------------------------- Description: CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/1111 > Add bouncycastle artefacts required by Camel integration > -------------------------------------------------------- > > Key: WFLY-6311 > URL: https://issues.jboss.org/browse/WFLY-6311 > Project: WildFly > Issue Type: Task > Components: Security > Affects Versions: 10.0.0.Final > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 10.1.0.Final > > > CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/1111 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6311) Add bouncycastle artefacts required by Camel integration

by Thomas Diesler (JIRA)

Thomas Diesler created WFLY-6311: ------------------------------------ Summary: Add bouncycastle artefacts required by Camel integration Key: WFLY-6311 URL: https://issues.jboss.org/browse/WFLY-6311 Project: WildFly Issue Type: Task Components: Security Affects Versions: 10.0.0.Final Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 10.1.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2492) <valid-connection-checker> does not have module attribute

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-2492?page=com.atlassian.jira.plugin.... ] Lin Gao commented on WFLY-2492: ------------------------------- Maybe we can work around this by adding an optional module: {{org.jboss.ironjacamar.addons}} like what does in https://issues.jboss.org/browse/WFLY-6301? So that customers can wrap their extension classes into this module? > <valid-connection-checker> does not have module attribute > --------------------------------------------------------- > > Key: WFLY-2492 > URL: https://issues.jboss.org/browse/WFLY-2492 > Project: WildFly > Issue Type: Feature Request > Components: JCA > Affects Versions: 8.0.0.Beta1 > Reporter: James Livingston > Assignee: Lin Gao > > A datasource's <valid-connection-checker> element lets you specify the class name. It does not let you specify the module name, so you can only use IJ-provided ones. It should let you specify a module name too, so you can use custom connection checkers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6310) Populate the ModifiableResourceAdapter with all information presents before RaOperationUtil.buildResourceAdaptersObject is invoked

by Lin Gao (JIRA)

Lin Gao created WFLY-6310: ----------------------------- Summary: Populate the ModifiableResourceAdapter with all information presents before RaOperationUtil.buildResourceAdaptersObject is invoked Key: WFLY-6310 URL: https://issues.jboss.org/browse/WFLY-6310 Project: WildFly Issue Type: Bug Components: JCA Affects Versions: 10.0.0.Final Reporter: Lin Gao Assignee: Lin Gao Services are used to bring this data into the ModifiableResourceAdapter, the entire process of populating the data becomes multi-threaded, and therefore more complex and fragile. OTOH, if, when RaOperationUtil.buildResourceAdaptersObject is invoked, the Resource tree is in a state where all the relevant config information is present, the thread invoking RaOperationUtil can simply read that data and populate the object. Single threaded. Consider the full lifecycle of RA resource and subresource: RA can be added boot time reading xml and immediately activated RA can be added runtime by :add operations and then manually activated calling :activate operation I think the point is to run this RaOperationUtil.buildResourceAdaptersObject with all information presents. The bug should only at boot time though because in latter case is reponsible of human user/batch to call :activate only when all resources have been created. More context information can be found at PR: https://github.com/wildfly/wildfly/pull/8592 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-515) ConfigurationFile.successfulBoot() may try to write in an unwriteable dir

by Yeray Santana Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-515?page=com.atlassian.jira.plugin... ] Yeray Santana Borges commented on WFCORE-515: --------------------------------------------- [~brian.stansberry] Any suggestions about what to do if there is no enough rights to write in mainFile location? > ConfigurationFile.successfulBoot() may try to write in an unwriteable dir > ------------------------------------------------------------------------- > > Key: WFCORE-515 > URL: https://issues.jboss.org/browse/WFCORE-515 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > > ConfigurationFile.successfulBoot() creates a temp file when persistOriginal is false. It locates it in the same directory as mainFile, but in the !persistOriginal case, mainFile may point to any location, not necessarily to something in the configuration dir, and its directory may not be writable by the WildFly process. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-336) Ability for Deployment Overlays to overlay System Properties

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-336?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-336: ----------------------------------------- If WildFly full's ee subsystem is configured, WildFly supports using deployment specific properties in expression resolution. The properties are read from file META-INF/jboss.properties, if present. So using file overlays for that file should provide something pretty close to the requested functionality. > Ability for Deployment Overlays to overlay System Properties > ------------------------------------------------------------ > > Key: WFCORE-336 > URL: https://issues.jboss.org/browse/WFCORE-336 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Joshua Henn > > Currently Deployment Overlays allow only the replacing whole resource files. It would be nice to also be able to overlay System Properties that take precedent over globally defined properties. > ie. > {code:xml} > <deployment-overlays> > <deployment-overlay name="myOverlay"> > <system-properties> > <property name="datasource" value="java:jboss/datasources/controller"/> > </system-properties> > <deployment name="controller.war"/> > </deployment-overlay> > </deployment-overlays> > {code} > Usecase: > Have two deployments active of the same application, run-time configured by descriptor replacements via System Properties. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6309) Bad defaults in Undertow subsystem

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-6309: ------------------------------------ Summary: Bad defaults in Undertow subsystem Key: WFLY-6309 URL: https://issues.jboss.org/browse/WFLY-6309 Project: WildFly Issue Type: Bug Components: Web (Undertow) Reporter: Stuart Douglas Assignee: Stuart Douglas There is no connection timeout and pipeline buffering is enabled. The lack of timeout is especially problematic as it can result in FD exhaustion if browsers hold onto connections for long periods -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6308) Bad defaults in Undertow subsystem

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-6308?page=com.atlassian.jira.plugin.... ] Stuart Douglas updated WFLY-6308: --------------------------------- Description: There is no connection timeout and pipeline buffering is enabled. The lack of timeout is especially problematic as it can result in FD exhaustion if browsers hold onto connections for long periods > Bad defaults in Undertow subsystem > ---------------------------------- > > Key: WFLY-6308 > URL: https://issues.jboss.org/browse/WFLY-6308 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > There is no connection timeout and pipeline buffering is enabled. The lack of timeout is especially problematic as it can result in FD exhaustion if browsers hold onto connections for long periods -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6308) Bad defaults in Undertow subsystem

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-6308: ------------------------------------ Summary: Bad defaults in Undertow subsystem Key: WFLY-6308 URL: https://issues.jboss.org/browse/WFLY-6308 Project: WildFly Issue Type: Bug Components: Web (Undertow) Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 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 March 2016