January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1905) FORK: RPCs might block if fork channel or fork stack is not available

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/JGRP-1905?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on JGRP-1905: ------------------------------------ Your strategy of connecting all fork channels first doesn't gel with the way WildFly provisions its channels. Infinispan is no longer the only consumer of JGroups channels, as was the case in AS7 - and thus no longer designed to control the lifecycle of the main channel. Effectively, there is no definitive set of forks for a given deployment - these are created and connected as needed by the requisite clustering services required to fulfill the components used by that deployment. > FORK: RPCs might block if fork channel or fork stack is not available > --------------------------------------------------------------------- > > Key: JGRP-1905 > URL: https://issues.jboss.org/browse/JGRP-1905 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Critical > Fix For: 3.6.2 > > > When we have nodes A,B,C,D, but fork-stack "fs-2" is not available on B, or fork-channel "ch-3" is not available on B, then an RPC invoked by A on all cluster nodes will time out. > h5. Solution > * Throw an exception on B if a fork-stack or -channel is not available on a target node. This way, the RPC would return quickly and B's response would be set to the exception (e.g. "fork channel fc-2 not available"). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-497) OperationStepHandlers for audit log handler add ops prematurely validate

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-497: --------------------------------------- Summary: OperationStepHandlers for audit log handler add ops prematurely validate Key: WFCORE-497 URL: https://issues.jboss.org/browse/WFCORE-497 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 1.0.0.Alpha15 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 1.0.0.Alpha16 SyslogAuditLogHandlerAddHandler and FileAuditLogHandlerAddHandler are doing reference validation directly in populateModel. This should instead be done in a separate step, removing the requirement to have the add op for the formatter occur before the add op for the handler, so long as both ops occur within the set of ops handled by the same OperationContext. This will simplify booting from a filesystem tree instead of xml, removing the need to persist ordering information about formatter/handler in the FS. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JGRP-1905) FORK: RPCs might block if fork channel or fork stack is not available

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1905?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1905: -------------------------------- Sure, a ResponseFilter would also work, but what about my proposal above ? > FORK: RPCs might block if fork channel or fork stack is not available > --------------------------------------------------------------------- > > Key: JGRP-1905 > URL: https://issues.jboss.org/browse/JGRP-1905 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Critical > Fix For: 3.6.2 > > > When we have nodes A,B,C,D, but fork-stack "fs-2" is not available on B, or fork-channel "ch-3" is not available on B, then an RPC invoked by A on all cluster nodes will time out. > h5. Solution > * Throw an exception on B if a fork-stack or -channel is not available on a target node. This way, the RPC would return quickly and B's response would be set to the exception (e.g. "fork channel fc-2 not available"). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4241) Update JSF based on jsf-impl-2.2.9-jbossorg-2

by Farah Juma (JIRA)

Farah Juma created WFLY-4241: -------------------------------- Summary: Update JSF based on jsf-impl-2.2.9-jbossorg-2 Key: WFLY-4241 URL: https://issues.jboss.org/browse/WFLY-4241 Project: WildFly Issue Type: Component Upgrade Components: JSF Reporter: Farah Juma Assignee: Farah Juma Update to jsf-impl-2.2.9-jbossorg-2 to include the fix for [JAVASERVERFACES-3674 | https://java.net/jira/browse/JAVASERVERFACES-3674]. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4164) New JTS record types are not showing up in the CLI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4164?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4164: ----------------------------------------------- Hayk Hovsepyan <hhovsepy(a)redhat.com> changed the Status of [bug 1168973|https://bugzilla.redhat.com/show_bug.cgi?id=1168973] from ON_QA to VERIFIED > New JTS record types are not showing up in the CLI > -------------------------------------------------- > > Key: WFLY-4164 > URL: https://issues.jboss.org/browse/WFLY-4164 > Project: WildFly > Issue Type: Enhancement > Components: CLI, Transactions > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > We need to expose the new JTS record types in the tooling: > {code} > AssumedCompleteHeuristicTransaction > AssumedCompleteHeuristicServerTransaction > AssumedCompleteTransaction > AssumedCompleteServerTransaction > {code} > We need these because if a transaction ends up in a heuristic state we can't actually view this using the CLI even though the records are in the object store. This has the consequence that a transaction can remain in the object store indefinitely. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-678) Constraints index Null values as 0s

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-678?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-678. -------------------------------- Fix Version/s: 6.2.0.Final Resolution: Done Fixed by https://github.com/droolsjbpm/drools/commit/1d7be3fc5dd86a6051ae09fd494b1... > Constraints index Null values as 0s > ----------------------------------- > > Key: DROOLS-678 > URL: https://issues.jboss.org/browse/DROOLS-678 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.2.0.Final > > > In the following test case: > {code} > @Test > public void testAlphaIndexing() throws Exception { > String drl = > " package org.drools.test; " + > > " declare ObjectB " + > " name : String " + > " intValue : Integer " + > " end " + > > " rule 'insert object' " + > " when " + > " then " + > " insert( new ObjectB( null, 0 ) ); " + > " end " + > > " rule 'rule 1' " + > " when " + > " ObjectB( intValue == 1 ) " + > " then " + > " end " + > > " rule 'rule 2' " + > " when " + > " ObjectB( intValue == 2 ) " + > " then " + > " end " + > > " rule 'rule 3' " + > " when " + > " $b : ObjectB( intValue == null ) " + > " then\n" + > " System.out.println( $b ); " + > " end" + > "\n" ; > > KieHelper helper = new KieHelper(); > helper.addContent( drl, ResourceType.DRL ); > assertTrue( helper.verify().getMessages( org.kie.api.builder.Message.Level.ERROR ).isEmpty() ); > helper.build( ).newKieSession().fireAllRules(); > } > {code} > rule 3 fires even if it shouldn't -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4171) Provide an html5 archetype for wildfly

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/WFLY-4171?page=com.atlassian.jira.plugin.... ] Rafael Benevides resolved WFLY-4171. ------------------------------------ Resolution: Done Archetypes staged at: https://repository.jboss.org/nexus/content/repositories/jboss_releases_st... > Provide an html5 archetype for wildfly > -------------------------------------- > > Key: WFLY-4171 > URL: https://issues.jboss.org/browse/WFLY-4171 > Project: WildFly > Issue Type: Feature Request > Reporter: Fred Bricon > Assignee: Rafael Benevides > > We'd like to provide a Wildfly-ified version of the html5 archetype in JBoss Central, for JBoss Tools and Developer Studio, The current versions we serve right now are : > * org.jboss.aerogear.archetypes:jboss-html5-mobile-archetype:7.1.3.Final > * org.jboss.archetype.wfk:jboss-html5-mobile-archetype:2.6.0.Final -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4190) Provide a Willdfly banner instead of JBossAS7 for Kitchensink quickstarts

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/WFLY-4190?page=com.atlassian.jira.plugin.... ] Rafael Benevides commented on WFLY-4190: ---------------------------------------- New commit: https://github.com/wildfly/quickstart/commit/26e7ca0c55192c7b3a30447752b7... - Thanks [~james.cobb]. It's much better now! > Provide a Willdfly banner instead of JBossAS7 for Kitchensink quickstarts > -------------------------------------------------------------------------- > > Key: WFLY-4190 > URL: https://issues.jboss.org/browse/WFLY-4190 > Project: WildFly > Issue Type: Enhancement > Reporter: Rafael Benevides > Assignee: Rafael Benevides > Labels: quickstart, quickstarts > Attachments: wildfly_400x130.jpg > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4190) Provide a Willdfly banner instead of JBossAS7 for Kitchensink quickstarts

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/WFLY-4190?page=com.atlassian.jira.plugin.... ] Rafael Benevides resolved WFLY-4190. ------------------------------------ Resolution: Done > Provide a Willdfly banner instead of JBossAS7 for Kitchensink quickstarts > -------------------------------------------------------------------------- > > Key: WFLY-4190 > URL: https://issues.jboss.org/browse/WFLY-4190 > Project: WildFly > Issue Type: Enhancement > Reporter: Rafael Benevides > Assignee: Rafael Benevides > Labels: quickstart, quickstarts > Attachments: wildfly_400x130.jpg > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-496) add-user.sh - if password contains § it is not possible to log into the webinterface

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-496?page=com.atlassian.jira.plugin... ] Darran Lofthouse moved WFLY-4240 to WFCORE-496: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-496 (was: WFLY-4240) Affects Version/s: (was: 8.2.0.Final) Component/s: Domain Management Security (was: Domain Management) (was: Security) Fix Version/s: 1.0.0.Alpha16 (was: 9.0.0.Beta1) > add-user.sh - if password contains § it is not possible to log into the webinterface > ------------------------------------------------------------------------------------ > > Key: WFCORE-496 > URL: https://issues.jboss.org/browse/WFCORE-496 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Environment: wheezy, Firefox 34.0.5, Chrome 36.0.1985.125 > Reporter: do ev > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha16 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2015