February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3872) The package sun.util.locale is missing when you use the class java.util.Locale in a JSP file.

by Igor Nadal (JIRA)

Igor Nadal created AS7-3872: ------------------------------- Summary: The package sun.util.locale is missing when you use the class java.util.Locale in a JSP file. Key: AS7-3872 URL: https://issues.jboss.org/browse/AS7-3872 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.0.Final Environment: Operative system: Kubuntu 11.10 (Oneiric Ocelot) / Linux 3.0.0-16-generic x86_64 JDK: Oracle JDK 1.7.0_01 Reporter: Igor Nadal Assignee: Jason Greene If you use the 2 arguments constructor of java.util.Locale in a JSP file, it triggers an exception which reports about the absence of classes from the package sun.util.locale. This is the stacktrace which I get when I use such constructor in a simple JSP: 15:49:56,476 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/test].[jsp]] (http--0.0.0.0-8443-1) Servlet.service() for servlet jsp threw exception: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 7 in the jsp file: /index.jsp The type sun.util.locale.LocaleExtensions cannot be resolved. It is indirectly referenced from required .class files 4: 5: %><% 6: 7: Locale myLocale = new Locale ("es", "ES"); 8: 9: 10: %> An error occurred at line: 7 in the jsp file: /index.jsp The type sun.util.locale.BaseLocale cannot be resolved. It is indirectly referenced from required .class files 4: 5: %><% 6: 7: Locale myLocale = new Locale ("es", "ES"); 8: 9: 10: %> Stacktrace: at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:92) [jbossweb-7.0.10.Final.jar:] at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:330) [jbossweb-7.0.10.Final.jar:] at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:446) [jbossweb-7.0.10.Final.jar:] at org.apache.jasper.compiler.Compiler.compile(Compiler.java:362) [jbossweb-7.0.10.Final.jar:] at org.apache.jasper.compiler.Compiler.compile(Compiler.java:340) [jbossweb-7.0.10.Final.jar:] at org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) [jbossweb-7.0.10.Final.jar:] at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:607) [jbossweb-7.0.10.Final.jar:] at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:312) [jbossweb-7.0.10.Final.jar:] at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326) [jbossweb-7.0.10.Final.jar:] at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253) [jbossweb-7.0.10.Final.jar:] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final.jar:] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_01] If I use the same java.util.Locale constructor in a simple class into the same WAR, no exception is thrown however. This error is not thrown using the JDK 6, neither in JSP files nor in classes. -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] (AS7-3798) JGroups subsystem tcp stack should set NAKACK.use_mcast_xmit to false

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-3798: --------------------------------- Summary: JGroups subsystem tcp stack should set NAKACK.use_mcast_xmit to false Key: AS7-3798 URL: https://issues.jboss.org/browse/AS7-3798 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Minor Fix For: 7.1.1.Final ... to avoid the following unnecessary warning in the log: 10:38:00,676 WARNING [org.jgroups.protocols.pbcast.NAKACK] (pool-4-thread-1) use_mcast_xmit should not be used because the transport (TCP) does not support IP multicasting; setting use_mcast_xmit to false Consider setting this property automatically, based on whether the transport supports multicast. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] (AS7-3965) Make modcluster subsystem attributes to support ${} property notation

by Noel Rocher (JIRA)

Noel Rocher created AS7-3965: -------------------------------- Summary: Make modcluster subsystem attributes to support ${} property notation Key: AS7-3965 URL: https://issues.jboss.org/browse/AS7-3965 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Affects Versions: 7.1.0.Final Reporter: Noel Rocher Assignee: Paul Ferraro Make modcluster subsystem attributes to support ${} property notation -- 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, 3 months

3
4
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, 3 months

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, 3 months

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, 3 months

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, 3 months

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, 3 months

2
2
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, 3 months

2
2
0 / 0

[JBoss JIRA] (AS7-2800) JMX via JNDI not working

by Savas Ali Tokmen (Created) (JIRA)

JMX via JNDI not working ------------------------ Key: AS7-2800 URL: https://issues.jboss.org/browse/AS7-2800 Project: Application Server 7 Issue Type: Bug Components: JMX Affects Versions: 7.1.0.Beta1 Reporter: Savas Ali Tokmen Assignee: John Bailey Fix For: 7.1.0.CR1, 7.1.0.Final The documentation on https://docs.jboss.org/author/display/AS7/JMX+subsystem+configuration as well as the testcase jmx/src/test/java/org/jboss/as/jmx/JMXSubsystemTestCase.java seems to indicate that the JMX URL service:jmx:rmi:///jndi/rmi://localhost:1090/jmxrmi should be accessible via a JMX console (for example, the jconsole). When I open: {noformat} jconsole service:jmx:rmi:///jndi/rmi://localhost:1090/jmxrmi {noformat} I get an error message saying: "the connection to service:jmx:rmi:///jndi/rmi://localhost:1090/jmxrmi did not succeed". -- 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, 3 months

6
7
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 February 2012