October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1764) Add method to create a thrusted and unthrusted XStream instance on XStreamUtils

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1764?page=com.atlassian.jira.plugi... ] Geoffrey De Smet commented on DROOLS-1764: ------------------------------------------ Submitted a PR on droolsjbpm-knowledge https://github.com/kiegroup/droolsjbpm-knowledge/pull/270 > Add method to create a thrusted and unthrusted XStream instance on XStreamUtils > ------------------------------------------------------------------------------- > > Key: DROOLS-1764 > URL: https://issues.jboss.org/browse/DROOLS-1764 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Geoffrey De Smet > Assignee: Geoffrey De Smet > Priority: Critical > > Each piece of code will need to figure out wether to use the thrusting or unthrusting xstream. > - thrusted: the xml is just like java code. It's basically executable. > - unthrusted: only whitelisted, select packages are allowed. There is no blacklist approach. Root packages are not being whitelisted. > Furthermore, *we want unthursted to allow all XStreamAliassed annotations automatically*, so it works like JAXB and Jackson. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9446) mvn idea:idea in parent pom giving error

by sujay hegde (JIRA)

sujay hegde created WFLY-9446: --------------------------------- Summary: mvn idea:idea in parent pom giving error Key: WFLY-9446 URL: https://issues.jboss.org/browse/WFLY-9446 Project: WildFly Issue Type: Feature Request Reporter: sujay hegde Assignee: Jason Greene [INFO] WildFly Test Suite: Integration - Smoke ............ SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 04:48 min [INFO] Finished at: 2017-10-16T18:37:36+05:30 [INFO] Final Memory: 148M/388M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-idea-plugin:2.2.1: idea (default-cli) on project wildfly-clustering: Execution default-cli of goal org.apache.maven.plugins:maven-idea-plugin:2.2.1:idea failed.: NullPointerExcept ion -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit ch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please rea d the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutio nException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :wildfly-clustering -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8769) Integrate GOOGLE_PING2 discovery protocol

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8769?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-8769: -------------------------------------- [~mjurc] It is not and will be not. What are you talking about? > Integrate GOOGLE_PING2 discovery protocol > ----------------------------------------- > > Key: WFLY-8769 > URL: https://issues.jboss.org/browse/WFLY-8769 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > The original GOOGLE_PING is being deprecated given how low quality the code is. > Going forward, we need to integrate https://github.com/jgroups-extras/jgroups-google to keep supporting Google Cloud Platform-specific discovery mechanism. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8770) Integrate NATIVE_S3_PING discovery protocol

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8770?page=com.atlassian.jira.plugin.... ] Radoslav Husar edited comment on WFLY-8770 at 10/16/17 8:55 AM: ---------------------------------------------------------------- [~mjurc] It is not and will be not. Where is this coming from? was (Author: rhusar): [~mjurc] It is not and will be now. Where is this coming from? > Integrate NATIVE_S3_PING discovery protocol > ------------------------------------------- > > Key: WFLY-8770 > URL: https://issues.jboss.org/browse/WFLY-8770 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > The original S3_PING is being deprecated given how low quality the code is. > Going forward, we need to integrate NATIVE_S3_PING from https://github.com/jgroups-extras/native-s3-ping to keep supporting EC2-specific discovery mechanism. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8770) Integrate NATIVE_S3_PING discovery protocol

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8770?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-8770: -------------------------------------- [~mjurc] It is not and will be now. Where is this coming from? > Integrate NATIVE_S3_PING discovery protocol > ------------------------------------------- > > Key: WFLY-8770 > URL: https://issues.jboss.org/browse/WFLY-8770 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > The original S3_PING is being deprecated given how low quality the code is. > Going forward, we need to integrate NATIVE_S3_PING from https://github.com/jgroups-extras/native-s3-ping to keep supporting EC2-specific discovery mechanism. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9445) Distributed shared web sessions can expire prematurely

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-9445: ---------------------------------- Summary: Distributed shared web sessions can expire prematurely Key: WFLY-9445 URL: https://issues.jboss.org/browse/WFLY-9445 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.1.0.Final, 11.0.0.CR1 Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Critical When an EAR is configured to share web sessions across WARs, each WAR deployment will use the same distributed session manager factory instance. However, each deployment will use a separate session manager instance (created from the shared factory). Since session expiration and passivation is managed per session manager, it is possible that a session is scheduled to expire on one manager, regardless of whether it is subsequently referenced by another manager, and can thus expire prematurely. To fix this, each session manager instance must also share session expiration/eviction schedulers, where each manager registers deployment specific listeners on SessionManager.start() and unregisters on stop(). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8770) Integrate NATIVE_S3_PING discovery protocol

by Michal Jurc (JIRA)

[ https://issues.jboss.org/browse/WFLY-8770?page=com.atlassian.jira.plugin.... ] Michal Jurc commented on WFLY-8770: ----------------------------------- This should not be included in WildFly 11/JBoss EAP7 with concerns regarding backwards compatibility. CC [~jason.greene]. > Integrate NATIVE_S3_PING discovery protocol > ------------------------------------------- > > Key: WFLY-8770 > URL: https://issues.jboss.org/browse/WFLY-8770 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > The original S3_PING is being deprecated given how low quality the code is. > Going forward, we need to integrate NATIVE_S3_PING from https://github.com/jgroups-extras/native-s3-ping to keep supporting EC2-specific discovery mechanism. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8769) Integrate GOOGLE_PING2 discovery protocol

by Michal Jurc (JIRA)

[ https://issues.jboss.org/browse/WFLY-8769?page=com.atlassian.jira.plugin.... ] Michal Jurc commented on WFLY-8769: ----------------------------------- This should not be included in WildFly 11/JBoss EAP7 with concerns regarding backwards compatibility. CC [~jason.greene]. > Integrate GOOGLE_PING2 discovery protocol > ----------------------------------------- > > Key: WFLY-8769 > URL: https://issues.jboss.org/browse/WFLY-8769 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > The original GOOGLE_PING is being deprecated given how low quality the code is. > Going forward, we need to integrate https://github.com/jgroups-extras/jgroups-google to keep supporting Google Cloud Platform-specific discovery mechanism. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8770) Integrate NATIVE_S3_PING discovery protocol

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8770?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-8770: -------------------------------------- Only deprecated. S3_PING will be removed in 5.0. > Integrate NATIVE_S3_PING discovery protocol > ------------------------------------------- > > Key: WFLY-8770 > URL: https://issues.jboss.org/browse/WFLY-8770 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > The original S3_PING is being deprecated given how low quality the code is. > Going forward, we need to integrate NATIVE_S3_PING from https://github.com/jgroups-extras/native-s3-ping to keep supporting EC2-specific discovery mechanism. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8770) Integrate NATIVE_S3_PING discovery protocol

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-8770?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda commented on WFLY-8770: ----------------------------------------- Is S3_PING deprecated in JGroups 4 or removed ? > Integrate NATIVE_S3_PING discovery protocol > ------------------------------------------- > > Key: WFLY-8770 > URL: https://issues.jboss.org/browse/WFLY-8770 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > The original S3_PING is being deprecated given how low quality the code is. > Going forward, we need to integrate NATIVE_S3_PING from https://github.com/jgroups-extras/native-s3-ping to keep supporting EC2-specific discovery mechanism. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2017