January 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1809) The security subsystem plugins use deprecated Infinispan API

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1809?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1809: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 8.0.0.Final) > The security subsystem plugins use deprecated Infinispan API > ------------------------------------------------------------ > > Key: WFLY-1809 > URL: https://issues.jboss.org/browse/WFLY-1809 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: 8.0.0.Alpha3 > Reporter: NadirX > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 9.0.0.CR1 > > > org.jboss.as.security.plugins.JNDIBasedSecurityManagement uses a deprecated way of configuring an Infinispan cache which must be removed. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2809) JACC PolicyContext.getContext("javax.servlet.http.HttpServletRequest")

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2809?page=com.atlassian.jira.plugin.... ] Jason Greene resolved WFLY-2809. -------------------------------- Resolution: Done > JACC PolicyContext.getContext("javax.servlet.http.HttpServletRequest") > ---------------------------------------------------------------------- > > Key: WFLY-2809 > URL: https://issues.jboss.org/browse/WFLY-2809 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EE > Affects Versions: 8.0.0.CR1 > Reporter: Frank Cornelis > Assignee: Stefan Guilhen > Priority: Blocker > Fix For: 8.0.0.Final > > Attachments: 0001-integration-test-for-JACC-PolicyContext.patch > > > Calling > {code} > PolicyContext.getContext("javax.servlet.http.HttpServletRequest"); > {code} > within a @Stateless session bean gives an exception. > I've created an integration test to reproduce this issue. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11) Bundle path for Embedded server still not working properly

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFLY-11?page=com.atlassian.jira.plugin.sy... ] Alexey Loubyansky updated WFLY-11: ---------------------------------- Fix Version/s: (was: 8.0.0.CR1) Git Pull Request: https://github.com/wildfly/wildfly/pull/5830 > Bundle path for Embedded server still not working properly > ---------------------------------------------------------- > > Key: WFLY-11 > URL: https://issues.jboss.org/browse/WFLY-11 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Galder Zamarreño > Assignee: Alexey Loubyansky > Fix For: 8.0.0.Final > > > Error is: > {code} io.escalante.test.artifact.ArtifactInstallTest: bundlesDir not a directory{code} > The problem is that the check is done in an 'assert' block and that only happens when assertions have been enabled by the user :( > The problem comes cos bundlesDir is set to "null/bundles", even if I have not set any bundlesDir. > Seems like bundlesDir is pre-computed too early in EmbeddedContainerConfiguration where it expects a system property, but that might not be set, it might come from arquillian.xml. So better delay until EmbeddedServerFactory.create. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11) Bundle path for Embedded server still not working properly

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFLY-11?page=com.atlassian.jira.plugin.sy... ] Alexey Loubyansky resolved WFLY-11. ----------------------------------- Resolution: Done Fixed. > Bundle path for Embedded server still not working properly > ---------------------------------------------------------- > > Key: WFLY-11 > URL: https://issues.jboss.org/browse/WFLY-11 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Galder Zamarreño > Assignee: Alexey Loubyansky > Fix For: 8.0.0.Final > > > Error is: > {code} io.escalante.test.artifact.ArtifactInstallTest: bundlesDir not a directory{code} > The problem is that the check is done in an 'assert' block and that only happens when assertions have been enabled by the user :( > The problem comes cos bundlesDir is set to "null/bundles", even if I have not set any bundlesDir. > Seems like bundlesDir is pre-computed too early in EmbeddedContainerConfiguration where it expects a system property, but that might not be set, it might come from arquillian.xml. So better delay until EmbeddedServerFactory.create. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1789) Fix host binding of tests involving GossipRouter

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/JGRP-1789?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz commented on JGRP-1789: ------------------------------------------- Both of these tests create their own stack involving TUNNEL and this stack does not explicitly set the bind address passed into the test case. Both the GossipRouter and the TUNNEL protocol should probably use the same jgroups.bind_addr to avoid this sort of failure. > Fix host binding of tests involving GossipRouter > ------------------------------------------------ > > Key: JGRP-1789 > URL: https://issues.jboss.org/browse/JGRP-1789 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2.13 > Environment: Windows > Reporter: Richard Achmatowicz > Assignee: Bela Ban > Fix For: 3.2.13 > > > Tests like TUNNEL_Test and GossipRouterTest make use of the following: > - a GosspiRouter which binds to a certain host address and port > - a GossipRouter client whose TUNNEL protocol binds to a certain host address and port > If these bind addresses are not specified, we often get test failures involving an inability of the client to communicate with the GossipRouter. > {noformat} > ------------- startRouter ----------- > -- starting GossipRouter on 127.0.0.1[23003] > ------------- testConnectThree ----------- > ------------------------------------------------------------------- > GMS: address=B, cluster=TUNNEL_Test, physical address=192.168.5.141:61373 > ------------------------------------------------------------------- > 605382 [WARN] TUNNEL: - Failed connecting to GossipRouter at /127.0.0.1:23003 > 605383 [WARN] TUNNEL: - failed reconnecting stub to GR at /127.0.0.1:23003: java.lang.Exception: Could not connect to /127.0.0.1:23003 > 605383 [ERROR] TUNNEL: - failed sending message to cluster (94 bytes): java.lang.Exception: None of the available stubs [RouterStub[localsocket=/192.168.5.141:51802,router_host=127.0.0.1::23003,connected=false]] accepted a multicast message, cause: null > {noformat} > TUNNEL_Test and GossipRouterTest are failing on Windows, for example, due to this sort of issue. > -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1789) Fix host binding of tests involving GossipRouter

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/JGRP-1789?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz updated JGRP-1789: -------------------------------------- Description: Tests like TUNNEL_Test and GossipRouterTest make use of the following: - a GosspiRouter which binds to a certain host address and port - a GossipRouter client whose TUNNEL protocol binds to a certain host address and port If these bind addresses are not specified, we often get test failures involving an inability of the client to communicate with the GossipRouter, due to each not having the other's correct address, or one being on local host and the other on a non-localhost interface: {noformat} ------------- startRouter ----------- -- starting GossipRouter on 127.0.0.1[23003] ------------- testConnectThree ----------- ------------------------------------------------------------------- GMS: address=B, cluster=TUNNEL_Test, physical address=192.168.5.141:61373 ------------------------------------------------------------------- 605382 [WARN] TUNNEL: - Failed connecting to GossipRouter at /127.0.0.1:23003 605383 [WARN] TUNNEL: - failed reconnecting stub to GR at /127.0.0.1:23003: java.lang.Exception: Could not connect to /127.0.0.1:23003 605383 [ERROR] TUNNEL: - failed sending message to cluster (94 bytes): java.lang.Exception: None of the available stubs [RouterStub[localsocket=/192.168.5.141:51802,router_host=127.0.0.1::23003,connected=false]] accepted a multicast message, cause: null {noformat} TUNNEL_Test and GossipRouterTest are failing on Windows, for example, due to this sort of issue. was: Tests like TUNNEL_Test and GossipRouterTest make use of the following: - a GosspiRouter which binds to a certain host address and port - a GossipRouter client whose TUNNEL protocol binds to a certain host address and port If these bind addresses are not specified, we often get test failures involving an inability of the client to communicate with the GossipRouter. {noformat} ------------- startRouter ----------- -- starting GossipRouter on 127.0.0.1[23003] ------------- testConnectThree ----------- ------------------------------------------------------------------- GMS: address=B, cluster=TUNNEL_Test, physical address=192.168.5.141:61373 ------------------------------------------------------------------- 605382 [WARN] TUNNEL: - Failed connecting to GossipRouter at /127.0.0.1:23003 605383 [WARN] TUNNEL: - failed reconnecting stub to GR at /127.0.0.1:23003: java.lang.Exception: Could not connect to /127.0.0.1:23003 605383 [ERROR] TUNNEL: - failed sending message to cluster (94 bytes): java.lang.Exception: None of the available stubs [RouterStub[localsocket=/192.168.5.141:51802,router_host=127.0.0.1::23003,connected=false]] accepted a multicast message, cause: null {noformat} TUNNEL_Test and GossipRouterTest are failing on Windows, for example, due to this sort of issue. > Fix host binding of tests involving GossipRouter > ------------------------------------------------ > > Key: JGRP-1789 > URL: https://issues.jboss.org/browse/JGRP-1789 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2.13 > Environment: Windows > Reporter: Richard Achmatowicz > Assignee: Bela Ban > Fix For: 3.2.13 > > > Tests like TUNNEL_Test and GossipRouterTest make use of the following: > - a GosspiRouter which binds to a certain host address and port > - a GossipRouter client whose TUNNEL protocol binds to a certain host address and port > If these bind addresses are not specified, we often get test failures involving an inability of the client to communicate with the GossipRouter, due to each not having the other's correct address, or one being on local host and the other on a non-localhost interface: > {noformat} > ------------- startRouter ----------- > -- starting GossipRouter on 127.0.0.1[23003] > ------------- testConnectThree ----------- > ------------------------------------------------------------------- > GMS: address=B, cluster=TUNNEL_Test, physical address=192.168.5.141:61373 > ------------------------------------------------------------------- > 605382 [WARN] TUNNEL: - Failed connecting to GossipRouter at /127.0.0.1:23003 > 605383 [WARN] TUNNEL: - failed reconnecting stub to GR at /127.0.0.1:23003: java.lang.Exception: Could not connect to /127.0.0.1:23003 > 605383 [ERROR] TUNNEL: - failed sending message to cluster (94 bytes): java.lang.Exception: None of the available stubs [RouterStub[localsocket=/192.168.5.141:51802,router_host=127.0.0.1::23003,connected=false]] accepted a multicast message, cause: null > {noformat} > TUNNEL_Test and GossipRouterTest are failing on Windows, for example, due to this sort of issue. > -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1789) Fix host binding of tests involving GossipRouter

by Richard Achmatowicz (JIRA)

Richard Achmatowicz created JGRP-1789: ----------------------------------------- Summary: Fix host binding of tests involving GossipRouter Key: JGRP-1789 URL: https://issues.jboss.org/browse/JGRP-1789 Project: JGroups Issue Type: Bug Affects Versions: 3.2.13 Environment: Windows Reporter: Richard Achmatowicz Assignee: Bela Ban Fix For: 3.2.13 Tests like TUNNEL_Test and GossipRouterTest make use of the following: - a GosspiRouter which binds to a certain host address and port - a GossipRouter client whose TUNNEL protocol binds to a certain host address and port If these bind addresses are not specified, we often get test failures involving an inability of the client to communicate with the GossipRouter. {noformat} ------------- startRouter ----------- -- starting GossipRouter on 127.0.0.1[23003] ------------- testConnectThree ----------- ------------------------------------------------------------------- GMS: address=B, cluster=TUNNEL_Test, physical address=192.168.5.141:61373 ------------------------------------------------------------------- 605382 [WARN] TUNNEL: - Failed connecting to GossipRouter at /127.0.0.1:23003 605383 [WARN] TUNNEL: - failed reconnecting stub to GR at /127.0.0.1:23003: java.lang.Exception: Could not connect to /127.0.0.1:23003 605383 [ERROR] TUNNEL: - failed sending message to cluster (94 bytes): java.lang.Exception: None of the available stubs [RouterStub[localsocket=/192.168.5.141:51802,router_host=127.0.0.1::23003,connected=false]] accepted a multicast message, cause: null {noformat} TUNNEL_Test and GossipRouterTest are failing on Windows, for example, due to this sort of issue. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2558) Patching core Test failure

by Emanuel Muckenhuber (JIRA)

[ https://issues.jboss.org/browse/WFLY-2558?page=com.atlassian.jira.plugin.... ] Emanuel Muckenhuber resolved WFLY-2558. --------------------------------------- Fix Version/s: 8.0.0.Final Resolution: Done > Patching core Test failure > -------------------------- > > Key: WFLY-2558 > URL: https://issues.jboss.org/browse/WFLY-2558 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Patching > Affects Versions: 8.0.0.Beta1 > Environment: JDK 8-ea-b115, Linux Ubuntu 64-bit > Reporter: Yosi Pramajaya > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.Final > > > Running org.jboss.as.patching.tests.PatchModuleInvalidationTestCase > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.135 sec <<< FAILURE! - in org.jboss.as.patching.tests.PatchModuleInvalidationTestCase > test(org.jboss.as.patching.tests.PatchModuleInvalidationTestCase) Time elapsed: 0.13 sec <<< FAILURE! > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertNotNull(Assert.java:621) > at org.junit.Assert.assertNotNull(Assert.java:631) > at org.jboss.as.patching.tests.PatchModuleInvalidationTestCase.assertLoadable(PatchModuleInvalidationTestCase.java:192) > at org.jboss.as.patching.tests.PatchModuleInvalidationTestCase.test(PatchModuleInvalidationTestCase.java:77) -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2723) Accessing "serverInventory" without holding lock "serverInventoryLock"

by Emanuel Muckenhuber (JIRA)

[ https://issues.jboss.org/browse/WFLY-2723?page=com.atlassian.jira.plugin.... ] Emanuel Muckenhuber resolved WFLY-2723. --------------------------------------- Fix Version/s: 8.0.0.Final Resolution: Done > Accessing "serverInventory" without holding lock "serverInventoryLock" > ---------------------------------------------------------------------- > > Key: WFLY-2723 > URL: https://issues.jboss.org/browse/WFLY-2723 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Rostislav Svoboda > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.Final > > > Accessing "serverInventory" without holding lock "org.jboss.as.host.controller.DomainModelControllerService.serverInventoryLock". > Elsewhere, "serverInventory" is accessed with "DomainModelControllerService.serverInventoryLock" held 4 out of 5 times. > https://github.com/wildfly/wildfly/blob/master/host-controller/src/main/j... -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2791) Remove jboss-marshalling mvn dependency from the management protocol

by Emanuel Muckenhuber (JIRA)

[ https://issues.jboss.org/browse/WFLY-2791?page=com.atlassian.jira.plugin.... ] Emanuel Muckenhuber resolved WFLY-2791. --------------------------------------- Resolution: Done > Remove jboss-marshalling mvn dependency from the management protocol > -------------------------------------------------------------------- > > Key: WFLY-2791 > URL: https://issues.jboss.org/browse/WFLY-2791 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Emanuel Muckenhuber > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.Final > > > The wildfly-protocol depends on jboss-marshalling although it should not be used for a while now. We need to verify that it's not used any more and remove it. -- 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, 12 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 January 2014