July 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-3312) LdapExtLoginModule is missing the first role group of a nested structure

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3312?page=all ] Dimitris Andreadis updated JBAS-3312: ------------------------------------- Fix Version/s: JBossAS-4.0.6.CR1 (was: JBossAS-4.0.5.CR1) Assignee: Anil Saldhana (was: Scott M Stark) > LdapExtLoginModule is missing the first role group of a nested structure > ------------------------------------------------------------------------ > > Key: JBAS-3312 > URL: http://jira.jboss.com/jira/browse/JBAS-3312 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: JBossAS-4.0.4.GA > Reporter: Scott M Stark > Assigned To: Anil Saldhana > Fix For: JBossAS-4.0.6.CR1 > > > When traversing through a hiearchical role structure, the first matching context does not have its role name added to the resulting subject roles. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1283) Tomcat Unable to Compile JSPs when Separate ClassLoader Namespace Used for Webapp

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1283?page=all ] Dimitris Andreadis updated JBAS-1283: ------------------------------------- Fix Version/s: JBossAS-4.0.6.CR1 (was: JBossAS-4.0.5.CR1) > Tomcat Unable to Compile JSPs when Separate ClassLoader Namespace Used for Webapp > --------------------------------------------------------------------------------- > > Key: JBAS-1283 > URL: http://jira.jboss.com/jira/browse/JBAS-1283 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Affects Versions: JBossAS-3.2.6 Final > Environment: Stock JBoss 3.2.6 running on Linux (kernel 2.4.26), Sun JDK and JRE version 1.4.2_04 > Reporter: Jeremy Brown > Assigned To: Scott M Stark > Priority: Minor > Fix For: JBossAS-4.0.6.CR1 > > Attachments: test.war > > > See my initial forum post at "http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861452#3861452". > The dom4j libs provided by JBoss do not work correctly with my web application, so I attempted to configure my webapp's "jboss-web.xml"--as per the wiki page at "http://www.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration"--so that my webapp would essentially be in a different classloader namspace and would be able to override the server dom4j implementation with its own. Now, Tomcat bails out during JSP compilation with a dom4j-related ClassCastException, leading me to believe there might some problem with the sort of setup I'm trying to attempt...for example, Tomcat's JSP compiler might be trying to link with the dom4j in my application's namespace while its classes have been loaded next to (and probably are already using) dom4j in the server namespace. > I'll attach a .war file exhibiting this behavior to this bug report. > Here's the specific exception for this .war file: > java.lang.ClassCastException > at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:93) > at org.apache.jasper.xmlparser.ParserUtils.parseXMLDocument(ParserUtils.java:91) > at org.apache.jasper.compiler.JspConfig.processWebDotXml(JspConfig.java:70) > at org.apache.jasper.compiler.JspConfig.init(JspConfig.java:188) > at org.apache.jasper.compiler.JspConfig.findJspProperty(JspConfig.java:240) > at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:160) > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:470) > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:451) > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:439) > at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511) > at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295) > at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) > at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) > at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) > at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) > at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) > at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:66) > at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:158) > at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) > at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) > at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118) > at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) > at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) > at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705) > at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) > at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) > at java.lang.Thread.run(Thread.java:534) > Interestingly enough, I can copy my app-specific "dom4j-full.jar" over the JBoss-provided "dom4j.jar" in "/lib", and everything works great. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-541) i18n issue in JNDIView - needs html encode

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-541?page=all ] Dimitris Andreadis updated JBAS-541: ------------------------------------ Fix Version/s: (was: JBossAS-4.0.5.CR1) > i18n issue in JNDIView - needs html encode > ------------------------------------------ > > Key: JBAS-541 > URL: http://jira.jboss.com/jira/browse/JBAS-541 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Naming > Affects Versions: JBossAS-3.2.6 Final > Reporter: SourceForge User > Assigned To: Scott M Stark > Priority: Minor > > SourceForge Submitter: rodburgett . > JNDIView.listXML retrieves context and entry names and > puts them into an XML doc. If any of these names > contain special or foreign characters, then an XML > processor or browser will object. All these names > should be HTML encoded as the doc is created. > Updating JNDIView to call an encoding method is easy, > the harder part is finding/writing that method. > Is there an encoder embedded somewhere in JBoss, > Jetty or one of the tools to do this, or do we need to > create one? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1313) RepositorySelector should be integrated into JBoss Server

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1313?page=all ] Dimitris Andreadis updated JBAS-1313: ------------------------------------- Fix Version/s: JBossAS-4.0.6.CR1 (was: JBossAS-4.0.5.CR1) > RepositorySelector should be integrated into JBoss Server > --------------------------------------------------------- > > Key: JBAS-1313 > URL: http://jira.jboss.com/jira/browse/JBAS-1313 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JMX > Reporter: Stan Silvert > Assigned To: Stan Silvert > Priority: Minor > Fix For: JBossAS-4.0.6.CR1 > > > Often, an application will want to have its own log4j configuration and have all log messages generated go to an application-specific log file. Solutions to this problem are documented on this wiki page: http://www.jboss.org/wiki/Wiki.jsp?page=Logging > The log4j RepositorySelector provides a clean solution to this problem without any special classloader settings. However, at the present time, a developer must create his own version of a RepositorySelector and make sure his application initializes it properly. > This can be difficult to accomplish because the RepositorySelector feature is not well known and takes time to understand. It can also be difficult to make sure that the RepositorySelector is initialized before the application makes ANY call to Logger.getLogger(). > We can instead, provide a RepositorySelector implementation as part of the JBoss Application server. If a deployer finds a log4j.xml file in the /META-INF direcotry (or /WEB-INF for WARs) it would add an entry into the RepositorySelector for that application. Then, logging from that application would use the custom log4j configuration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1505) Wrong exception message for missing findByPrimaryKey() method

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1505?page=all ] Dimitris Andreadis updated JBAS-1505: ------------------------------------- Fix Version/s: JBossAS-4.0.6.CR1 (was: JBossAS-4.0.5.CR1) > Wrong exception message for missing findByPrimaryKey() method > ------------------------------------------------------------- > > Key: JBAS-1505 > URL: http://jira.jboss.com/jira/browse/JBAS-1505 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB2 > Affects Versions: JBossAS-4.0.1 SP1 > Environment: Windows 2000 Professional / Sun JDK 1.4.2_04 > Reporter: Torsten Paul > Assigned To: Alexey Loubyansky > Priority: Minor > Fix For: JBossAS-4.0.6.CR1 > > Attachments: testcase.zip > > > When deploying an application including a bean with a missing findByPrimaryKey() method in the home interface the exception message gives not the offending bean > but an arbitrary other bean that possibly has a findByPrimaryKey() method. This makes it hard to find the bean that needs fixing. > (Explained in http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48222 but I didn't find a bugtracking entry for this.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1900) Clustered webapp shouldn't require ClusteredSingleSignon?

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1900?page=all ] Dimitris Andreadis updated JBAS-1900: ------------------------------------- Fix Version/s: JBossAS-4.0.6.CR1 (was: JBossAS-4.0.5.CR1) > Clustered webapp shouldn't require ClusteredSingleSignon? > --------------------------------------------------------- > > Key: JBAS-1900 > URL: http://jira.jboss.com/jira/browse/JBAS-1900 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security, Clustering > Affects Versions: JBossAS-4.0.2 Final > Reporter: Stan Silvert > Assigned To: Brian Stansberry > Priority: Minor > Fix For: JBossAS-4.0.6.CR1 > > > A customer had three webapps. The set of users for each webapp is different. So, they don't want single signon behavior. They do want HttpSessionReplication to take care of the credentials so that the user doesn't need to sign on when redirected to another server. It was found that we needed to enable clustered single signon to get this to work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2301) Startup fails if plus sign in JBoss home path

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2301?page=all ] Dimitris Andreadis updated JBAS-2301: ------------------------------------- Fix Version/s: JBossAS-4.0.6.CR1 (was: JBossAS-4.0.5.CR1) > Startup fails if plus sign in JBoss home path > --------------------------------------------- > > Key: JBAS-2301 > URL: http://jira.jboss.com/jira/browse/JBAS-2301 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: System service > Affects Versions: JBossAS-4.0.3RC2 > Environment: Linux > Reporter: Ortwin Glück > Priority: Minor > Fix For: JBossAS-4.0.6.CR1 > > > If the JBoss home directory contains a plus sign (+) startup fails with a ClassNotFoundException. In my setup the real path contained the plus sign but I used a symlink without a plus and it still crashed. I guess this is due to missing/wrong URL encoding when you configure the URLClassLoader in the startup classes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1955) New Interceptor to InvokerAdaptorService that prevent NonSerializableException

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1955?page=all ] Dimitris Andreadis updated JBAS-1955: ------------------------------------- Fix Version/s: (was: JBossAS-4.0.5.CR1) Assignee: (was: Scott M Stark) > New Interceptor to InvokerAdaptorService that prevent NonSerializableException > ------------------------------------------------------------------------------ > > Key: JBAS-1955 > URL: http://jira.jboss.com/jira/browse/JBAS-1955 > Project: JBoss Application Server > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: Management services > Affects Versions: JBossAS-4.0.2 Final > Environment: jmx, twiddle > Reporter: Fabiano C. de Oliveira > Priority: Minor > Attachments: JBAS-1955.zip, JBAS-1955a.zip, JBAS-1955a.zip > > > This patch add a Interceptor to org.jboss.jmx.connector.invoker.InvokerAdaptorService besides AuthenticationInterceptor that is responsable for prevent remote clients to launch NonSerializable exception. See http://jira.jboss.com/jira/browse/JBAS-1939 and > The interception have 3 types of action: Invisible, Null and Wrapper. > In the Invisible mode all NonSerializable fields are ignored so if you call getMBeanInfo all NonSerializable will be remove and returned to your remote client(twiddle, MC4J, etc). This mode is more tested so it is recommended. > In the null mode NonSerializable fields are visible but always return Null. > The wraper mode is not implemented, but the idea is replace the NonSerializable Class for another > The interceptor is only a class. The tests are in the patch too. Only test for invisible mode. I´m still doing tests for the other modes. > Any idea is very appreciated. I dont have sufficient time to work more in this code. But I hope to do soon. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1942) Hypersonic MBean does not correctly reflect the state of the database

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1942?page=all ] Dimitris Andreadis updated JBAS-1942: ------------------------------------- Fix Version/s: JBossAS-4.0.6.CR1 (was: JBossAS-4.0.5.CR1) > Hypersonic MBean does not correctly reflect the state of the database > --------------------------------------------------------------------- > > Key: JBAS-1942 > URL: http://jira.jboss.com/jira/browse/JBAS-1942 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Other > Affects Versions: JBossAS-4.0.2 Final > Reporter: Adrian Brock > Priority: Minor > Fix For: JBossAS-4.0.6.CR1 > > > The Hypersonic MBean does not correctly start the database. > It forks a thread which could take a while to recover the database/bind sockets. > This means that dependent services may try to use the database before it ready, > e.g. see the Hack in JBossMQ's persistence manager that has a retry loop to avoid the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2395) Allow for easy configuration of mutlicast port like multicast address

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2395?page=all ] Dimitris Andreadis updated JBAS-2395: ------------------------------------- Fix Version/s: JBossAS-4.0.6.CR1 (was: JBossAS-4.0.5.CR1) > Allow for easy configuration of mutlicast port like multicast address > --------------------------------------------------------------------- > > Key: JBAS-2395 > URL: http://jira.jboss.com/jira/browse/JBAS-2395 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Deployment services > Affects Versions: JBossAS-4.0.3 Final > Reporter: Adrian Brock > Priority: Minor > Fix For: JBossAS-4.0.6.CR1 > > > This bug report suggests http://bugs.sun.com/bugdatabase/view_bug.do;:YfiG?bug_id=4701650 > suggests that the new "-u" option isn't going to work on all platforms so we should look at using the port instead. > See the forums discussion for more info. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
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 July 2006