January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-871) AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-871?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved SECURITY-871. --------------------------------------- Resolution: Done > AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault > ---------------------------------------------------------------------------- > > Key: SECURITY-871 > URL: https://issues.jboss.org/browse/SECURITY-871 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Reporter: Derek Horton > Assignee: Darran Lofthouse > Fix For: Negotiation_2_3_6_Final > > > AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4206) jboss-javaee-7.0-with-resteasy bom exposes JUnit as dependency

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4206?page=com.atlassian.jira.plugin.... ] Tomaz Cerar resolved WFLY-4206. ------------------------------- Resolution: Done fixed in boms 8.2.1.Final > jboss-javaee-7.0-with-resteasy bom exposes JUnit as dependency > -------------------------------------------------------------- > > Key: WFLY-4206 > URL: https://issues.jboss.org/browse/WFLY-4206 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 8.2.0.Final > Reporter: James Bodkin > Assignee: Tomaz Cerar > Priority: Minor > > The jboss-javaee-7.0-with-resteasy bom includes the JUnit dependency, I believe this should be included with the jboss-javaee-7.0-with-tools bom instead. (It seems to already be included in tools as well) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1876) MERGE3 : Strange number and content of subgroups

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/JGRP-1876?page=com.atlassian.jira.plugin.... ] Radim Vansa updated JGRP-1876: ------------------------------ Attachment: views.txt Logs from 4 nodes edg-perf[10-13], containing sequences of installed views. > MERGE3 : Strange number and content of subgroups > ------------------------------------------------ > > Key: JGRP-1876 > URL: https://issues.jboss.org/browse/JGRP-1876 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4.2 > Reporter: Karim AMMOUS > Assignee: Bela Ban > Fix For: 3.5.1, 3.6, 3.6.2 > > Attachments: 4Subgroups.zip, DkeJgrpAddress.java, MergeTest4.java, MergeViewWith210Subgroups.log, views.txt > > > Using JGroups 3.4.2, a split occurred and a merge was processed successfully but number of subgroups is wrong (210 instead of 2). > The final mergeView is correct and contains 210 members. > Here is an extract of subviews: > {code} > INFO | Incoming-18,cluster,term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F] | [MyMembershipListener.java:126] | (middleware) | MergeView view ID = [serv-ZM2BU35940-58033:vt-14:192.168.55.55:1:CL(GROUP01)[F]|172] > 210 subgroups > [.... > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [term-ETJ104215245-11092:host:192.168.56.72:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU38960-6907:asb:192.168.55.52:1:CL(GROUP01)[F]] > [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]|171] (1) [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU47533-55240:vt-14:192.168.55.57:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU35943-49435:asb:192.168.55.51:1:CL(GROUP01)[F]] > ....] > {code} > II wasn't able to reproduce that with a simple program. But I observed that merge was preceded by an ifdown/ifup on host 192.168.56.6. That member lost all others members, but it still present in their view. > Example: > {code} > {A, B, C} => {A, B, C} and {C} => {A, B, C} > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3989) TCCL in constructor of MDB is ModuleClassLoader for Module "org.hornetq.ra:main"

by Robert Smith (JIRA)

[ https://issues.jboss.org/browse/WFLY-3989?page=com.atlassian.jira.plugin.... ] Robert Smith commented on WFLY-3989: ------------------------------------ Can this be patched in 8.1.0? We are using 8.1.0.Final and are having problems with spring loading in mdbs. > TCCL in constructor of MDB is ModuleClassLoader for Module "org.hornetq.ra:main" > -------------------------------------------------------------------------------- > > Key: WFLY-3989 > URL: https://issues.jboss.org/browse/WFLY-3989 > Project: WildFly > Issue Type: Bug > Components: Class Loading, EE > Affects Versions: 8.1.0.Final > Environment: Windows > Reporter: Prasad Deshpande > Assignee: jaikiran pai > Fix For: 9.0.0.Beta1 > > > The spec mandates that the TCCL be the application's classloader when the component is invoked (even during construction), but I'm getting it as > TCCL in constructor of MDB is ModuleClassLoader for Module "org.hornetq.ra:main" from local module loader -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4223) Upgrade to JBoss Negotiation 2.3.6.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-4223: -------------------------------------- Summary: Upgrade to JBoss Negotiation 2.3.6.Final Key: WFLY-4223 URL: https://issues.jboss.org/browse/WFLY-4223 Project: WildFly Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 9.0.0.Beta1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-873) Release JBoss Negotiation 2.3.6.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created SECURITY-873: ----------------------------------------- Summary: Release JBoss Negotiation 2.3.6.Final Key: SECURITY-873 URL: https://issues.jboss.org/browse/SECURITY-873 Project: PicketBox Issue Type: Release Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2_3_6_Final -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-871) AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-871?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-871: -------------------------------------- Fix Version/s: Negotiation_2_3_6_Final > AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault > ---------------------------------------------------------------------------- > > Key: SECURITY-871 > URL: https://issues.jboss.org/browse/SECURITY-871 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Reporter: Derek Horton > Assignee: Darran Lofthouse > Fix For: Negotiation_2_3_6_Final > > > AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1876) MERGE3 : Strange number and content of subgroups

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1876?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-1876 at 1/6/15 9:51 AM: -------------------------------------------------------- This specific issue doesn't appear anymore, but we can still have too many subviews, as described in the next comment. Note that the MergeView itself is correct and lists the correct members. It is the subviews which are incorrect. was (Author: belaban): This specific issue doesn't appear anymore, but we can still have too many subviews, as described in the next comment > MERGE3 : Strange number and content of subgroups > ------------------------------------------------ > > Key: JGRP-1876 > URL: https://issues.jboss.org/browse/JGRP-1876 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4.2 > Reporter: Karim AMMOUS > Assignee: Bela Ban > Fix For: 3.5.1, 3.6, 3.6.2 > > Attachments: 4Subgroups.zip, DkeJgrpAddress.java, MergeTest4.java, MergeViewWith210Subgroups.log > > > Using JGroups 3.4.2, a split occurred and a merge was processed successfully but number of subgroups is wrong (210 instead of 2). > The final mergeView is correct and contains 210 members. > Here is an extract of subviews: > {code} > INFO | Incoming-18,cluster,term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F] | [MyMembershipListener.java:126] | (middleware) | MergeView view ID = [serv-ZM2BU35940-58033:vt-14:192.168.55.55:1:CL(GROUP01)[F]|172] > 210 subgroups > [.... > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [term-ETJ104215245-11092:host:192.168.56.72:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU38960-6907:asb:192.168.55.52:1:CL(GROUP01)[F]] > [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]|171] (1) [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU47533-55240:vt-14:192.168.55.57:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU35943-49435:asb:192.168.55.51:1:CL(GROUP01)[F]] > ....] > {code} > II wasn't able to reproduce that with a simple program. But I observed that merge was preceded by an ifdown/ifup on host 192.168.56.6. That member lost all others members, but it still present in their view. > Example: > {code} > {A, B, C} => {A, B, C} and {C} => {A, B, C} > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1876) MERGE3 : Strange number and content of subgroups

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1876?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1876: --------------------------- Fix Version/s: 3.6.2 Reopened in 3.6.2. Radim's going to attach a sample MergeView with 3 members, but *38 subviews*. All subviews are of type ({{A}} is the coord: {{A|10}}, {{A|9}}, {{A|8}} etc > MERGE3 : Strange number and content of subgroups > ------------------------------------------------ > > Key: JGRP-1876 > URL: https://issues.jboss.org/browse/JGRP-1876 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4.2 > Reporter: Karim AMMOUS > Assignee: Bela Ban > Fix For: 3.5.1, 3.6, 3.6.2 > > Attachments: 4Subgroups.zip, DkeJgrpAddress.java, MergeTest4.java, MergeViewWith210Subgroups.log > > > Using JGroups 3.4.2, a split occurred and a merge was processed successfully but number of subgroups is wrong (210 instead of 2). > The final mergeView is correct and contains 210 members. > Here is an extract of subviews: > {code} > INFO | Incoming-18,cluster,term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F] | [MyMembershipListener.java:126] | (middleware) | MergeView view ID = [serv-ZM2BU35940-58033:vt-14:192.168.55.55:1:CL(GROUP01)[F]|172] > 210 subgroups > [.... > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [term-ETJ104215245-11092:host:192.168.56.72:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU38960-6907:asb:192.168.55.52:1:CL(GROUP01)[F]] > [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]|171] (1) [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU47533-55240:vt-14:192.168.55.57:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU35943-49435:asb:192.168.55.51:1:CL(GROUP01)[F]] > ....] > {code} > II wasn't able to reproduce that with a simple program. But I observed that merge was preceded by an ifdown/ifup on host 192.168.56.6. That member lost all others members, but it still present in their view. > Example: > {code} > {A, B, C} => {A, B, C} and {C} => {A, B, C} > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1876) MERGE3 : Strange number and content of subgroups

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1876?page=com.atlassian.jira.plugin.... ] Bela Ban reopened JGRP-1876: ---------------------------- This specific issue doesn't appear anymore, but we can still have too many subviews, as described in the next comment > MERGE3 : Strange number and content of subgroups > ------------------------------------------------ > > Key: JGRP-1876 > URL: https://issues.jboss.org/browse/JGRP-1876 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4.2 > Reporter: Karim AMMOUS > Assignee: Bela Ban > Fix For: 3.5.1, 3.6 > > Attachments: 4Subgroups.zip, DkeJgrpAddress.java, MergeTest4.java, MergeViewWith210Subgroups.log > > > Using JGroups 3.4.2, a split occurred and a merge was processed successfully but number of subgroups is wrong (210 instead of 2). > The final mergeView is correct and contains 210 members. > Here is an extract of subviews: > {code} > INFO | Incoming-18,cluster,term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F] | [MyMembershipListener.java:126] | (middleware) | MergeView view ID = [serv-ZM2BU35940-58033:vt-14:192.168.55.55:1:CL(GROUP01)[F]|172] > 210 subgroups > [.... > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [term-ETJ104215245-11092:host:192.168.56.72:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU38960-6907:asb:192.168.55.52:1:CL(GROUP01)[F]] > [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]|171] (1) [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU47533-55240:vt-14:192.168.55.57:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU35943-49435:asb:192.168.55.51:1:CL(GROUP01)[F]] > ....] > {code} > II wasn't able to reproduce that with a simple program. But I observed that merge was preceded by an ifdown/ifup on host 192.168.56.6. That member lost all others members, but it still present in their view. > Example: > {code} > {A, B, C} => {A, B, C} and {C} => {A, B, C} > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2015