December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2064) JDBC_PING: make subclass of FILE_PING

by Ashish Agarwal (JIRA)

[ https://issues.jboss.org/browse/JGRP-2064?page=com.atlassian.jira.plugin.... ] Ashish Agarwal commented on JGRP-2064: -------------------------------------- I tried using remove_old_coords_on_view_change and remove_all_files_on_view_change in my xml file but its not working Please suggest. My xml looks like this : <JDBC_PING connection_url="DB url" connection_username="user_name" connection_password="password" connection_driver="oracle.jdbc.OracleDriver" remove_old_coords_on_view_change="true" initialize_sql="CREATE TABLE IF NOT EXISTS jgroup_ping ( own_addr varchar(200) NOT NULL, cluster_name varchar(200) NOT NULL, ping_data varbinary(5000) DEFAULT NULL, PRIMARY KEY (own_addr, cluster_name) )ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin" insert_single_sql="INSERT INTO jgroup_ping (own_addr, cluster_name, ping_data) values (?, ?, ?)" delete_single_sql="DELETE FROM jgroup_ping WHERE own_addr=? AND cluster_name=?" select_all_pingdata_sql="SELECT ping_data FROM jgroup_ping WHERE cluster_name=?" /> > JDBC_PING: make subclass of FILE_PING > ------------------------------------- > > Key: JGRP-2064 > URL: https://issues.jboss.org/browse/JGRP-2064 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0 > > > This way, zombie removal would be possible, e.g. attributes {{remove_old_coords_on_view_change}} and {{remove_all_files_on_view_change}} would be usable. > Currently, JDBC_PING extends Discovery only, not FILE_PING -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9617) Add persistend store to infinispan via CLI fail

by Domenico Briganti (JIRA)

[ https://issues.jboss.org/browse/WFLY-9617?page=com.atlassian.jira.plugin.... ] Domenico Briganti commented on WFLY-9617: ----------------------------------------- Ok. So it is not possible to configure a persistent store in an existent cache, correct? (only hacking the standalone.xml file :) ) > Add persistend store to infinispan via CLI fail > ----------------------------------------------- > > Key: WFLY-9617 > URL: https://issues.jboss.org/browse/WFLY-9617 > Project: WildFly > Issue Type: Bug > Components: Clustering, Domain Management > Affects Versions: 11.0.0.Final > Reporter: Domenico Briganti > Assignee: Paul Ferraro > > Configure a persistent file for a local-cache via CLI fail if not into a batch block. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9617) Add persistend store to infinispan via CLI fail

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9617?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-9617: -------------------------------------- The whole add operation for the cache needs to be run in a batch: {noformat} batch /subsystem=infinispan/cache-container=reservation:add /subsystem=infinispan/cache-container=reservation/local-cache=authtoken:add(statistics-enabled=true) /subsystem=infinispan/cache-container=reservation/local-cache=authtoken/store=file:add(path=authtoken.dat,relative-to=jboss.home.dir,passivation=false,preload=true,purge=true) run-batch {noformat} > Add persistend store to infinispan via CLI fail > ----------------------------------------------- > > Key: WFLY-9617 > URL: https://issues.jboss.org/browse/WFLY-9617 > Project: WildFly > Issue Type: Bug > Components: Clustering, Domain Management > Affects Versions: 11.0.0.Final > Reporter: Domenico Briganti > Assignee: Paul Ferraro > > Configure a persistent file for a local-cache via CLI fail if not into a batch block. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9617) Add persistend store to infinispan via CLI fail

by Domenico Briganti (JIRA)

[ https://issues.jboss.org/browse/WFLY-9617?page=com.atlassian.jira.plugin.... ] Domenico Briganti commented on WFLY-9617: ----------------------------------------- OK, but I have the same error if I want to add a file store in a second moment. If I previously create the cache and now I run: batch /subsystem=infinispan/cache-container=reservation/local-cache=authtoken/store=file:add(path=authtoken.dat,relative-to=jboss.home.dir,passivation=false,preload=true,purge=true) run-batch I get the same error. > Add persistend store to infinispan via CLI fail > ----------------------------------------------- > > Key: WFLY-9617 > URL: https://issues.jboss.org/browse/WFLY-9617 > Project: WildFly > Issue Type: Bug > Components: Clustering, Domain Management > Affects Versions: 11.0.0.Final > Reporter: Domenico Briganti > Assignee: Paul Ferraro > > Configure a persistent file for a local-cache via CLI fail if not into a batch block. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2183) Can't configure KieSession used in RuleUnitExecutor

by Duncan Doyle (JIRA)

Duncan Doyle created DROOLS-2183: ------------------------------------ Summary: Can't configure KieSession used in RuleUnitExecutor Key: DROOLS-2183 URL: https://issues.jboss.org/browse/DROOLS-2183 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.5.0.Final Environment: macOS 10.12.6, Oracle Hotspot 1.8.0_151 Reporter: Duncan Doyle Assignee: Mario Fusco To support CEP using RuleUnits, we need to be able to configure a session that uses the PseudoClock (a best practice when using deterministic CEP rule execution). However, in the current implementation, the KieSession configuration in kmodule.xml is discarded. Second, there is not a nice way in the current API to pass session configuration programmatically. A reproducer of the problem can be found here (sorry for not cleaning it up nicely. It basically tries to set the SessionClock as fact into WorkingMemory, and at that time trying to cast to SessionPseudoClock.): https://github.com/DuncanDoyle/rule-unit-and-session-conf Just run "mvn clean test" on that project. As discussed on IRC, we agreed that the proper way of doing this would be to make the RuleUnitExecutor a container resource and allow it to use session configuration defined in kmodule.xml (also from a KIE-Server perspective). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-187) The ClassLoaderLogContextSelector check for the log context should return null

by James Perkins (JIRA)

James Perkins created LOGMGR-187: ------------------------------------ Summary: The ClassLoaderLogContextSelector check for the log context should return null Key: LOGMGR-187 URL: https://issues.jboss.org/browse/LOGMGR-187 Project: JBoss Log Manager Issue Type: Bug Reporter: James Perkins The {{ClassLoaderLogContextSelector}} check for the registered {{LogContext}} returns {{defaultSelector.getLogContext()}} in the {{check()}} method and should return {{null}}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2182) NPE when @Expires is missing on event type

by Christian Bauer (JIRA)

Christian Bauer created DROOLS-2182: --------------------------------------- Summary: NPE when @Expires is missing on event type Key: DROOLS-2182 URL: https://issues.jboss.org/browse/DROOLS-2182 Project: Drools Issue Type: Bug Affects Versions: 7.5.0.Final Reporter: Christian Bauer Assignee: Edson Tirelli This code in {{ClassObjectTypeConf}} assumes that an event class always has an @Expires annotation, which is optional: {code} Role role = clazz.getAnnotation(Role.class); if (role != null) { isEvent = role.value() == Type.EVENT; if (isEvent) { Expires expires = clazz.getAnnotation(Expires.class); expirationOffset = TimeIntervalParser.parseSingle( expires.value() ); } } {code} {code} java.lang.NullPointerException at org.drools.core.reteoo.ClassObjectTypeConf.<init>(ClassObjectTypeConf.java:99) at org.drools.core.common.ObjectTypeConfigurationRegistry.getObjectTypeConf(ObjectTypeConfigurationRegistry.java:69) at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:181) at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1493) at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1453) at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1447) {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3462) Expose the ability for filters on loggers to be inherited

by James Perkins (JIRA)

James Perkins created WFCORE-3462: ------------------------------------- Summary: Expose the ability for filters on loggers to be inherited Key: WFCORE-3462 URL: https://issues.jboss.org/browse/WFCORE-3462 Project: WildFly Core Issue Type: Enhancement Components: Logging Reporter: James Perkins Assignee: James Perkins In LOGMGR-45 the ability to allow loggers to inherit filters was added. This should also be supported in the management model for WildFly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2154) Design navigation between the DRG and DRD's

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2154?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2154: ------------------------------------- [~manstis] [~tirelli] [~mstevens1] I posted a mockup that illustrates the key navigation points, to address this story. I plan to create a separate jira for inline interactions and such. !Screen Shot 2017-12-15 at 10.16.33 AM.png|thumbnail! > Design navigation between the DRG and DRD's > ------------------------------------------- > > Key: DROOLS-2154 > URL: https://issues.jboss.org/browse/DROOLS-2154 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam > Attachments: Screen Shot 2017-12-15 at 10.16.33 AM.png > > > *Use case description: * > As a business user (Citizen Developer…), I want to navigate between the DRG and the DRDs, and the content of each node, to model business decision logic. > *Requirements:* > * Diagram modeling must be absolutely consistent with Process Modeler: Process Designer and DMN editors should provide the same features, support the same interactions and appear visually similar in all aspects to one and other at "Level 1". Divergence may exist at "Level 2". > *Verification Conditions* > * The user of this feature is able to understand that the the DRDs are subsets of the whole DRG model/file. > * The user of this feature can seamlessly navigate between the diagrams and the content of the nodes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2154) Design navigation between the DRG and DRD's

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2154?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2154: -------------------------------- Attachment: Screen Shot 2017-12-15 at 10.16.33 AM.png > Design navigation between the DRG and DRD's > ------------------------------------------- > > Key: DROOLS-2154 > URL: https://issues.jboss.org/browse/DROOLS-2154 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam > Attachments: Screen Shot 2017-12-15 at 10.16.33 AM.png > > > *Use case description: * > As a business user (Citizen Developer…), I want to navigate between the DRG and the DRDs, and the content of each node, to model business decision logic. > *Requirements:* > * Diagram modeling must be absolutely consistent with Process Modeler: Process Designer and DMN editors should provide the same features, support the same interactions and appear visually similar in all aspects to one and other at "Level 1". Divergence may exist at "Level 2". > *Verification Conditions* > * The user of this feature is able to understand that the the DRDs are subsets of the whole DRG model/file. > * The user of this feature can seamlessly navigate between the diagrams and the content of the nodes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 December 2017