November 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1897) ENCRYPT might drop messages during key change

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1897?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1897: -------------------------------- I'm afraid you did ... :-) I don't mean to be a PITA, but your formatting essentially changed all lines in {{ENCRYPT}} ! Please keep the existing formatting and submit only the changes. > ENCRYPT might drop messages during key change > --------------------------------------------- > > Key: JGRP-1897 > URL: https://issues.jboss.org/browse/JGRP-1897 > Project: JGroups > Issue Type: Bug > Reporter: Tero Leppikangas > Assignee: Bela Ban > Fix For: 3.6.1 > > > ENCRYPT might drop some (unicast) messages encrypted with unknown key if the delivery of new view is delayed. > This problem was noticed while doing some stress testing on the fix for JGRP-1893. > When view changes, coordinator multicasts the new view after which is starts using new symmetric keys. If some node receives a message sent with the new key before the new view is received, the received message will be dropped since it cannot be decrypted. > We thought of possible solutions to be. > 1. Sender specific queue holding the messages received. > 2. Starting to queue up messages until new view has been received > I have implemented the second option which is quite straightforward, but it could lead into problems when receiving message with unknown key that is not related to coming view change. > I wonder if there is another way to overcome this problem? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-210) IO error during deployment scanning triggers undeployment

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-210?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-210: ------------------------------------------------ Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1159709|https://bugzilla.redhat.com/show_bug.cgi?id=1159709] from NEW to ASSIGNED > IO error during deployment scanning triggers undeployment > --------------------------------------------------------- > > Key: WFCORE-210 > URL: https://issues.jboss.org/browse/WFCORE-210 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha10 > Reporter: James Livingston > Assignee: Emmanuel Hugonnet > Fix For: 1.0.0.Beta1 > > > If an IO error such as reaching the file descriptor limit occurs during deployment scanning, the scanner continues with an empty deployment list causing it to undeploy applications. > This occurs because FileSystemDeploymentService.scanDirectory() treats File.listFiles() returning null as an empty list rather than an error. http://docs.oracle.com/javase/7/docs/api/java/io/File.html#listFiles%28%29 notes that it returns an empty array if the directory is empty, and null if it is not a directory or an IO error occurs. > It should instead respond to a null return value by aborting the scanner run, with a log message, and not proceed to undeploy applications. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-210) IO error during deployment scanning triggers undeployment

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-210?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-210: ------------------------------------ Fix Version/s: 1.0.0.Beta1 Assignee: Emmanuel Hugonnet (was: Jason Greene) Component/s: Domain Management (was: Server) > IO error during deployment scanning triggers undeployment > --------------------------------------------------------- > > Key: WFCORE-210 > URL: https://issues.jboss.org/browse/WFCORE-210 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha10 > Reporter: James Livingston > Assignee: Emmanuel Hugonnet > Fix For: 1.0.0.Beta1 > > > If an IO error such as reaching the file descriptor limit occurs during deployment scanning, the scanner continues with an empty deployment list causing it to undeploy applications. > This occurs because FileSystemDeploymentService.scanDirectory() treats File.listFiles() returning null as an empty list rather than an error. http://docs.oracle.com/javase/7/docs/api/java/io/File.html#listFiles%28%29 notes that it returns an empty array if the directory is empty, and null if it is not a directory or an IO error occurs. > It should instead respond to a null return value by aborting the scanner run, with a log message, and not proceed to undeploy applications. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3978) PicketLink Subsystem EAP 6.4 Issues

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3978?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3978: ----------------------------------------------- FIlip Bogyai <fbogyai(a)redhat.com> changed the Status of [bug 1151230|https://bugzilla.redhat.com/show_bug.cgi?id=1151230] from ON_QA to VERIFIED > PicketLink Subsystem EAP 6.4 Issues > ----------------------------------- > > Key: WFLY-3978 > URL: https://issues.jboss.org/browse/WFLY-3978 > Project: WildFly > Issue Type: Task > Components: Security > Affects Versions: 9.0.0.Alpha1 > Reporter: Pedro Igor > Assignee: Pedro Igor > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1897) ENCRYPT might drop messages during key change

by Tero Leppikangas (JIRA)

[ https://issues.jboss.org/browse/JGRP-1897?page=com.atlassian.jira.plugin.... ] Tero Leppikangas commented on JGRP-1897: ---------------------------------------- Hi. Created PRs for 3.4, 3.5 and master. Hopefully I did not mess up this time :) > ENCRYPT might drop messages during key change > --------------------------------------------- > > Key: JGRP-1897 > URL: https://issues.jboss.org/browse/JGRP-1897 > Project: JGroups > Issue Type: Bug > Reporter: Tero Leppikangas > Assignee: Bela Ban > Fix For: 3.6.1 > > > ENCRYPT might drop some (unicast) messages encrypted with unknown key if the delivery of new view is delayed. > This problem was noticed while doing some stress testing on the fix for JGRP-1893. > When view changes, coordinator multicasts the new view after which is starts using new symmetric keys. If some node receives a message sent with the new key before the new view is received, the received message will be dropped since it cannot be decrypted. > We thought of possible solutions to be. > 1. Sender specific queue holding the messages received. > 2. Starting to queue up messages until new view has been received > I have implemented the second option which is quite straightforward, but it could lead into problems when receiving message with unknown key that is not related to coming view change. > I wonder if there is another way to overcome this problem? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3978) PicketLink Subsystem EAP 6.4 Issues

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3978?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3978: ----------------------------------------------- FIlip Bogyai <fbogyai(a)redhat.com> changed the Status of [bug 1150639|https://bugzilla.redhat.com/show_bug.cgi?id=1150639] from ON_QA to VERIFIED > PicketLink Subsystem EAP 6.4 Issues > ----------------------------------- > > Key: WFLY-3978 > URL: https://issues.jboss.org/browse/WFLY-3978 > Project: WildFly > Issue Type: Task > Components: Security > Affects Versions: 9.0.0.Alpha1 > Reporter: Pedro Igor > Assignee: Pedro Igor > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4046) Container lifecycle event method invoked outside of extension observer method invocation

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-4046?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened WFLY-4046: ---------------------------------- Can we please keep this open util it is resolved? Willem Jiang who maintains camel-cdi works for RedHat too. Let me talk to him to find out whether he knows what to do about this. Do you have a suggestion? > Container lifecycle event method invoked outside of extension observer method invocation > ---------------------------------------------------------------------------------------- > > Key: WFLY-4046 > URL: https://issues.jboss.org/browse/WFLY-4046 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 9.0.0.Alpha1 > Reporter: Thomas Diesler > Assignee: Jozef Hartinger > > Cannot deploy war that uses camel-cdi > This works in 8.1.0.Final > {code} > org.jboss.weld.exceptions.IllegalStateException: WELD-000143: Container lifecycle event method invoked outside of extension observer method invocation. > at org.jboss.weld.bootstrap.events.ContainerEvent.checkWithinObserverNotification(ContainerEvent.java:61) > at org.jboss.weld.bootstrap.events.ProcessAnnotatedTypeImpl.getAnnotatedType(ProcessAnnotatedTypeImpl.java:56) > at org.apache.camel.cdi.internal.CamelContextConfig.configure(CamelContextConfig.java:47) > at org.apache.camel.cdi.internal.CamelContextBean.configureCamelContext(CamelContextBean.java:131) > at org.apache.camel.cdi.internal.CamelExtension.startConsumeBeans(CamelExtension.java:231) > {code} > Cross Issue: https://issues.apache.org/jira/browse/CAMEL-7992 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4046) Container lifecycle event method invoked outside of extension observer method invocation

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-4046?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated WFLY-4046: --------------------------------- Description: Cannot deploy war that uses camel-cdi This works in 8.1.0.Final {code} org.jboss.weld.exceptions.IllegalStateException: WELD-000143: Container lifecycle event method invoked outside of extension observer method invocation. at org.jboss.weld.bootstrap.events.ContainerEvent.checkWithinObserverNotification(ContainerEvent.java:61) at org.jboss.weld.bootstrap.events.ProcessAnnotatedTypeImpl.getAnnotatedType(ProcessAnnotatedTypeImpl.java:56) at org.apache.camel.cdi.internal.CamelContextConfig.configure(CamelContextConfig.java:47) at org.apache.camel.cdi.internal.CamelContextBean.configureCamelContext(CamelContextBean.java:131) at org.apache.camel.cdi.internal.CamelExtension.startConsumeBeans(CamelExtension.java:231) {code} Cross Issue: https://issues.apache.org/jira/browse/CAMEL-7992 was: Cannot deploy war that uses camel-cdi This works in 8.1.0.Final {code} org.jboss.weld.exceptions.IllegalStateException: WELD-000143: Container lifecycle event method invoked outside of extension observer method invocation. at org.jboss.weld.bootstrap.events.ContainerEvent.checkWithinObserverNotification(ContainerEvent.java:61) at org.jboss.weld.bootstrap.events.ProcessAnnotatedTypeImpl.getAnnotatedType(ProcessAnnotatedTypeImpl.java:56) at org.apache.camel.cdi.internal.CamelContextConfig.configure(CamelContextConfig.java:47) at org.apache.camel.cdi.internal.CamelContextBean.configureCamelContext(CamelContextBean.java:131) at org.apache.camel.cdi.internal.CamelExtension.startConsumeBeans(CamelExtension.java:231) {code} > Container lifecycle event method invoked outside of extension observer method invocation > ---------------------------------------------------------------------------------------- > > Key: WFLY-4046 > URL: https://issues.jboss.org/browse/WFLY-4046 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 9.0.0.Alpha1 > Reporter: Thomas Diesler > Assignee: Jozef Hartinger > > Cannot deploy war that uses camel-cdi > This works in 8.1.0.Final > {code} > org.jboss.weld.exceptions.IllegalStateException: WELD-000143: Container lifecycle event method invoked outside of extension observer method invocation. > at org.jboss.weld.bootstrap.events.ContainerEvent.checkWithinObserverNotification(ContainerEvent.java:61) > at org.jboss.weld.bootstrap.events.ProcessAnnotatedTypeImpl.getAnnotatedType(ProcessAnnotatedTypeImpl.java:56) > at org.apache.camel.cdi.internal.CamelContextConfig.configure(CamelContextConfig.java:47) > at org.apache.camel.cdi.internal.CamelContextBean.configureCamelContext(CamelContextBean.java:131) > at org.apache.camel.cdi.internal.CamelExtension.startConsumeBeans(CamelExtension.java:231) > {code} > Cross Issue: https://issues.apache.org/jira/browse/CAMEL-7992 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4044) Wildfly service will not start on fedora 20 - 64 bit

by Marek Goldmann (JIRA)

[ https://issues.jboss.org/browse/WFLY-4044?page=com.atlassian.jira.plugin.... ] Marek Goldmann commented on WFLY-4044: -------------------------------------- I'll look into this. > Wildfly service will not start on fedora 20 - 64 bit > ---------------------------------------------------- > > Key: WFLY-4044 > URL: https://issues.jboss.org/browse/WFLY-4044 > Project: WildFly > Issue Type: Feature Request > Components: Server > Affects Versions: 8.1.0.Final > Environment: Fedora 20 - updates installed > Reporter: Karl Nicholas > Assignee: Marek Goldmann > > standalone.sh starts wildfly ok but systemctl start service fails: > [root@localhost system]# yum install wildfly > Loaded plugins: langpacks, refresh-packagekit > Package wildfly-8.1.0-3.fc20.noarch already installed and latest version > Nothing to do > [root@localhost system]# systemctl start wildfly > [root@localhost system]# systemctl status wildfly > wildfly.service - The WildFly Application Server > Loaded: loaded (/usr/lib/systemd/system/wildfly.service; disabled) > Active: failed (Result: exit-code) since Sat 2014-11-01 15:50:40 PDT; 5s ago > Process: 7658 ExecStart=/usr/share/wildfly/bin/launch.sh $WILDFLY_MODE $WILDFLY_CONFIG $WILDFLY_BIND (code=exited, status=1/FAILURE) > Main PID: 7658 (code=exited, status=1/FAILURE) > Nov 01 15:50:39 localhost.localdomain systemd[1]: Started The WildFly Application Server. > Nov 01 15:50:40 localhost.localdomain systemd[1]: wildfly.service: main process exited, code=exited, status=1/FAILURE > Nov 01 15:50:40 localhost.localdomain systemd[1]: Unit wildfly.service entered failed state. > [root@localhost system] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1893) ENCRYPT: Thread safety issues during key changes

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1893?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1893: --------------------------- Fix Version/s: 3.6.1 > ENCRYPT: Thread safety issues during key changes > ------------------------------------------------ > > Key: JGRP-1893 > URL: https://issues.jboss.org/browse/JGRP-1893 > Project: JGroups > Issue Type: Bug > Reporter: Tero Leppikangas > Assignee: Bela Ban > Fix For: 3.6.1 > > > For symmetric encryption, ENCRYPT has members with shared state: secret key, version and ciphers. In order for to provide consistent state between different threads accessing these members, they should be synchronized. > I have implemented one solution by wrapping the state in separate object which can be found here: > https://github.com/tepitebson/JGroups/tree/ENCRYPT_Thread_safety > I also have replaced the WeakHashMap holding the previous keys with Cache in google's guava library so my solution probably is not suitable for an official solution. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

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 November 2014