April 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3268) Stabilize intermittently failing clustering tests

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-3268: ------------------------------------ Summary: Stabilize intermittently failing clustering tests Key: WFLY-3268 URL: https://issues.jboss.org/browse/WFLY-3268 Project: WildFly Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Clustering Affects Versions: 8.0.0.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 8.1.0.Final Some of the clustering tests org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulTimeoutTestCase(SYNC-tcp).timeout org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).nestedBeanFailover org.jboss.as.test.clustering.cluster.singleton.SingletonTestCase(SYNC-tcp).testSingletonService are failing due to OOM ERROR [org.infinispan.topology.ClusterTopologyManagerImpl] (transport-thread-4) ISPN000230: Failed to start rebalance for cache default-host/stateful-failover: java.lang.OutOfMemoryError: unable to create new native thread -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3070) The download link for Wildfly at http://www.jboss.org/projects is broken

by David Hladky (JIRA)

[ https://issues.jboss.org/browse/WFLY-3070?page=com.atlassian.jira.plugin.... ] David Hladky reopened WFLY-3070: -------------------------------- I checked the project matrix and it is still wrong. I checked http://wildfly.org/project.properties and the changes were not published. Therefore I am reopening the issue. > The download link for Wildfly at http://www.jboss.org/projects is broken > ------------------------------------------------------------------------ > > Key: WFLY-3070 > URL: https://issues.jboss.org/browse/WFLY-3070 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Karel Piwko > Assignee: Tomaz Cerar > > The link currently points to http://www.wildfly.org/download/, however should actually be http://wildfly.org/downloads/. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-821) SPNEGOSocket does not throw Exception in case it fails to establish GSSContext

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-821?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated SECURITY-821: --------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1088792, https://bugzilla.redhat.com/show_bug.cgi?id=1088793, https://bugzilla.redhat.com/show_bug.cgi?id=1088795 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1088792, https://bugzilla.redhat.com/show_bug.cgi?id=1088793) > SPNEGOSocket does not throw Exception in case it fails to establish GSSContext > ------------------------------------------------------------------------------ > > Key: SECURITY-821 > URL: https://issues.jboss.org/browse/SECURITY-821 > Project: PicketBox > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_1_5, Negotiation_2_2_7, Negotiation_2_3_0_Final > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: Negotiation_2_1_6, Negotiation_2_2_8, Negotiation_2_3_1_Final > > > Point of failure: https://github.com/wildfly/jboss-negotiation/blob/master/jboss-negotiatio... > Socket in mentioned versions log error and allow connection to be up. This is a cause of hangup in case of proxy lookup( atleast in EAP5 - JBPAPP-10748 ) > Code should terminate connection and throw exception upstream, in case login/logout(?) failure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-821) SPNEGOSocket does not throw Exception in case it fails to establish GSSContext

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-821?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated SECURITY-821: --------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1088792 > SPNEGOSocket does not throw Exception in case it fails to establish GSSContext > ------------------------------------------------------------------------------ > > Key: SECURITY-821 > URL: https://issues.jboss.org/browse/SECURITY-821 > Project: PicketBox > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_1_5, Negotiation_2_2_7, Negotiation_2_3_0_Final > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: Negotiation_2_1_6, Negotiation_2_2_8, Negotiation_2_3_1_Final > > > Point of failure: https://github.com/wildfly/jboss-negotiation/blob/master/jboss-negotiatio... > Socket in mentioned versions log error and allow connection to be up. This is a cause of hangup in case of proxy lookup( atleast in EAP5 - JBPAPP-10748 ) > Code should terminate connection and throw exception upstream, in case login/logout(?) failure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-821) SPNEGOSocket does not throw Exception in case it fails to establish GSSContext

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-821?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated SECURITY-821: --------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1088792, https://bugzilla.redhat.com/show_bug.cgi?id=1088793 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1088792) > SPNEGOSocket does not throw Exception in case it fails to establish GSSContext > ------------------------------------------------------------------------------ > > Key: SECURITY-821 > URL: https://issues.jboss.org/browse/SECURITY-821 > Project: PicketBox > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_1_5, Negotiation_2_2_7, Negotiation_2_3_0_Final > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: Negotiation_2_1_6, Negotiation_2_2_8, Negotiation_2_3_1_Final > > > Point of failure: https://github.com/wildfly/jboss-negotiation/blob/master/jboss-negotiatio... > Socket in mentioned versions log error and allow connection to be up. This is a cause of hangup in case of proxy lookup( atleast in EAP5 - JBPAPP-10748 ) > Code should terminate connection and throw exception upstream, in case login/logout(?) failure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3241) KDC server does not bind to correct address

by Dominik Pospisil (JIRA)

[ https://issues.jboss.org/browse/WFLY-3241?page=com.atlassian.jira.plugin.... ] Dominik Pospisil commented on WFLY-3241: ---------------------------------------- https://github.com/wildfly/wildfly/pull/6154 > KDC server does not bind to correct address > ------------------------------------------- > > Key: WFLY-3241 > URL: https://issues.jboss.org/browse/WFLY-3241 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.1.0.CR1 > Reporter: Dominik Pospisil > Assignee: Dominik Pospisil > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3241) KDC server does not bind to correct address

by Dominik Pospisil (JIRA)

[ https://issues.jboss.org/browse/WFLY-3241?page=com.atlassian.jira.plugin.... ] Dominik Pospisil resolved WFLY-3241. ------------------------------------ Resolution: Done > KDC server does not bind to correct address > ------------------------------------------- > > Key: WFLY-3241 > URL: https://issues.jboss.org/browse/WFLY-3241 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.1.0.CR1 > Reporter: Dominik Pospisil > Assignee: Dominik Pospisil > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-821) SPNEGOSocket does not throw Exception in case it fails to establish GSSContext

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/SECURITY-821?page=com.atlassian.jira.plug... ] Bartosz Baranowski commented on SECURITY-821: --------------------------------------------- PRs: 2.1.x : https://github.com/wildfly/jboss-negotiation/pull/10 2.2.x : https://github.com/wildfly/jboss-negotiation/pull/7 2.x : https://github.com/wildfly/jboss-negotiation/pull/8 > SPNEGOSocket does not throw Exception in case it fails to establish GSSContext > ------------------------------------------------------------------------------ > > Key: SECURITY-821 > URL: https://issues.jboss.org/browse/SECURITY-821 > Project: PicketBox > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_1_5, Negotiation_2_2_7, Negotiation_2_3_0_Final > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: Negotiation_2_1_6, Negotiation_2_2_8, Negotiation_2_3_1_Final > > > Point of failure: https://github.com/wildfly/jboss-negotiation/blob/master/jboss-negotiatio... > Socket in mentioned versions log error and allow connection to be up. This is a cause of hangup in case of proxy lookup( atleast in EAP5 - JBPAPP-10748 ) > Code should terminate connection and throw exception upstream, in case login/logout(?) failure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-821) SPNEGOSocket does not throw Exception in case it fails to establish GSSContext

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/SECURITY-821?page=com.atlassian.jira.plug... ] Bartosz Baranowski updated SECURITY-821: ---------------------------------------- Summary: SPNEGOSocket does not throw Exception in case it fails to establish GSSContext (was: SPNEGOSocket does not throw Exception in case it fails to establiosh GSSContext) > SPNEGOSocket does not throw Exception in case it fails to establish GSSContext > ------------------------------------------------------------------------------ > > Key: SECURITY-821 > URL: https://issues.jboss.org/browse/SECURITY-821 > Project: PicketBox > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_1_5, Negotiation_2_2_7, Negotiation_2_3_0_Final > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: Negotiation_2_1_6, Negotiation_2_2_8, Negotiation_2_3_1_Final > > > Point of failure: https://github.com/wildfly/jboss-negotiation/blob/master/jboss-negotiatio... > Socket in mentioned versions log error and allow connection to be up. This is a cause of hangup in case of proxy lookup( atleast in EAP5 - JBPAPP-10748 ) > Code should terminate connection and throw exception upstream, in case login/logout(?) failure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-821) SPNEGOSocket does not throw Exception in case it fails to establiosh GSSContext

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/SECURITY-821?page=com.atlassian.jira.plug... ] Bartosz Baranowski commented on SECURITY-821: --------------------------------------------- SPNEGOServerSocket seems to throw IOE in such case. > SPNEGOSocket does not throw Exception in case it fails to establiosh GSSContext > ------------------------------------------------------------------------------- > > Key: SECURITY-821 > URL: https://issues.jboss.org/browse/SECURITY-821 > Project: PicketBox > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_1_5, Negotiation_2_2_7, Negotiation_2_3_0_Final > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: Negotiation_2_1_6, Negotiation_2_2_8, Negotiation_2_3_1_Final > > > Point of failure: https://github.com/wildfly/jboss-negotiation/blob/master/jboss-negotiatio... > Socket in mentioned versions log error and allow connection to be up. This is a cause of hangup in case of proxy lookup( atleast in EAP5 - JBPAPP-10748 ) > Code should terminate connection and throw exception upstream, in case login/logout(?) failure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 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 April 2014