March 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4062) Fix CLITestSuite and DomainTestSuite failures on windows platform

by Dominik Pospisil (JIRA)

Dominik Pospisil created AS7-4062: ------------------------------------- Summary: Fix CLITestSuite and DomainTestSuite failures on windows platform Key: AS7-4062 URL: https://issues.jboss.org/browse/AS7-4062 Project: Application Server 7 Issue Type: Task Components: Test Suite Affects Versions: 7.1.1.Final Reporter: Dominik Pospisil Assignee: Dominik Pospisil CLITestSuite and DomainTestsuite fail consistently on Windows platform. CLITestSuite failure stacktrace: java.lang.Exception: CLI read timeout. at org.jboss.as.test.integration.management.util.CLIWrapper.readLine(CLIWrapper.java:188) at org.jboss.as.test.integration.management.util.CLIWrapper.sendLine(CLIWrapper.java:135) at org.jboss.as.test.integration.management.util.CLIWrapper.sendLine(CLIWrapper.java:154) at org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase.addRolloutPlan(RolloutPlanTestCase.java:66) at org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase.testRolloutPlan(RolloutPlanTestCase.java:52) DomainTestSuite failure stacktrace: java.lang.AssertionError: at org.junit.Assert.fail(Assert.java:91) at org.junit.Assert.assertTrue(Assert.java:43) at org.junit.Assert.assertTrue(Assert.java:54) at org.jboss.as.test.integration.domain.suites.CoreResourceManagementTestCase.testDomainSnapshot(CoreResourceManagementTestCase.java:488) There is a FileNotFoundException in log as Windows systems are unable to find application-users.properties file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
1
0 / 0

[JBoss JIRA] (AS7-3659) Create test for depoyed JDBC driver.

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3659: --------------------------------- Summary: Create test for depoyed JDBC driver. Key: AS7-3659 URL: https://issues.jboss.org/browse/AS7-3659 Project: Application Server 7 Issue Type: Task Components: Test Suite Reporter: Ondrej Zizka Assignee: Vladimir Rastseluev Fix For: 7.1.1.Final JDBC 4.0 driver, instead of being a module, may also be a deployment - when just copied to {{standalone/deployments}}. Please create a test which copies a JDBC 4.0 driver (any - pick from ) from src/test/resources to {{standalone/deployments}}, sets up a datasource in AS config accordingly, and does some basic operation on it. And then cleans up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
9
0 / 0

[JBoss JIRA] (AS7-2929) Add support for unscheduled write-behind cache stores to Infinispan subsytem

by Martin Gencur (Created) (JIRA)

Add support for unscheduled write-behind cache stores to Infinispan subsytem ---------------------------------------------------------------------------- Key: AS7-2929 URL: https://issues.jboss.org/browse/AS7-2929 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Reporter: Martin Gencur Assignee: Tristan Tarrant Infinispan subsystem should support unscheduled write-behind cache stores. Currently it is not possible to set this up. In Infinispan this is done via <async> sub-element of <loader> element. E.g. <async enabled="true" threadPoolSize="10" /> Documentation for EDG is mentioning both unscheduled and scheduled write-behind cache stores even though scheduled one is not implemented even in Infinispan (ISPN-328). OTOH, the unscheduled one is implemented and should be available in EDG. So take into account that in future there might be also scheduled write-behind store available and infinispan schema for JBossAS should count with that. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1182) DatabaseServerLoginModule doesn't work

by Juergen Zimmermann (JIRA)

DatabaseServerLoginModule doesn't work -------------------------------------- Key: AS7-1182 URL: https://issues.jboss.org/browse/AS7-1182 Project: Application Server 7 Issue Type: Bug Components: Security Affects Versions: 7.0.0.CR1 Reporter: Juergen Zimmermann I want to migrate from JBossAS 6 to 7.0.0.CR1. In standalone.xml I declare the following security domain, but get the stacktrace (see below) looking for UsersRolesLoginModule instead of DatabaseServerLoginModule. Security domain in standalone.xml: <security-domain name="swe2" cache-type="default"> <authentication> <login-module code="Database" flag="required"> <module-option name="dsJndiName" value="java:/swe2DS"/> <module-option name="unauthenticatedIdentity" value="gast"/> <module-option name="principalsQuery" value="SELECT password FROM kunde WHERE username=?"/> <module-option name="rolesQuery" value="SELECT role, 'Roles' FROM swe2_role r INNER JOIN kunde k ON r.kunde_fk = k.k_id WHERE k.username=?"/> <module-option name="hashAlgorithm" value="SHA-1"/> <module-option name="hashEncoding" value="base64"/> </login-module> </authentication> </security-domain> Stacktrace regarding UsersRolesLoginModule (instead of DatabaseServerLoginModule): 16:03:58,528 ERROR [org.jboss.security.auth.spi.UsersRolesLoginModule] (http--127.0.0.1-8080-2) Failed to load users/passwords/role files: java.io.IOException: No properties file: users.properties or defaults: defaultUsers.properties found at org.jboss.security.auth.spi.Util.loadProperties(Util.java:227) [picketbox-4.0.0.CR1.jar:4.0.0.CR1] at org.jboss.security.auth.spi.UsersRolesLoginModule.loadUsers(UsersRolesLoginModule.java:188) [picketbox-4.0.0.CR1.jar:4.0.0.CR1] at org.jboss.security.auth.spi.UsersRolesLoginModule.createUsers(UsersRolesLoginModule.java:202) [picketbox-4.0.0.CR1.jar:4.0.0.CR1] at org.jboss.security.auth.spi.UsersRolesLoginModule.initialize(UsersRolesLoginModule.java:129) [picketbox-4.0.0.CR1.jar:4.0.0.CR1] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] at javax.security.auth.login.LoginContext.invoke(LoginContext.java:756) [:1.6.0_26] at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) [:1.6.0_26] at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) [:1.6.0_26] at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_26] at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) [:1.6.0_26] at javax.security.auth.login.LoginContext.login(LoginContext.java:579) [:1.6.0_26] at org.jboss.security.authentication.JBossCachedAuthenticationManager.defaultLogin(JBossCachedAuthenticationManager.java:411) [picketbox-infinispan-4.0.0.CR1.jar:4.0.0.CR1] at org.jboss.security.authentication.JBossCachedAuthenticationManager.authenticate(JBossCachedAuthenticationManager.java:345) [picketbox-infinispan-4.0.0.CR1.jar:4.0.0.CR1] at org.jboss.security.authentication.JBossCachedAuthenticationManager.isValid(JBossCachedAuthenticationManager.java:154) [picketbox-infinispan-4.0.0.CR1.jar:4.0.0.CR1] at org.jboss.as.web.security.JBossWebRealm.authenticate(JBossWebRealm.java:127) [jboss-as-web-7.0.0.CR1.jar:7.0.0.CR1] at org.apache.catalina.authenticator.BasicAuthenticator.authenticate(BasicAuthenticator.java:180) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:446) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1] at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.0.CR1.jar:7.0.0.CR1] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.0.CR1.jar:7.0.0.CR1] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1] at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:893) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1] at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:626) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1] at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:2054) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
16
0 / 0

[JBoss JIRA] (JBWEB-226) Prevent Web Crawlers from creating many sessions

by Jason Shepherd (JIRA)

Jason Shepherd created JBWEB-226: ------------------------------------ Summary: Prevent Web Crawlers from creating many sessions Key: JBWEB-226 URL: https://issues.jboss.org/browse/JBWEB-226 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Reporter: Jason Shepherd Assignee: Remy Maucherat Priority: Minor This feature solve the same problem as the Tomcat 7 CrawlerSessionManagerValve, described here [1]. Also the source code for the Valve is available here, [2]. Jean-Frederic has suggested it would be better implement this as a filter instead of a valve. [1] http://www.tomcatexpert.com/blog/2011/05/18/crawler-session-manager-valve [2] http://svn.apache.org/repos/asf/tomcat/tc7.0.x/trunk/java/org/apache/cata... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] (AS7-3953) maxHttpHeaderSize

by Juergen Hoffmann (JIRA)

Juergen Hoffmann created AS7-3953: ------------------------------------- Summary: maxHttpHeaderSize Key: AS7-3953 URL: https://issues.jboss.org/browse/AS7-3953 Project: Application Server 7 Issue Type: Feature Request Components: Web Reporter: Juergen Hoffmann Assignee: Remy Maucherat a user was able to configure the maxHttpHeaderSize in the <Connector Definition. Now the Headersize is fixed to 8k. In my particular case I am configuring jboss SPNEGO Negotiation against AD. Which works, but I have too many rights. making the header bigger than 8k and I am getting: 17:02:59,941 DEBUG [org.apache.coyote.http11.Http11Processor] (http--0.0.0.0-8080-1) Error parsing HTTP request header: java.lang.IllegalArgumentException: Request header is too large Please add this again as a configurable parameter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] (AS7-4024) ignore this

by Jan Lanik (JIRA)

[ https://issues.jboss.org/browse/AS7-4024?page=com.atlassian.jira.plugin.s... ] Jan Lanik deleted AS7-4024: --------------------------- > ignore this > ----------- > > Key: AS7-4024 > URL: https://issues.jboss.org/browse/AS7-4024 > Project: Application Server 7 > Issue Type: Bug > Reporter: Jan Lanik > Assignee: Jan Lanik > Priority: Critical > > ignore this -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4024) Remove security/auditing/form-auth.war

by Jan Lanik (JIRA)

Jan Lanik created AS7-4024: ------------------------------ Summary: Remove security/auditing/form-auth.war Key: AS7-4024 URL: https://issues.jboss.org/browse/AS7-4024 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.1.0.Final Reporter: Jan Lanik Assignee: Jan Lanik Priority: Critical Fix For: 7.1.1.Final Deployments are build using shrinkwrap. They should not just be be pre-built and then dumped into the resources dir as a binary blob. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
4
0 / 0

[JBoss JIRA] (AS7-4035) Method setResourceAdpater() in administered object implementation never called by server

by Vladimir Rastseluev (JIRA)

Vladimir Rastseluev created AS7-4035: ---------------------------------------- Summary: Method setResourceAdpater() in administered object implementation never called by server Key: AS7-4035 URL: https://issues.jboss.org/browse/AS7-4035 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.0.Final Reporter: Vladimir Rastseluev Assignee: Stefano Maestri Fix For: 7.1.1.Final Test case will be added. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
1
0 / 0

[JBoss JIRA] (AS7-3771) If slave HC fails to connect to remote DC due to SSL handlshake failure it should terminate quickly

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3771: ------------------------------------- Summary: If slave HC fails to connect to remote DC due to SSL handlshake failure it should terminate quickly Key: AS7-3771 URL: https://issues.jboss.org/browse/AS7-3771 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.1.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
2
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 March 2012